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.
• 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 <namespace>.VlocityOpenInterface or namespace.VlocityOpenInterface2 with System.Callable.
• Adds this code to the class:

  public Object call(String action, Map<String,Object> args)
  {
      		Map<String,Object> inputMap = (Map<String,Object>)args.get('input');
      		Map<String,Object> outMap = (Map<String,Object>)args.get('output');
      		Map<String,Object> options = (Map<String,Object>)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.

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 <namespace>:vlocityLWCOmniWrapper. During migration, <namespace>: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 <namespace>:vlocityLWCOmniWrapper. During migration, <namespace>: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 <namespace>. During migration, the <namespace> is replaced with the c namespace. Additionally, the report lists the <runtimeNamespace>namespace</runtimeNamespace> 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.