-
History changes should not be tracked unless necessary. When configuring an attribute, the Track changes checkbox should be unchecked if there's no business need for seeing changes to that attribute. This is especially true of Text, Formatted Text, and Alphanumeric attributes greater than 255 characters.
-
When configuring a Dynamic Folder, use the Document Type Query option. When creating a Dynamic Folder, use the Document Type Query option when possible. This limits document search to the specified Document Type(s) rather than every single Document Type that a keyword is associated with.
-
Considerations should be given to server performance when setting WVMaxResults key in web.config. When configuring the WVMaxResults key in the OnBase Web Server's web.config, care should be taken not to set this to a very high value. Setting this to a very high value may cause users to experience slow response times when executing filters.
-
Configure lookup Filters with User Entry Constraints. If a lookup filter on a relationship attribute is likely to return a very long list of results, it is recommended that you configure a User Entry Constraint so that users can search for specific items instead of returning a long list of items.
-
Purge inactive items after performing a “Test mode only” Class data import operation. After performing a Test mode only import, although objects are not activated (displayed on filters), they are created in the database and marked as inactive. Use the Purge inactive/deleted items feature to purge inactive items from the database. This will free up some space that is used by the inactive items created during the test import.
-
Allocate appropriate database space for attributes. When configuring attributes, allocate the number of spaces that will fit the data users will enter. For example, if the “ZipCode” only will have a maximum of 15 characters, do not allocate 100 characters for the “ZipCode” field.