Winter '21 - Release Notes

Updated 5 months ago by Copado Solutions

Important: This is a major release. Please, read the Upgrade Instructions before upgrading, and follow them carefully afterwards. Test on a sandbox first.

The Winter’ 21 release includes all the features and enhancements that have been released from Summer ‘20 to date, including those features that have been released in the minor versions.

New Features and Enhancements in the Copado Deployer Package

Copado Platform

Copado Platform allows you to execute different automations and Salesforce flows as part of your deployment. This feature includes four major items:

  • Automation Templates: An automation template is a reusable template that contains a set of steps that can be executed in the future. This template can be used as part of a connection behavior (if you are working with Copado Continuous Delivery), but it can also be triggered in a deployment step or as part of a Salesforce flow. For more information about this, check out the article Automation Templates.
  • Salesforce Flow step: The Salesforce Flow user story task and deployment step bring a lot of power to your deployments by allowing you to execute a Salesforce flow and integrate with external APIs as part of your deployment. For more information about this feature, take a look at the article Deployment Step: Salesforce Flow.
  • Dynamic Variables: Copado has introduced a new set of dynamic variables that you can use when working with Salesforce Flow deployment steps. For more information about all the available variables and their use, check out the article Dynamic Variables.
  • Result object: There is a new object named Results where you can store all your external job results and test run results linked to user stories and deployments. This way, you won’t need to scroll endlessly down on the user story related lists to find your different test results or navigate to any other objects to find the results you are looking for. For more information about this object, check out the article Result Object.
Copado Data Deploy

There is a new version of Copado Data Deploy that contains new features and enhancements:

  • An automatic record matching functionality that allows you to build a formula that generates external Id values for the records that don’t have one in order to match them across all orgs in the pipeline, helping you avoid deployment failures and duplicate records. For more information, check out the article Automatic Record Matching.
  • An enhanced summary results table that includes a column with the Ids that have been generated by the new record matching functionality.
  • The relationship diagram now displays an icon next to the templates that have filters or record limits applied and attachment options selected. This way, you can easily identify which of the templates included in your main template have filters, record limits or attachments so that you can make the necessary adjustments before performing the deployment.
  • Support for filters in child templates. Now, if you deploy, for instance, accounts and their related contacts, Copado will not only apply the filters specified in the main account template, if any, but also those in the child contact template, giving you more control over the data that gets deployed and helping you avoid hitting governor limits.
Copado Core
  • There is a new checkbox in Custom Settings named Disable Auto-Resolve that allows you to disable the Auto-Resolve option from the online conflict resolution page. You can enable this checkbox if you want users to manually resolve conflicts rather than select the Auto-Resolve option. For more information about this feature check out the article Online Conflict Resolution.
  • There is a new checkbox in the Pipeline record named Enable Smart Conflict Resolution that allows you to enable or disable the Smart Conflict Resolution functionality, as desired. This checkbox will be selected by default. If enabled, Copado will apply the last conflict resolution strategy that was implemented through the Online Conflict Resolution feature and stored as an attachment in the Git Repository record to all subsequent promotions in the pipeline if the same conflict occurs.
    If the checkbox is disabled, Copado will still store conflict resolution strategies, but will not apply them to other promotions in the pipeline.

  • There is a new checkbox in the deployment information section, Attach Deployment File. When you select this checkbox, Copado automatically adds @debug to the deployment name and then generates the zip file that contains the logs with the deployment results so that you can further troubleshoot any potential issues.
  • There is a new field in environment variables named Scope that allows you to define and specify where a particular environment variable is applied. This field will be available in the Environment Variables related list in the Environment record. For more information about the different scopes you can define, check out the article Environment Variables.
  • There are two new Apex invocable methods:
    • Get User Story Count: Use this method to get the user stories ahead and behind count. This can be very useful if you are performing a validation before deploying and want to confirm if there are any user stories behind before actually executing the deployment.
    • Execute Automation Template: Use this method to execute an automation template.
      For more information about these methods, check out the article Apex Invocable Methods.
  • There are two new objects that can help you organize your user stories: Application and Feature.
    • The Application object allows you to organize sets of features and user stories that are tied to an application or product. Learn more in the Application Object article.
    • The Feature object allows you to track the lifecycle of a feature from request to delivery. Learn more in the Feature Object article.
  • A new picklist value named Callback URL has been added to the Dynamic URL Parameters field in the URL Callout deployment step. When you select this value, Copado builds a resume URL and sends it to the third-party tool involved in the callout step so that this third-party tool can easily update the job as completed or failed.
  • When you execute a deployment or a validation deployment from the Pipeline page, the Source Environment column is now displayed before the Destination Environment column to make it clearer what the source and destination environments of the promotion are.
