Library 2.0 Setup
Pre-requisites
If you are on the latest library release with the legacy responses (records), you must migrate the responses from App Launcher > search and select LFS Configuration > New Library 2.0 Setup tab. This tab is only available for administrators.
After upgrading to the latest package, the admin can deploy new picklist values (Draft) in the global value set (Response Status) using the Setup Metadata for Library 2.0 button, and initiate the library migration batch job using the Initiate Library 2.0 Migration button under the New Library 2.0 Setup tab.
The two options that help you manually deploy the picklist values and migrate the responses are as follows:
Setup Metadata for Library 2.0
Initiate Library 2.0 Migration
To perform New Library 2.0 Setup
Go to the App Launcher, search, and select LFS Configuration.
You will be landed to the New Library 2.0 Setup page.Click the Setup Metadata for Library 2.0 button to deploy new picklist values.
A successful setup message appears on the top.Click the Initiate Library 2.0 Migration button to migrate the legacy library data.
A message shows that the migration job has been scheduled and you can track the status under Setup > Apex Jobs(ResponseMigrationBatchService).
The field dependency between the Status and Status Category picklist fields has to be removed manually if need be.
Important
For Setup Metadata for Library 2.0 to work, you must have View Setup and Configuration permission.
Please contact your System Administrator to Initiate Library 2.0 Migration.
Field Mapping after Migration
Following migration, the data would be populated in the respective objects' fields as displayed in the Value column.
Field | Value | |
|---|---|---|
Response | First Published By | Response Created By |
First Published Date | Response's Response Operation Last Modified Date / Created Date of Response | |
Last Published By | Response Created By | |
Last Published Date | Response's Response Operation Last Modified Date / Created Date of Response | |
Publish Reason | Library Migration Publish | |
Project Question | Response Version | Active Response Version of Response |
Last Modified Date Backup | LastModifiedDate of Project Question before migration | |
Last Modified By Backup | LastModifiedBy of Project Question before migration | |
Last Modified Date | Date/time when the migration is run successfully | |
Last Modified By | User who initiated the batch for Project Question and Response records. |
Once you upgrade the package to the latest library release, the existing records are still not migrated and have to be done manually as discussed above. If any of the users access these legacy records before migration, they will see a warning message “After the most recent library release update, some legacy library records are found in the system which are not yet migrated. Loopio advises against making any changes to old responses. So, kindly migrate these records by clicking the Setup button” on the Response Library and Responses object pages.