1,126
edits
Difference between revisions of "Migrating From Filenet to Content Manager OnDemand"
Migrating From Filenet to Content Manager OnDemand (view source)
Revision as of 07:08, 11 February 2017
, 07:08, 11 February 2017Clarified Application definition.
m (Minor changes to the Filenet to IBM CMOD Migration) |
m (Clarified Application definition.) |
||
| Line 29: | Line 29: | ||
; Application (aka "App") | ; Application (aka "App") | ||
: Defines the type of document (AFP, Line data, PDF, Image), and how to collect | : Defines the type of document (AFP, Line data, PDF, Image), and how to automatically collect metadata (aka 'indexes') that will be used as search criteria by end users, for storage in the database. | ||
: Multiple Applications of any data type (ie, AFP for customer statements, Line data reports generated by a mainframe, special letters or notices in PDF format, and incoming faxes stores as TIFF images). | : Multiple Applications of any data type (ie, AFP for customer statements, Line data reports generated by a mainframe, special letters or notices in PDF format, and incoming faxes stores as TIFF images). | ||
; Folder | ; Folder | ||
: The Folder in OnDemand abstracts the internal complexities of Application Groups and Applications, and presents users with the fields that they can search (which were populated into the database by the Application) and sets limits on their queries (maximum number of returned hits, fields required for searches, etc.) | : The Folder in OnDemand abstracts the internal complexities of Application Groups and Applications, and presents users with the fields that they can search (which were populated into the database by the Application) and sets limits on their queries (maximum number of returned hits, fields required for searches, etc.) | ||
== Considerations == | == Considerations == | ||