Deploy Additional Metadata
Download unmanaged permission sets and approval processes from the additional metadata folder in Static Resources. Set up approval processes for custom objects; and get object and field permissions for standard and custom objects using the unmanaged permission sets.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
Install Salesforce CLI and authorize it for use with your Salesforce org using the command:
sf org login web --alias ALIAS
Here are the steps to deploy additional metadata:
If you're an upgrade customer, to prevent overwriting your customizations to the existing approval processes and permission sets, we recommend cloning them before deployment of additional metadata. Post deployment, keep the deployed unmanaged metadata inactive, use it as a reference, and make the required changes manually to your cloned version. Post applying the changes on the cloned version of permission sets and approval processes, make sure to activate the approval processes. You can skip cloning and apply the changes manually if you don’t have any customizations made.
To deploy additional metadata:
- From Setup, in the Quick Find box, find and select Static Resources.
-
Deploy the cgcloud__additional_metadata file. The
downloaded cgcloud__additional_metadata file contains another .zip
file in it.
- For Windows users, after you extract the cgcloud__additional_metadata.zip file, you can see another zip file named additionalMetadata.zip. Extract this file. You can see these folders: permissionsets, approvalProcesses, and a new file named package.xml. Add both the folders and the package.xml file into a new folder named additionalMetadata.
- For Mac users, after you extract the zip file, a new folder named additionalMetadata is available after the extraction.
- From the command prompt, go to the folder that contains the additionalMetadata folder.
-
Deploy the additionalMetadata folder by using this Salesforce CLI command:
sf project deploy start --metadata-dir additionalMetadata --target-org ALIAS --wait 5During deployment, unmanaged permission sets and approval processes are created.
Important Group: All Internal Users is the default value in the Initial Submitter field for approval processes of Orders and Customer Tasks. Any user other than the creator can submit the order or task for approval. Review the approval processes and if necessary, tailor them based on business needs. We recommend keeping the Initial Submitters field as Group: All Internal Users for the approval processes. See Specify Who Can Submit Records to an Approval Process.If you're new to Summer ’25, turn on the CGCloud: Order Approval for Mobility Flow. This starts the approval process for orders that are created and synced from the Consumer Goods Cloud offline mobile app.
If you’re upgrading to Summer ’25, in Approval Processes under Setup, review the Initial Submitter field and update the Initial Submitters field from Record Creator to Group: All Internal Users for Orders and Customer Tasks.
Check the metadata deployed in your org. For example, to verify whether the permission sets are deployed, from Setup, find and search for permission sets, and then check whether the new permission sets are available.
- Approval Processes for Direct Store Delivery (DSD) and Van Sales
Similar to Retail Execution orders, all Direct Store Delivery and Van Sales orders are set to Ready status after drivers complete their order on the offline mobile app and the order's approval processes are completed. Here are considerations made while setting up direct approval processes of the Advance Orders object shipped as part of Static Resources for Direct Store Delivery and Van Sales.
