1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Jump to navigation
Jump to search
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 15:28, 15 October 2015
, 15:28, 15 October 2015Added Reconciliation.
(Added section on handling blank fields) |
(Added Reconciliation.) |
||
| Line 51: | Line 51: | ||
There's no better time to review the contents of reports, and refer with end users to determine which reports should be stored, indexed, managed, and disposed of in the same manner. Put on your Business Analyst cap and strap on your most comfortable telephone headset, because this is the most time consuming and manual part of the whole process. | There's no better time to review the contents of reports, and refer with end users to determine which reports should be stored, indexed, managed, and disposed of in the same manner. Put on your Business Analyst cap and strap on your most comfortable telephone headset, because this is the most time consuming and manual part of the whole process. | ||
=== Reconciliation === | |||
In order to reconcile the documents after the migration is complete, you'll want to have a unique identifier for each document that needs to be moved out of FileNet and into CMOD. Thankfully, FileNet provides a unique 'Document Indentifier' or "DocID" -- which can be loaded into CMOD by adding a corresponding field in the Application Group definition. The DocID field doesn't need to be added to CMOD folders, so it can remain invisible to end users, or exposed to a different folder to be used with existing tools that use them. | |||
== Differences in Functionality == | == Differences in Functionality == | ||