Copado Continuous Delivery
  • Copado has introduced an enhancement in the user stories ahead and behind calculation that accounts for two use cases that were not previously covered:
    • You promote a user story to a higher environment, then move it back to the lower environment it came from in order to fix something and recommit. Copado will include this user story in the User Stories Ahead tab so that you can promote it again or it will automatically promote it if you are working with Copado Continues Delivery and have configured an automated or scheduled deployment behavior.
    • You promote a user story to a higher environment, and the user story gets back promoted to other lower environments. You then manually move that user story from the upper environment to the lower environment where it originated in order to fix something and recommit. Once the user story gets promoted again, Copado will display the user story on the User Stories Behind tab so that you can back promote it to the other lower environments or it will automatically back promote the user story if you are working with Copado Continuous Delivery and have configured an automated or scheduled back promotion behavior.

In order to support this enhancement, a new Status field has been added to the Promoted User Story object (see the Upgrade Instructions). When you manually move a user story to the environment where it originated, Copado automatically updates this picklist field to Outdated, and the user story is again available for promotion.

If you accidentally change the environment on a user story to a lower environment, but you don’t want to make the user story available for promotion or back promotion, you will need to edit this picklist field and change it from Outdated to Active.
  • Copado Continuous Delivery quality gates and automations now also apply to org-to-org metadata deployments.
  • Copado Continuous Delivery now back promotes user stories that belong to different projects or releases in a single promotion if you have configured an automated or scheduled back promotion behavior. This way, if you have several user stories from different releases or projects that need to be back promoted to the same environment, Copado will just create one promotion record instead of multiple records.
Static Code Analysis
  • Copado now supports Apex pages (Visualforce), Apex components and Apex triggers when working with PMD. For more information, check out the PMD section of our documentation site.
Copado Compliance Hub
  • Copado now prevents users from entering duplicate names for Compliance Rule Groups.
  • The error message defined in a compliance rule can now also be found in the Compliance Findings object.
  • Copado now shows different messages on the commit page when compliance rules are violated depending on whether the action is Abort Process or not.
Additional Changes
  • Copado has created a new custom permission named Enable Vlocity Integration. This custom permission allows users to see the Toggle Vlocity button and enable Vlocity in their org even if they are not system admins.
  • Copado now displays the Vlocity components that have been successfully deployed as well as those that have failed.
  • Security enhancement when registering with the Copado server in Copado Playgrounds. This registration process is entirely performed by Copado’s backend.
  • In order to add an extra security layer when installing Copado for the first time, there is a new button at the top right corner of the Account Summary page called Register Application. New customers will have to click on it to complete the registration with the Copado server.
    This step has to be performed right after the installation, and before creating and authenticating the org credentials.
  • Copado now displays two different error messages, one if you have installed Copado for the first time and have not yet completed the registration with the Copado server, and another one if you have not authenticated the org credential.
  • The Copado Console app is now available in Winter ‘21.

Name Changes

    • The Quality Gate object has been relabeled as Automation.
    • The Deployment Behavior section within the Connection Behavior record has been relabeled as Promotion Details.
    • The Back-Promotion Behavior section within the Connection Behavior record has been relabeled as Back-Promotion Details.
    • Connection behavior fields:
      • The field Deployment Behaviour has been relabeled as Promotion Execution.
      • The field Back-Promotion Behaviour has been relabeled as Back-Promotion Execution.
      • The field Scheduled Deployment Max Batch Size has been relabeled as Scheduled Promotion US Group Size.
      • The field Scheduled Back-Promotion Max Batch Size has been relabeled as Scheduled Back-Promotion User Story Group Size.
      • The field User Story Status After Deployment has been relabeled as User Story Status After Promotion.
      • The field Deployment Schedule has been relabeled as Promotion Schedule.
      • The field Schedule Deployment has been relabeled Schedule Promotion.
    • The field copado__Story_Points_SFDC__c on the User Story object has been relabelled as Actual Points.
    • The field copado__Story_Points_Other__c on the User Story object has been relabelled as Planned Points.
    • The field copado__Story_points__c on the Sprint object has been relabelled as Total Capacity (Points).

Copa GCP

As part of the Winter ‘21 release, Copado has introduced a new backend server based on the Google Cloud Platform, Copa GCP. This new server offers, among other things,  performance improvements and support for SSH connection for on-premise resources. If you are interested in learning more about this feature, reach out to your customer success manager.

New Features and Enhancements in the Value Stream Mapping Package

New Metrics & Improved Interaction

  • There is a new standard metric called Cycle Time that represents the time that was spent on completing a work item for a process block (this excludes  the idle time).
  • Custom metrics can now be easily edited or deleted as well as rearranged using a new drop-down menu.
  • Enhancement in the display of numeric fields for standard metrics. Metrics are now adjusted to months, days and hours.
  • You can now create custom metrics based on currency fields.
  • Stages and process blocks can show you what records are behind those metrics. Now you can click into any  process block or stage to see a drill-down data table with the corresponding work item records. The data table will display the work item hyperlink so that users can navigate directly to record in Salesforce. 
  • Filters now support custom metrics in addition to standard metrics.
  • FIlters now support the contains filter logic, lookup and picklist fields.
  • You can now use chatter in the value stream map to collaborate with other team mates on your work items. Native chatter functionality in the bottom utility bar enables you to post, tag, and collaborate with other users.

