Loading
Mail Delivery Issue Impacting Email to Salesforce UsersRead 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
            Set Up and Deploy a Major Release Version

            You are here:

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

            Set Up and Deploy a Major Release Version

            Create branches for the target upgrade release, for example, 248-core and 248-cust. Retain the source release branches (246-core and 246-cust) for existing users running the application on version 246.

            Required Editions

            Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled.
            User Permissions Needed
            To set up Git repo: Customizer, Admin

            When an upgraded version of design contracts is available from a subsequent major release, set up your Git repository and branches as shown in this workflow. For example, upgrade from Winter’24 to Spring’24 (246.4 → 248.0)

            Important
            Important Follow the guideline for your git branches and have dedicated branches for Salesforce core contracts and you customizing contracts. In case you have not segregated core and cust branches there are risks to override your customization parts.
            Git setup workflow for upgrade release.

            On the new branches, you can integrate the new features, and implement and test the new custom features without affecting the support lines. After all work on the 248-cust branch is complete, create a Deployment.zip of that branch and upload to the production Salesforce org to distribute the changes to all users.

            1. Create a branch for the target version (248-core) based on the existing source version branch (246-core).
            2. Create a feature branch based on the target version branch (248-core) to update the core contracts.
            3. Delete the src folder of the workspace. Then, import the core design contracts into the feature branch by running this command: sf modeler workspace utils importContracts -i DesignContracts.zip
            4. Create a pull request against the 248-core branch.
            5. Create a branch for 248-cust based on the existing 246-cust branch.
            6. Create a feature branch to update the contracts in your customizing branch.
            7. Merge the 248-core branch into 248-cust-update-248-0.
            8. Resolve merge conflicts locally, if any. You can test the changes made as part of the merge resolution in the feature branch.
            9. When the merge is successful, run the necessary tests and pull the changes from the 248-cust branch.
             
            Loading
            Salesforce Help | Article