--- schema_version: "1" id: 4809154517ba8e52022d882d665e6296a28efa152d8e8a35be413a752c5737c3 title: Review the Assessment Reports (Vlocity Industries Managed Packages and Custom Data Model) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_migrate_review_assess_reports.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_migrate_review_assess_reports.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 9cbf95955ec44dcbda2b89ef705aba74adf9b488794c80ec15ea5ad7fc50eead description: When you run the Omnistudio Migration Assistant in Assess mode, it generates assessment reports for Omniscripts, Flexcards, Data Mappers, Integration Procedures, Apex Classes, Omni Global Auto Numbers, FlexiPages, Experience Cloud Site Pages, Lightning Web Components, and Custom Labels. These assessment reports highlight several key areas that require attention before migrating Omnistudio components. products: - Omnistudio release: "264" --- # Review the Assessment Reports (Vlocity Industries Managed Packages and Custom Data Model) When you run the Omnistudio Migration Assistant in Assess mode, it generates assessment reports for Omniscripts, Flexcards, Data Mappers, Integration Procedures, Apex Classes, Omni Global Auto Numbers, FlexiPages, Experience Cloud Site Pages, Lightning Web Components, and Custom Labels. These assessment reports highlight several key areas that require attention before migrating Omnistudio components. The reports contain these assessment statuses: - **Ready for migration**: The component is ready for migration without any manual updates. - **Warnings**: The tool applied updates to the component, and the component is ready for migration. - **Needs manual intervention**: The component requires manual updates or fixes before migration. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_important.png) Important If you have any components with the **Needs manual intervention** status, click the **Call to Action** button and follow the instructions to resolve the issue. If you do not resolve the issue, the Omnistudio Migration Assistant does not migrate those components. - **Failed**: The component cannot be migrated due to technical errors. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png) Note If you have any components with **Failed** status, contact Salesforce Customer Support. ![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_important.png) Important Make sure that all records listed in the Assessment Status column of the Assessment Report are marked as either **Ready for Migration** or **Warnings** before proceeding with the migration. ## Omniscripts Assessment Report The Omniscript assessment report contains information about Angular Omniscripts, name changes, duplicate Omniscripts, and dependencies on Data Mappers, Integration Procedures, Flexcards, and LWCs. It also provides details on how the Omnistudio Migration Assistant updates them. Review the report and take action: - Angular Omniscripts: The Omnistudio Migration Assistant does not migrate Angular Omniscripts. To migrate Angular Omniscripts, convert them to LWC Omniscripts. See [Convert an Angular Omniscript to an LWC Omniscript](https://help.salesforce.com/s/articleView?id=xcloud.os_convert_an_angular_omniscript_to_an_lwc_omniscript.htm&language=en_US&type=5). - Type and subtype with special characters: The type or subtype of an Omniscript can contain only alphanumeric characters. During assessment, the Omnistudio Migration Assistant identifies any type or subtype that includes special characters and notifies you. During migration, the tool automatically updates them by removing the special characters. Example: - Before: CreateQuotePolicy\_Date\_Nominee - After: CreateQuotePolicyDateNominee - Before: One Time Payment - After: OneTimePayment - Duplicate Omniscripts: The Omnistudio Migration Assistant does not migrate multiple Omniscripts with the same name. To continue with the migration, you must rename all duplicate Omniscripts. - Data Mapper and Integration Procedure dependencies: The report lists the Data Mappers and Integration Procedures used in each Omniscript. Review the report to identify how these components in the Omniscripts are impacted by migration. ## Flexcards Assessment Report The Flexcards assessment report contains information about name changes, dependent Omniscripts, Integration Procedures, and Data Mappers in each Flexcard. It also provides details on how the Omnistudio Migration Assistant updates them. Review the report and take action: - Name with special characters: The Flexcard name can contain only alphanumeric characters. During assessment, the Omnistudio Migration Assistant identifies any name that includes special characters and notifies you. During migration, the tool automatically updates Flexcard names by removing these special characters. Example: - Before: insAccountChild\_nds - After: insAccountChildnds - Omniscript, Data Mapper, and Integration Procedure dependencies: The report lists the Omniscripts, Data Mappers, and Integration Procedures used in each Flexcard. Review the report to identify how these components in the Flexcard are impacted by migration. ## Data Mappers Assessment Report The Data Mappers assessment report contains information about name changes, duplicate names, custom functions, and Apex classes in each Data Mapper. It also provides details on how the Omnistudio Migration Assistant updates them. Review the report and take action. - Name with special characters: The Data Mapper name can contain only alphanumeric characters. During assessment, the Omnistudio Migration Assistant identifies any name that includes special characters and notifies you. During migration, the tool automatically updates them by removing the special characters. Example: - Before: auto\_DriverContact\_IP - After: autoDriverContactIP - Duplicate Data Mappers: The Omnistudio Migration Assistant does not migrate multiple Data Mappers with the same name. To continue with the migration, you must rename all duplicate Data Mappers. - Custom Function dependencies: Omnistudio Migration Assistant updates all custom functions defined using the `FunctionDefinition__mdt` custom metadata in the managed package runtime to the `FUNCTION(“ClassName”, “MethodName”, args)` syntax. Example: - Before: `REPLACE(targetString, replacementString)` - After: `FUNCTION(“CustomStringFunctions”, “replace”, targetString, replacementString)` - Apex dependencies: The report lists the Apex classes used in each Data Mapper. Review the Apex assessment reports for identifying how these Apex classes are impacted by migration. ## Integration Procedures Assessment Report The Integration Procedures assessment report contains information about name changes, duplicate names, and dependencies on other Integration Procedures, Data Mappers, and remote actions. It also provides details on how the Omnistudio Migration Assistant updates them. Review the report and take action. - Type and subtype with special characters: The type or subtype of an Integration Procedure can contain only alphanumeric characters. During assessment, the Omnistudio Migration Assistant identifies any type or subtype that includes special characters and lists them in the assessment report. During migration, the tool automatically updates Integration Procedure type and subtype by removing these special characters. Example: - Before: Policy Submit - After: PolicySubmit - Duplicate Integration Procedures: During assessment, the Omnistudio Migration Assistant identifies multiple Integration Procedures with the same name and lists them in the report. To continue with migration, you must rename the duplicate Integration Procedures. - Data Mapper and Integration Procedure dependencies: During assessment, the Omnistudio Migration Assistant identifies the Data Mappers and Integration Procedures that are used in each Omniscript, and lists them in the report. Review the Data Mappers and Integration Procedures assessment reports for identifying how these components in the Integration Procedures are impacted by migration. - Remote Actions: During assessment, the Omnistudio Migration Assistant identifies the remote actions that are called in the Integration Procedures, and lists them in the report. Review the Apex Assessment report for identifying how these components in the Integration Procedures are impacted by migration. - Reserved words: Check your Integration Procedures for reserved words and refactor them if needed. Remove these reserved words, if used: `Request` and `Response`. ## Apex Assessment Report The Apex assessment report lists the Apex classes that use remote actions with their file reference, comments, and errors. It also shows the file diff of changes made to the Apex classes by the Omnistudio Migration Assistant during migration. In the managed package runtime, you implement the `VlocityOpenInterface` class in any Apex class that uses remote actions. During migration to standard runtime, the Omnistudio Migration Assistant replaces the <`namespace>.VlocityOpenInterface` or `namespace`.`VlocityOpenInterface2` with the `System.Callable` class. The Omnistudio Migration Assistant performs these updates to the Apex class: - Replaces any instances of `.VlocityOpenInterface or` `namespace`.`VlocityOpenInterface2` with `System.Callable.` - Adds this code to the class: ``` public Object call(String action, Map args) { Map inputMap = (Map)args.get('input'); Map outMap = (Map)args.get('output'); Map options = (Map)args.get('options'); return invokeMethod(action, inputMap, outMap, options); } ``` ## Omni Global Auto Numbers Assessment Report The Omni Global Auto Numbers assessment report lists all the Omni global auto numbers in your org that are ready for migration. Verify the list and status of these components. See [Omni Global Auto Numbers](https://help.salesforce.com/s/articleView?id=xcloud.os_standard_global_auto_number.htm&type=5&language=en_US). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/images/icon_note.png) Note Omnistudio Migration Assistant does not remove special characters from the Omni Global Auto Number names during migration. ## FlexiPages Assessment Report The FlexiPages assessment report lists the components that use `:vlocityLWCOmniWrapper`. During migration, `:vlocityLWCOmniWrapper` is replaced with Omnistudio standard wrappers (for example, `runtime_omnistudio:omniscript`). The component attributes such as name, type, subtype, and language are also updated during migration. The report also lists updates to references that use runtime\_omnistudio:omniscript, which contain special characters in type and subtype. ## Experience Cloud Site Pages Assessment Report The Experience Cloud site pages assessment report lists the components that use `:vlocityLWCOmniWrapper`. During migration, `:vlocityLWCOmniWrapper` is replaced with Omnistudio standard wrappers (for example, `runtime_omnistudio:omniscript`). The component attributes such as name, type, subtype, and language are also updated during migration. The report also lists updates to references that use runtime\_omnistudio:omniscript, which contain special characters in type and subtype. ## Lightning Web Components Assessment Report The Lightning web components assessment report lists the Lighting web components (LWCs) that use a ``. During migration, the `` is replaced with the `c` namespace. Additionally, the report lists the `namespace` tags. During migration, the tags are removed from the `*.js-meta.xml` file. LWCs that fall under these categories are not assessed and are excluded from the assessment report: - Auto-generated Omniscript LWCs containing `Omniscript Auto-generated` in js-meta.xml: When you have an Omniscript in a managed package, activating it creates a backend LWC automatically. These auto-generated LWCs are not assessed. - Auto-generated Flexcard LWCs prefixed with `cf`: When you have a Flexcard in a managed package, activating it creates a backend LWC automatically. Flexcard LWCs that are prefixed with `cf` are not assessed. - Omniscript component directory prefixed with `Omniscript`: Omniscript LWCs with this prefix are not assessed. - Language variant directories suffixed with `MultiLanguage` or `English`: LWCs in directories with these suffixes are not assessed. - Utility component directory containing `Util`: LWCs in a directory containing `Util` are not assessed. - `lodash` library directory containing `lodash`: LWC directory or metadata that references `lodash` is not assessed. - Definition files containing `_def, definition, styleDefinition`: Definition files that `contain _def, definition,` or `styleDefinition` are not assessed. ## Custom Labels Assessment Report The custom labels assessment report lists custom labels with warnings or failures that require your attention. For labels that pass successfully, the report only shows the total count and not each label individually.