For more information about these features, take a look at the article Value Stream Maps.

New Features and Enhancements in the DevOps Analytics Package

  • The new version of DevOps Analytics utilizes metrics from the Git Snapshot object to capture metrics like pull requests by state and number of open pull requests. These metrics have been included in the Development dashboard.
  • The new chart which shows the number of merged vs. open pull requests will show you all open or merged pull requests related to the user stories. 
  • A new component which displays open pull requests needing action displays Pull Request records which have a related review record where there are open comments.
  • Destructive changes are now included in the existing tree map in the Development dashboard where you can see the number of promotions per file.
  • Pipelines have been incorporated into the existing filters so that you can filter the data by pipeline. 

New Features and Enhancements in the Change Management Integrations Package

  • There is a new version of the Change Management Integrations package. This new unlocked package replaces the previous open-source version, which means you can easily upgrade it without having to uninstall the previous package when Copado releases a new version.
  • You can now sync user stories with a sprint for Azure DevOps.
  • User story, sprint and related release sync is available for the Jira integration. 

For more information about this package, check out the article Change Management Integrations.

Bug Fixes

  • Copado no longer throws an error when you click on the tab Promotion Metadata.
  • When you deploy data with a Data Template deployment step and then click on the link View Results to view the results on a new page, the Deployment page no longer scrolls up to the top when you return to that page and remains at the deployment step results.
  • Metadata components previously committed as retrieve only are now also preselected when you use the Recommit Files operation.
  • You are now redirected to the relevant tab after deleting an Org Credential or a Git Snapshot record.
  • Copado’s External CI Jobs feature can now retrieve jobs that live within a folder.
  • The “Maximum view state size limit” error returned when promoting or back-promoting user stories in bulk from the Pipeline page has been fixed.
  • The conflict resolution page no longer displays duplicate conflicts.
  • Copado now removes blank spaces before and after values in compliance rule criteria. This way, criteria are no longer disregarded during the compliance scan.
  • Copado no longer displays a blank screen after you create a new user story from the sprint wall.
  • The Vlocity toggle button is now working as expected.
  • The Kanban Board page no longer breaks when you apply certain filter criteria.
  • The relationship diagram in Copado Data Deploy no longer displays the attachment icon on an object if you have not selected any attachment options in the template.
  • Nodes are now correctly drawn in Copado Data Deploy’s relationship diagram when the selected object includes a special character.
  • Copado Data Deploy now allows you to deploy objects from managed packages whose names begin with ‘e’ or ‘mdt’.
  • The online conflict resolution feature is no longer triggered due to empty lines, Copado just trims them (KI-00271). 
  • The Disable Auto-Resolve functionality no longer applies to conflicts in files that are not part of user story commits. Those files will continue to be marked as Auto-Resolve by default, and users will be able to choose whether they want to manually resolve them or let Copado resolve them.
  • Git Promotion and External CI deployment steps are created by Copado’s backend while deployment steps related to Copado Continuous Delivery’s quality gates are created by Copado’s frontend. When there were several quality gates, the same order number was being added to the last quality gate step and the first step created by the backend. As a result, the quality gate step was not being triggered, as only one step with a given order number can be executed. This issue has now been fixed (KI-00289).
  • Images in formula fields are now correctly displayed.
  • Copado no longer displays validation messages for org credentials that have the Disable Validation checkbox selected.
  • When you add a Name custom field to Disabled Fields in the Data Template Setup custom metadata type, standard name fields are no longer disabled (KI-00298).
  • The promotion page now displays a clear error message when the project linked to the promotion does not have a pipeline.
  • The project json is now correctly updated when a new version of a package that has a dependency is generated.
  • Git MetaData deployment steps the Add Commits functionality are now correctly retrieving metadata from the Git commit (KI-00296).
  • CodeScan static code analysis scans are now working as expected with Aura definition bundles (KI-00311).
  • The results summary table is now correctly displayed once the data deployment is completed.
  • You can now commit metadata into a scratch org without selecting a package.
  • Salesforce Flow deployment steps that call an External Service are no longer failing.
  • Copado no longer throws a “copado: Too many query rows: 50001” error when you click on Validate Selections on the Pipeline page (KI-00316).
  • Kanban boards no longer return the “No such column 'name' on entity 'Case'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.” error message (KI-00319).
  • The "Too many SOQL queries: 101" error returned when deploying a large amount of user stories with a lot of components as part of the same promotion has been fixed (KI-00253).

How did we do?