Deploy Multiplay Subscription Management Components (Managed Package)

Migrate Salesforce Components

First, use the salesforce components 1 and community YAML files to migrate the Salesforce and Community components into your target org.

1. Use SalesforceComponents1.project.yaml to migrate the first set of Salesforce components from source to target org.
   1. Load the SalesforceComponents 1 YAML file that shows up in the IDX Project list.
   2. Don't migrate Profiles folder components while migrating the SalesforceComponents 1 YAML file. Migrate Profiles components after all SalesforceComponents 1 YAML file components migration is done.
   3. Click Migrate with Dependencies.
   4. Migrate flow components.
      

      Note

      Download the package.xml file and use this file to retrieve the flow components such as SFI_CreateFraudRecordAlert, SFI_NBABuyAddOn, SFI_NBACashTopUp, and SFI_NBARecommendationFlow. Use the Ant Migration Tool to migrate these flow components to your target org.

2. Before migrating the Community.project.yaml file, complete these steps:
   1. Load the Community yaml file in IDX Workbench.
   2. Select the Mobile_Subscription_Self_Service_Portal.site-meta.xml component under Sites folder on the left panel.
   3. Open the Comparison tab located beside the Migration tab in IDX Workbench.
   4. Click View Source.
   5. Change the <siteAdmin> and <siteGuestRecordDefaultOwner> entry to the login username of your target org.
   6. Also, if you find the <subdomain> entry in the IDX Comparision tab, update it to the domain name of your target org. If the <subdomain> entry is not there, skip this step. To get the domain name: From Setup, in the Quick Find box, enter My Domain, and then select My Domain.
   7. If there’s a server down entry like <serverIsDown>SNA_Mobile_Subscription_Self_Service_Portal1_sf_default_cdn_Iw8v5</serverIsDown>, remove this entry.
   8. Save your changes.
3. Use Community.project.yaml to migrate the Salesforce components required for the customer portal from source org to target org.
   1. Load the Community yaml file that shows up in the IDX Project list.
   2. Select all the components in the left pane and click Migrate with Dependencies.

Migrate Salesforce Industries/Vlocity Components

Migrate the Vlocity, product catalog, and record alerts components to your target org.

1. Use VlocityComponents.project.yaml to migrate the Salesforce Industries/Vlocity components required for MSM application from source to target org:
   1. Load the VlocityComponents yaml file that shows up in the IDX Project list.
   2. Select the components and click Migrate with Dependencies. Migrate the components in this order: Integration Procedures and Data Mappers, then, OmniScripts and Vlocity Cards, then all remaining components.
      

      Note Migrating these components can take a few hours.
2. Use ProductCatalog.project.yaml to migrate all the products and catalog-related artifacts:
   1. Load the Product Catalog yaml file listed under Project in IDX.
   2. Select all the components on the left pane and click Migrate with Dependencies.
      

      Note Sometimes product migration fails due to globalKey references or IDX config or target org configuration issues. Contact the IDX team to resolve the issue or check the IDX Troubleshooting page. You can also refer to the source org for products configuration and create them manually in the target org.
3. Use RecordAlerts.project.yaml to migrate components for the Alert feature.
   1. Load the Record Alerts yaml file listed under Project in IDX.
   2. Select all the components on the left pane and click Migrate with Dependencies.

Troubleshoot Migration

If you encounter any issues while migrating components, check these troubleshooting steps for help.

• Some component migrations can take close to two hours depending on bandwidth.

• If the component migration doesn’t progress after some time, reset the repository in IDX Workbench and try again as described in these steps:

  1. Click Debug on the IDX Workbench menu bar and then click Reset Repository Data.

  2. To fetch all the YAML file components, perform these steps:

     1. On the Configure Workspace window, under Repository, select the repository folder.

     2. Under Source, select your source org.

     3. Under Target, select your target org.

     4. Under Project, select the YAML file.

     5. Save your changes.

  3. Select all components and click Migrate with Dependencies.

• Retry migrating the non-migrated components multiple times.

• If you see an error on a component that says LWC activation failed, check to see if the component is available in the target org and activate the component manually.

