TRIM Captura to TRIM Context Upgrade Notes - TRIM User Network

More documents

Recommendations

Info

TRIM Captura to TRIM Context Upgrade Notes - TRIM Context 6.1 Page 20 Data Conversion Notes • Client and Server Upgrades - The recommended upgrade process is to upgrade all Client computers before upgrading the Server computers. • Database (RDBMS) Upgrades - There are no specific TRIM requirements to consider when upgrading your RDBMS software, other than to ensure the new RDBMS software version is included as a validated and supported version for TRIM. Refer to your online help under the "Relational Database (RDBMS) Client and Server Requirements". Follow the requirements specified by the upgrade documentation provided by your RDBMS vendor. • SQL Server Database Upgrades - For upgrades of SQL Server databases from TRIM Captura to TRIM Context, the SQL Server compatibility level must be set to 80. • Document Content Index Conversion Issues - TRIM Captura databases which use the 'Main Document Store' when converted will point to the directory specified in the Path for Default Electronic Store field. If this is not the same directory, the documents held in the store will need to be copied or moved to the new store OR the store path changed to the new directory. You may move the documents manually or you may use the Electronic Document Stores - Transfer Documents function in TRIM Context. Alternatively you may use the %db% path statement for the global path. • Document Final Flag - In an upgrade from TRIM Captura to TRIM Context, the 'final' flag’s 'Date Finalized' field is set to the ‘Date Registered’ date. • Space Management System Captions - When upgrading a TRIM Captura Space Management System to TRIM Context, the Level descriptions are maintained during conversion. This will result in all levels being regarded as captioned. For more information about Space Management Captions, see the TRIM Context Help file – Administrator Guide – Ch 18 Space Management – Space System Caption Editor. • Record Types - If a Record Type is set to use an Electronic Document Store in TRIM Captura, it will be converted to a Document Record Type in TRIM Context. If a Record Type is set to level 4 or above in TRIM Captura, it will be converted to a Folder Record Type in TRIM Context. • Record Type Security Groups - During a TRIM Captura to TRIM Context upgrade, all Record Type Security Groups are converted to Groups. The use of TRIM Captura Record Type Security Groups and Access Controls will require reviewing in TRIM Context after the conversion process is complete, because these functions have been significantly enhanced. Record Type Security Groups are created as new Locations called ‘Converted Group ##’. These converted Groups can be found in Locations using the
TRIM Captura to TRIM Context Upgrade Notes - TRIM Context 6.1 Page 21 Groups filter. The converted Group will display the TRIM Captura 4.3 Security Group name in the notes field of the converted Group Location to help determine which TRIM Captura Record Type Security Group it was created from. A number of converted Groups maybe created for each Record Type Security Group as a converted Group is required for each TRIM Captura access permission set (for example, if a Record Type Security Group has access of ‘Create/Remove’ for one Record Type then ‘Read Access’ for another Record Type then two converted Groups will be created). The conversion process will automatically associate the converted Group to the Record Type Access permission, however it is recommended that these converted Groups be renamed. An upgrade from TRIM Captura creates a new "Converted Group" for every combination of Access Controls on records. Groups (for example, "Converted Group #nn") are not created for Record Access Controls and Classification Plan Access Controls. Instead, the conversion will place the locations directly against a record or Classification Plan entry. The value for the "Contribute Contents" Access Control will be set to 'Everyone' as part of the conversion. • Word Indexing - If users wish to search for indexed words that are part of an e-mail address or web address, then the Administrator should re-index the words in the upgraded TRIM Context dataset, otherwise words that are preceded by special characters such as the at symbol and forward slash will not be indexed. This is because the algorithm for indexing words is different between TRIM Context and TRIM Captura 4.3. For information on how to reindex the words in a dataset, see the TRIMTEM Help file, TRIM Context Enterprise Manager - Datasets Setup and Maintenance - Dataset Options - How to Reindex Words. For information on the word indexing algorithm, see the TRIM Help file, Chapter 22 - Word Indexes - Word Indexing Rules and Behavior.
Page 1 and 2: TRIM Captura to TRIM Context 6 Upgr
Page 3 and 4: TRIM Captura to TRIM Context Upgrad
Page 21: TRIM Captura to TRIM Context Upgrad

TRIM Captura to TRIM Context Upgrade Notes - TRIM User Network

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?