Backend Features and Performance Improvements in Summer '20
In its constant desire for improvement, Copado has introduced new features and enhancements in the backend since the last release. These features not only involve an improvement in the time spent executing Copado tasks such as committing or retrieving metadata but they also allow you to better handle your work with Copado.
- The Full Profiles & Permissions Sets Git operation runs faster for permission sets since all permissions set to false are no longer committed.
- Profile and permission set deployments no longer include user permissions that Salesforce does not allow to deploy, such as multiforce, thus making deployments faster.
- Faster metadata retrieve in orgs with big metadata enabled by using multiple Salesforce APIs for different metadata types.
- By default, when you manually create a promotion whose destination is the last environment in your pipeline and then manually create the deployment, Copado automatically calculates and displays the user stories that have been promoted to that environment and have not been back-promoted to other lower environments. As of Summer ‘20, you have the option to disable this calculation by editing a custom metadata type, which will speed up the creation and execution of deployments. For more information about how to disable the calculation, check out the article How to Create a Promotion.
- The Destructive Changes Git operation now supports deleting Field Sets.
- There is a new webhook that allows you to create branches in your Git repository to automate advanced use cases, like for example adding a new org to the Copado pipeline while creating the org’s branch in Git.
- Retrieving Vlocity dependencies now runs up to 20 times faster in commits and deployments, especially in large Vlocity implementations.
- You can now filter the types of Vlocity components that are retrieved during a snapshot, to have better control of which Vlocity metadata types get included in Git.
- The commit webhook for user stories now supports Vlocity components.
- Vlocity components can now be deployed with Continuous Integration.
- Copado now supports the parameter @maxDepth=-1 in the commit page when committing Vlocity components.
- If there is an error while deploying Vlocity components, logs will be attached to the MetaData deployment step so that you can review and troubleshoot the issues. Alternatively, you can add @debug to the deployment name to review Vlocity logs regardless of the deployment status.
- When working with Vlocity, there are different Vlocity custom settings that help you troubleshoot specific issues. Copado now allows you to specify your own Vlocity custom settings and add them to the Environment record using a YAML file.