Beginning in OnBase 18, a change has been made to the database logic to improve batch processing performance. If you are upgrading from a version of OnBase prior to OnBase 18, batches that were committed in earlier versions of OnBase will not be visible in the Committed batch status queue unless you manually migrate these batches to the appropriate database table. To migrate these previously committed batches and make them visible, in the OnBase Configuration module, select Utils | Upgrade Data | Migrate Committed Scan Batches. Once the migration is complete, a confirmation message is displayed.
Once the committed batches are migrated to the new database table, they will no longer be visible to users on a previous version of OnBase. If users need to access these batches, their Client workstations must be upgraded to the new version at the same time as the database.
When migrating scan batch data, note the following:
-
Batches committed in OnBase 18 are automatically migrated to the appropriate database table and are thus visible in the Committed batch status queue.
-
Migrating committed batches from older versions of OnBase makes these older batches visible in the OnBase Client and the Unity Client.
-
While an in-progress batch migration can be canceled, this cancellation does not roll back the entire migration process. Batches that have already been migrated to the new database table remain there, even if the full migration process is not completed.