New Designer features - Part 1
This is the first in a series of blogs about new stuff in Designer. Yes, I know there have been presentations at Lotusphere, and there's a forum. I'm interested in getting specific discussion about individual features in the comments here. So speak up!
From the help...
Support Response Thread History
This option is new with release 8. If "Support Response Thread History" is selected, documents in the database contain additional information fields allowing them to be sorted into a document response hierarchy.
Note Selecting this option has no effect on existing documents. Existing threads will not be identified or rendered as such and only new threads will take part in the feature. This is true even if a new replica or copy is made of a database with existing threads. Only new documents will be processed for thread citizenship and a place in the hierarchy.
I'm not clear on what makes this different from the old "Don't support specialized response hierarchy."
Don't allow simple search
This option is new with release 8. When "Don't allow simple search" is selected, DbSearch is disabled. This allows the administrator to prevent searches against large databases, when it is not desirable to create new views or a full text index. If this option is selected, DbSearch code returns an error.
I can't find any documentation for the design compression stuff. I know this was discussed at Lotusphere, but in a session I missed. Anyone who has details, please speak up!
Comments
<br />
<br />It's also referenced in the ND8 reviewers guide PDF file here. { <a href="{ Link } rel="nofollow" target ="blank">Link</a> }
<br />
<br />The feature will compress the DB design elements to use less space.
<br />Rob
Posted by Rob Ingram At 10:36:08 AM On 03/12/2007 |
I would think the new option relates to resilient threads as demo'ed in Notes 8 email (thread doesn't break if a doc in the middle is broken).
As you noted "Don't support specialized response hierarchy" has been around for a few versions now. Side effect of its selection is that certain code won't work (@Formulae like @IsResponseDoc or LotusScript methods like NotesDocument.Reponses). So it should only be selected if a database has no response structure at all.
Assuming that's correct, the "old" option could use a rename. "Specialized" throws me off, especially considering resilient threading. "Basic" is probably a better fit.
Which leads to another question. Does thread history work--assumed by me to be resilient threading--even if basic/specialized threading is turned off? If not, the "thread history" option should be a conditionally selectable sub-option under basic, rather than in independent option (i.e. grayed out unless basic is selected, like some of the sub-options on the Design tab of Database properties).
OK, enough rambling. May as well get confirmation that Thread History==Resilient threading before going on...and on...
Posted by Rod Stauffer At 03:01:33 PM On 03/12/2007 |