Migration
The Migration module is the data and image exporting stage of processing a batch. The product currently migrates data in over 60 different formats with many configurable options for each. All levels of index data, scanned images, and OCR output can be sent to a target location in a local or remote document management system, database, or folder, all depending on which migration method is being applied.
Migration to multiple formats or products is supported. When more than one migration target is selected and added to the workflow (see "Migration Settings" below), each migration is executed sequentially from the top of the list to the bottom. Furthermore, multiple migration stages can be added to the workflow if data needs to be partially migrated, edited, or checked, and then completely migrated. Each migration stage has its own set of migrations to process with different rules, but for most scenarios, one Migration step is sufficient.
For links to specific details on configuring migrations that PSIcapture can process, see the list of available migrations below.
The Migration Settings dialog box opens immediately after adding a Migration step to the workflow. It has two tabs:
-
General (default)
General
This tab lists migrations that are available to be added and currently configured migrations too.
-
The list of Available Migrations features all the migrations that can currently be used in the product.
Some migrations have Direct support, and are named as such. This indicates that PSIcapture directly connects to the target system and uploads the batch data in the native format of that system.
Other migrations have Flat support, which applies to migrations with a lack of "Direct" in the name. This indicates that PSIcapture migrates a file/folder format that is expected by the target product without establishing a direct connection to that product. That exported data can then be imported by the target product.
-
The list called Migration workflow features all the migrations that have been added to the current Migration step. Some notes on the behavior of this list:
-
Migrations to a single product or generic format can be configured multiple times (for example, you may have two separate FTP migrations in the workflow).
-
Migrations can be duplicated with identical settings.
-
During batch processing, the migrations are processed in sequence from top to bottom.
-
Exception processing alters the way the list behaves when a migration fails.
-
| Button | Description |
|---|---|
| Add | Adds the selected migration to the workflow and opens its configuration dialog box. Active only when a migration in the Available Migrations list is selected. |
| Remove | Removes the selected migration from the workflow and discards all configuration data. Active only when a migration in the Migration Workflow list is selected. |
| Move Up | Moves the selected migration up in the Migration Workflow list. |
| Move Down | Moves the selected migration down in the Migration Workflow list. |
| Copy | Copies the selected migration in the Migration Workflow list and all its settings. Opens the configuration dialog box for that migration to confirm its settings. |
| Configure | Opens the configuration dialog box for the selected migration in the Migration Workflow list. Can also be opened by double clicking the list item. |
For a full list of currently supported migrations, see Currently Supported Migrations.
Other migrations are not product-specific. They are available for situations where a simple flat file or a connection to a local or remote database serves as the migration target.
-
Database (Access, SQL server, Oracle, ODBC-compliant databases)
-
Email
-
Folder Export
-
FTP
-
Text
-
XML
Exception Processing
This tab handles all settings for all migrations configured in this individual instance of the Migration workflow step. A profile with two or more Migration steps that both require exception processing must have these settings configured separately for both.
Enable exceptions processing: Activates exception processing for this Migration step. Enables the following options:
-
Stop migrating when Document fails to migrate...: While using Automation, a batch halts in the Migration step if any of the migrations fail.
-
Automatically reject Documents...: An exceptions batch is automatically generated when a migration fails, and the Migration step continues processing.
-
Send exceptions Batch to previous workflow step: Move the exception batch to the selected step. You can only select workflow steps that are added to this profile (for example: Capture, Index, QA).