Loading
Feature degradation | Gmail Email delivery failureRead More
Visual Studio Code Based Modeler for Consumer Goods Cloud
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Migrate Windows Server Based Modeler Contracts to Visual Studio Code Based Modeler

            You are here:

            1. Salesforce Help
            2. Docs
            3. Visual Studio Code Based Modeler

            Migrate Windows Server Based Modeler Contracts to Visual Studio Code Based Modeler

            Migrate contracts from an existing project in Windows Server based Modeler to the latest version of VS Code based Modeler.

            Required Editions

            Available in: Enterprise and Unlimited Editions that have Consumer Goods Cloud enabled.
            User Permissions Needed
            To migrate to VS Code Modeler Customizer, Admin

            Use this workflow to set up your Git repo and migrate the contracts of your project from Windows Server based Modeler to a latest version of VS Code based Modeler. For example, migrate from Spring’XX version of Windows Server based Modeler to Summer’XX version of VS Code based Modeler.

            Git setup for users of Windows-based Modeler migrating to VSCode based Modeler..
            1. Update your customizer branch in Windows Server based Modeler with the latest core Modeler Content Package (MCP.zip) of SpringXX.
              1. Download the SpringXX core MCP zip from the Custom - Managed section of the Lightning App Builder and import it to the customizer branch in the Windows Server based Modeler.
              2. Resolve merge conflicts, if any.
              3. Export all the contracts of the project from the SpringXX customizer branch. From the Repository menu, select Export Contracts | Snapshot Version (Complete) and save the custom MCP locally.
            2. Create a Spring’XX-core branch in your Git repo, and then perform these steps in this branch:
              1. Create a workspace in this branch. Run sf modeler workspace create.
              2. Import the core contracts from the ‘contracts’ folder of the SpringXX Cust_MCP.zip to $workspace/src in the SpringXX-core branch. The custom contracts zip package includes the core contracts. Run sf modeler workspace utils importContracts -i <SpringXX-Cust_MCP.zip_filepath> -c
                This action transforms .core.xml files to .xml files. This action also transforms the XML business logic files to JavaScript (bl.js) files.
            3. Create a SpringXX-cust branch based on the SpringXX-core branch.
            4. In the SpringXX-cust branch, import the custom contracts to VS Code based Modeler syntax. Run sf modeler workspace utils importContracts -i <SpringXX-Cust_MCP.zip_filepath>
              This action transforms the XML business logic files to JavaScript (bl.js) files.
            5. Create a branch for the SummerXX-core based on the existing SpringXX-core branch.
            6. Create a feature branch based on the SummerXX-core to update the core contracts.
            7. Import the core design contract into the feature branch. Run sf modeler workspace utils importContracts -i <DesignContracts.zip_filepath>
            8. Create a pull request against SummerXX-core branch
            9. Create a branch for SummerXX-cust based on the existing SpringXX-cust branch.
            10. Create a feature branch to update the contracts in your customizing branch.
            11. Merge the SummerXX-core branch to SummerXX-cust upgrade branch.
            12. Resolve merge conflicts locally, if any. You can test the changes made as part of merge resolution in the feature branch.
            13. After the merge is successful, run the necessary tests and pull changes to the SummerXX-cust branch.
             
            Loading
            Salesforce Help | Article