Released on Feb 5, 2025

New Features

The user migration step now:
- Syncs a user’s enabled status (i.e., “AllowLogon”) from staging.
- Trims leading and trailing spaces from user IDs.
Existing document classes are now updated by the document class migration step instead of skipped.

Fixed Issues

CMPPW-1231: When migrating My Favorites categories and shortcuts to an imanage.work/on-premises Work server, categories and shortcuts are created in the current library.
CMPPW-1233: After enabling “Retain Container IDs” and entering the credentials for a valid system user account, workspace, and folder migrations steps immediately failed with a “No sync client available” until the project is re-opened.
CMPPW-1234: Folder, document, recent document/workspace, security, or document history migration steps, the job can fail with the error “This row has been removed from a table and does not have any data. BeginEdit() will allow creation of new data in this row.”
CMPPW-1236: When migrating My Matters matter shortcuts, shortcuts to matters located in other libraries are not migrated if their reference project parent ID doesn’t exist in the current library.

When migrating to an imanage.work/on-premises Work server, you cannot sync My Matters/Favorites objects for users that are disabled in the target library. To work around this, prior to migrating any users, update CAM.DocUsers so that any user whose Matters/Favorites needs to be synced to the cloud has AllowLogon = 1. After the users have been created, you can disable them by setting their AllowLogon field to 0, updating their Synced field to the current time, and then running the user migration step again to apply the changes.