• If you get LWC Activation errors where dependent cards are missing, perform these steps:

  1. Open IDX Workbench.

  2. Click the Configure Workspace pencil icon.

  3. Beside the Project field, click the Edit pencil icon and search for all the missing components.

  4. Move the components from All datapacks to Selected datapacks and save your changes.

  5. Click Save again to fetch the missing components and then remigrate with dependencies.

Post Migration of Salesforce Industries/Vlocity Components

Complete these post migration steps before migrating the next set of Salesforce components.

1. Verify OmniStudio FlexCards status:
   1. From the App Launcher, find and select OmniStudio FlexCards.
   2. Check if all the 'sfi' cards are active or not and if any of the FlexCards with 'sfi' prefix isn't active then activate only them. If there's any error in activating and if the error message indicates any missing dependent 'sfi' FlexCard, first activate that dependent FlexCard before activating the current one.
2. Activate the multi-language OmniScripts:
   1. From the App Launcher, find and select OmniScripts.
   2. Click the active version of the SFICashTopUp (Multi-Language) OmniScript.
   3. Click the dropdown arrow beside the Edit button. Click Open in Classic Designer.
   4. Click Script Configuration under the Structure section.
   5. Click Deactivate Version.
   6. Click Activate Version.
   7. Repeat the previous steps for these Multi-Language OmniScripts:

      • SFIBuyAddon

      • SFIChangeNumber

      • SFIChangePersonalDetails

      • SFICheckoutAndJoin

      • SFIManageFeatures

      • SFIManageLostandStolenDevicesorSIM

      • SFIRequestSIMUnlockCode

      • SFISIMReplacement

      • SFIVoucherTopup

3. Add Mobile Subscription Self Service Customer profile:
   1. From Setup, in the Quick Find box, enter All Sites, and then select All Sites.
   2. Beside Mobile Subscription Self Service Portal, click Workspaces.
   3. Click Administration.
   4. Click Members.
   5. Under Select Profiles section, select All in the Search dropdown.
   6. Add Mobile Subscription Self Service Customer profile.
   7. Save your changes.
4. Add Knowledge user and activate Knowledge setting in the target org:
   1. Add Knowledge user:

      • From Setup, in the Quick Find box, enter Users, and then select Users.

      • Beside System Administrator, click Edit.

      • Select the checkbox beside Knowledge User.

      • Save your changes.

   2. Activate lightning knowledge setting:

      • From Setup, in the Quick Find box, enter Knowledge Settings, and then select Knowledge Settings.

      • Select the checkbox and click Enable Salesforce Knowledge.

      • Click Edit.

      • Select both checkboxes under the Lightning Knowledge Settings section.

      • Save your changes.

5. Upload CSV files to decision matrices. If you have an Omnistudio Managed Package Runtime org, skip this step.
   1. Navigate to the MSM_sfdx_datapacks folder and extract the ‘DecisionMatrixData.zip’ file.
   2. From the App Launcher, find and select Decision Matrices.
   3. Click the Decision Matrices list view drop-down and select All Decision Matrices.

      • Click SFIAccessCheckMatrix.

      • On the Related tab, click SFIAccessCheckMatrix V1.

      • Click Upload CSV File.

      • Navigate to the MSM_sfdx_datapacks/DecisionMatrixData folder.

      • Select the SFIAccessCheckMatrix V1_2023-10-16 23_04_53.csv file.

      • Click Upload.

      • Click Done when the upload is complete.

      • Click Activate.

      • Go back to the Decision Matrices list.

      • Click SFIEligibilityMatrix.

      • On the Related tab, click SFIEligibilityMatrix V1.

      • Click Upload CSV File.

      • Navigate to the MSM_sfdx_datapacks/DecisionMatrixData folder.

      • Select the SFIEligibilityMatrix V1_2023-10-16 23_04_53.csv file.

      • Click Upload.

      • Click Done when the upload is complete.

      • Click Activate.

6. Remove Next Best Action or NBA component from the account flexi page in the source org:
   1. From Setup, in the Quick Find box, enter Lightning App Builder, and then select Lightning App Builder.
   2. Beside SFI-Account flexi page, click Edit.
   3. Click the blank box below the Knowledge FlexCard and click the delete icon.

Migrate Inter-Dependent Salesforce Components

Migrate the second set of the Salesforce components using the salesforce components 2 YAML file.