Summer '21 - Release Notes

Updated 4 months ago by Copado Solutions

Thank you for choosing Copado! Keeping up with our commitment towards continuous improvement, we bring you a wide range of exciting new features and enhancements to our product in the Summer ‘21 release. In this document, you will find a gist of all features and enhancements released from Winter ‘21 to date, including features that were released in the minor versions.

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


  • Manage development for technologies like Heroku and Mulesoft from inside Copado

You can now use Copado to manage DevOps processes for clouds like Heroku and Mulesoft, as well as for custom application development. For more information about Multi-Cloud, review the article Introduction to Multi-Cloud

  • Many development projects use similar patterns of environments for development, testing, and production. On Heroku and Mulesoft, each application needs its own copy of the pipeline. To simplify the process of creating new development pipelines, there is a new button on the Pipeline page called Clone with Environments. After you have created your first pipeline, you can use this option to create other pipelines. Copado will clone the environments and system properties, so all you need to do is update the records and activate the pipeline once the process is complete.

Key Features and Enhancements in the Copado Deployer Package

  • Introducing Functions, a new Copado feature
    Copado has released a new feature called Functions that enables you to execute multiple tasks as a part of your DevOps process. A function is basically a script that contains a series of commands that can run different tasks. Functions can be executed from multiple places such as:
  • A deployment step
  • A Function record
  • A custom Apex class
  • A Salesforce flow. This option enables you to trigger a function from a custom button on a layout.

To work with this feature, there is a new permission set: Copado Functions.

For more information about this feature, see the Functions article.

Automation Templates
  • Copado has significantly refactored and made architectural changes to automation templates: 
    • Now, you can see the list of steps in the Related List View
    • You can also create and edit steps in the modal. 
  • Copado has enhanced the automation templates to enable you to import, export, and clone templates. Also, a new quick action has been introduced in automation templates: Execute Template that allows you to execute automation templates on-demand from the Automation Template record. 

For more information about these new features, check the Exporting, Importing and Cloning Templates article. 

Copado Continuous Delivery 
  • Unapproved and untested user stories do not get promoted or back promoted

Now you have an advanced filtering criterion for automated promotions, scheduled promotions, and back promotions. This ensures that unapproved and untested user stories do not get promoted or back-promoted. You have two new fields in the Connection Behaviour object—Promotion Criteria and Back-Promotion Criteria, where you can define the filtering criteria. For more information about this feature, check the Pipeline Configuration article.

  • Execute promotions and back-promotions in parallel 
    • There are two new checkboxes on the Connection Behavior object: Execute promotions in parallel and Execute back-promotions in parallel. When the URL Callout steps are created as the result of a scheduled promotion or back-promotion:
      • If these checkboxes are selected, Copado continues to deploy other callout steps if one of them fails.
      • If these checkboxes are not selected, Copado doesn’t trigger the deployment of subsequent steps if one of them fails.
  • The pipeline wizard is no longer the default option to create a new pipeline. If you want to navigate to the pipeline wizard, you can click on the new Launch Pipeline Wizard button on the Pipelines tab.
  • Enhancement in the User stories ahead and behind calculation
    Copado has introduced an enhancement in the user stories ahead and behind the calculation. Now, when you create a new environment or refresh a sandbox, the user stories that were in production before the refresh date or date of creation of the new environment are no longer available for back promotion.
  • Promoted user story records now follow an appropriate naming convention when created as a result of a back promotion. Created records take this name: Back Promoted User Story: [UserStory Name]. This way, you can easily differentiate between promotions and back promotions.
Copado Data Deploy

New Features

  • Introducing Data Commits 

As part of the Summer ‘21 release, Copado has enhanced the data deployment functionality and now enables you to commit data changes on a user story. With this functionality, you can keep a version history of the changes in a CSV file and:

  • Deploy data commits to other environments in your pipeline.
  • Back-promote data commits to lower environments.

For more information about this feature, please review the article Deploying Data as Part of a User Story.

  • Introducing Data Sets
    To support data commits, Copado has introduced a new feature called Data Sets. Data sets enable you to take a snapshot of the data stored in a certain environment and save it for future use or to deploy it to other environments in your pipeline. Review the Data Sets article for more information.


  • Apart from the new Data Commits and Data Sets features, there are several other enhancements in Copado Data Deploy:
    • The Data Template deployment step and deployment task have been enhanced to support data sets. 
    • An option to validate the deployment has been introduced in the data deployment wizard and the Data Template deployment step for multi-step deployments. This option enables you to review the changes and see if any of the objects or fields you are deploying do not exist in the source or destination environment, or if the deploying user doesn’t have access to them. An error message will be displayed in this case so that you can fix these issues before executing the deployment.
  • Email notifications have been enabled for the data template deployments that complete with warnings. You can click View Deployment Result to open the Deployment page. On this page, click the yellow flag to see the warnings.
Copado Core
  • Environment Path (Deployment Flow) for the User Story Lightning record page is available in Lightning App builder.
    Now you can add this component to a Flexi page and see the environment path on the user story page layout in Lightning Experience. To add it, you need to:
    • Navigate to the Lightning App Builder page.
    • Click on Edit User Story Lightning Page
    • Add the Visualforce standard component and select UserStory in Visualforce Page Name.
  • New License Manager replaces the old License Manager for Classic
    With this updated version you get to experience some cool Lightning features. Some of these include color-coded graphical License bars, user-friendly License Allocation Grid, easy ways to assign and unassign licenses to users using the UI, dynamic updating of license stats, and so on. To know more about the new features of the new License Manager go to the License Manager Documentation.

To make things more exciting for you, we have introduced In-App guidance for License Manager.

This is displayed only within the Copado Developer App and for users with Salesforce Manage Users permissions.
  • Two new fields added to the Deployment Task page
    Two new fields have been added to the Deployment Task page to support the enhancements introduced on the user story’s Manual Task deployment task. 




Apply to


Allows you to specify whether a particular task should be performed in a specific environment or in all environments in your pipeline.

Disable Task for Back-Promotion


Allows you to enable/disable the enforcement of manual tasks in back promotions. If the checkbox is selected during a back-promotion, Copado will auto-complete the task and will add the following message in the task “Manual Task not required for this destination environment. Copado auto-completed this task.”.

  • The Platform picklist field has been added to the Pipeline tab on the Getting Started Page

This enables you to build a pipeline using the getting started wizard. Once you are done, click on the new tab icon to easily navigate to the Pipeline record.

  • The User Story layout has a new Open Org button
    This button enables you to quickly navigate and log in to the corresponding source org of the User Story.
  • Enhancement for the commit feature
    After a commit is done, you can now check the metadata that was committed as Retrieve Only in the User Story Selections grid.
  • The Snapshot Difference feature now supports files
    Does your snapshot difference fail due to an attachment size limitation? This enhancement will resolve your issue.
  • You can now select the checkbox Disable Re-create Feature Branch on US for specific users
    You can now decide which users should not be allowed to recreate the feature branch when they re-commit a user story. To do this, follow these steps:
    • Navigate to Setup > Custom Settings.
    • Click Manage next to Personal Settings.
    • Click Edit next to the name of the user or profile you want to edit the settings for.
    • Select the Disable Re-Create Feature Branch in US checkbox and click Save.
      Personal Settings
  • Copado has deprecated unsupported permission sets from the managed package
    Your implementations are now further simplified. Copado has deprecated unsupported permission sets from the managed package. Copado only supports the Copado_user permission set. Delete these permission sets from your org.
You can delete them with a destructive change.
  • Copado has introduced some enhancements in Copado Smart Tips
    • Two new fields have been added to Copado Smart Help:
      • Triggering Metadata Items, where you can specify specific metadata items to trigger the tips that will be displayed when the user selects these metadata items.
      • Help Text Url, where you can add hyperlinks in the Help Text box. The URL must be entered with https:// format. 
    • Help Text values have been added to the Copado Smart Tips fields to explain how to use them properly. 
    • In Copado Smart Tips - Commit Metadata Assistant the Flow Active Version record Help Text value updated to: "Please, do not select the Flow Definition when committing and deploying flows with Copado. When the Flow is selected in the grid, the latest version (active or inactive) will be retrieved, committed and deployed". Also, a new field checkbox named Active has been created. The default value is true, but you can activate or deactivate the Copado Smart Help records that need to be called out with this field. If you are upgrading from a previous version of Copado and want to get these changes updated, follow these steps:
      • Update the Help Text value from the Flow Active Version record: 
        • Go to Setup -> Custom Metadata Types -> Copado Smart Help.
        • Click on Manage Records and select Flow Active Version.
        • Click on Edit and update the Help Text value with: "Please, do not select the Flow Definition when committing and deploying flows with Copado. When the Flow is selected in the grid, the latest version (active or inactive) will be retrieved, committed and deployed". 
        • After making the changes, click on Save.
      • Add the Active field to the Copado Smart Help layout: 
        • Go to Setup -> Custom Metadata Types -> Copado Smart Help.
        • Click Edit next to the page layout name and add the Active field (copado__Active__c) to the information section. 
  • The Triggering Value field is renamed to Triggering Metadata Type.
  • Flag the deployment file you want to export
    With a Copado User license, you can flag the deployment's zip file. To do this, in a Deployment record, select the checkbox Attach Deployment File to export the deployment's zip file. Let’s understand this enhancement in more details:
    • There is a new checkbox in the Deployment object named Attach Deployment File
    • You can select this checkbox from the deployment detail section when you create a manual deployment from a promotion. 
    • This checks the deployment's Attach Deployment File checkbox automatically. 
    • When you select this checkbox, Copado automatically generates the zip file that contains the logs with the deployment results.
  • The commit page is refactored
    You can now easily navigate through a much faster and dynamic Commit page thanks to all the refactoring described below:
    • When accessing the User Story Commit page or Git Snapshot Commit page the metadata grid automatically displays to its maximum length based on the screen resolution. The expand button has been removed from these metadata grids
    • The twisted arrow used to refresh the grid is replaced with a button called Refresh All Metadata. At the bottom of the page, you can see the grid's last refresh date. 
    • There’s a new button Refresh Recent Changes that retrieves the components modified in the source org of the user story since the last credential refresh date. This makes the grid load faster since it’s no longer a full refresh, but a partial one that happens automatically when you load the page. 
      This button is available only when the source org is a developer or developer pro sandbox, or a scratch org, and when source tracking is enabled in the production org. To enable it:
      • Go to Setup --> Dev Hub → Select Enable Source Tracking in Developer and Developer Pro Sandboxes.
      • Refresh the sandbox after enabling this feature.
    • There’s a new button Auto-Select Changes that automatically selects all modified components in the grid based on the option selected from the drop-down list: 
      • Done Today: automatically select the grid components whose last modified date is today. 
      • Done Since Yesterday: automatically select the grid components whose last modified date is greater than or equal to yesterday.
      • Done Since Last Commit Date: the behavior will depend on the following scenarios:
        • There are commits on the user story: Copado will automatically select the grid components whose last modified date is greater than or equal to the last valid commit in the user story. 
        • There are no commits on the user story (first commit about to happen): Copado will automatically select the grid components whose last modified date is greater than or equal to the last valid commit performed by the org credential in the source environment of the user story. 
        • There are no commits on the user story or the related org credential: Nothing is selected and the following error message is displayed: "There is nothing to select at the moment. There should be at least one commit present in the User Story or in the related Org Credential".
      • Get Vlocity Dependencies: this field has been removed from the metadata grid page and is now part of this button. Its function remains the same. For more information about it, please review the Vlocity Integration article.  
      The components that are selected are those where the user in the Last Modified by ID column of the metadata grid matches the logged-in user’s full name (first and last name).

For more information about these enhancements, check the Metadata Grid article, since there are some limitations that you need to take into consideration. 

  • New global method to return recent changes in the Global API class
    A new global method to return recent changes in the Global API class is created to leverage the refresh recent changes feature. For more information, please check the Global API article.
  • When loading the metadata grid, either in page load, after a full refresh or refresh recent changes, the components are displayed by Last Modified Date in descending order.
  • More descriptive error messages have been added to the Metadata Grid operations (Auto-Select, Refresh Recent Changes) to provide better information.
  • Tooltips are added in the Online Conflict Resolution and labels renamed
    This helps you with more information about how the panels work. The following labels are renamed:  
    • In the 2 panels view:
      • Feature Branch label is renamed Conflicts in Feature branch.
    • In the 3 panels view:
      • Feature Branch label is renamed Conflicts in Feature branch.
      • Promotion Branch label is renamed Conflicts in Promotion branch.
User Story Bundle

User Story Bundle (USB) is meant for organizations that have regular promotions with a large number of stories. Hence if you want to centralize changes from several user stories into a single user story, you can leverage the User Story Bundle feature. With USB you do not have to migrate to SFDX packages. USB enables you to group large amounts of changes and helps in reducing time and complexity in promotions.

If you are already on the User Story Bundle - Pilot version, here is all the information you need to migrate to our latest version of User Story Bundle—User Story Bundle - Migration from Pilot to GA Version.

Copado CLI
  • New commands are added to Copado CLI.
  • You can upgrade using the command sfdx plugins:update.
  • For more information, refer to CLI Commands.
  • Now run Automation Templates (AT) from CLI
    Use CLI commands to list and run automation templates in a simple way from the CLI. You can extend Copado into your local environment without going into SFDC.
  • Copado now supports committing Vlocity components through the Copado CLI.
Copado Compliance Hub
  • Copado Compliance Hub Rule page is converted into a FlexiPage
    Now you can edit and adjust the Rule Detail Information of compliance rules to your needs. For more information about this feature see How to Create a Compliance Rule.
  • Compliance Scope lightning web component replaces Visualforce component
    A new Compliance Scope lightning web component is created for Compliance Rule that replaces the old Visualforce component. These are the new features included:
    • Compliance Scope displays metadata picklist, criteria row functionality and criteria filter logic. Matching criteria, record count, and record count criteria are no longer needed and are removed from the Compliance Rule layout.
    • Criteria conditions can individually be deleted by row.  
    • If there is a syntax error, duplicated criteria rows, or missing a criteria value, a validation alert is displayed and you will not be able to save the record until the error is fixed.
    • Read and Edit modes with Cancel/Save footer have been added to the Compliance Scope section.
    If you’re using a lightning record page that it’s not the Compliance Rule Record Page in the Compliance Rule object, you need to activate this one as Org Default for Desktop form factor. 
  • The compliance rule criteria allows checking for blank values for a field within a node. For this, two new operators have been added to the string value:
    • Is Blank
    • Is Not Blank
Boolean, Double, Integer, and Long are out of scope since null values are not supported. 
  • Copado Compliance Hub preset rules are available as an installable extension on DevOps Exchange, so you can import them into your Copado org and use them in your scans.
Copado DX
  • Significant refactors have been made in Copado DX
    You now have a Copado DX experience that is faster, efficient, and more robust to scale in the future without changing the behavior of the application. To implement these enhancements for you we had to remove some scratch-org, load-metadata options. 
  1. Go to Copado DX Panel > Scratch Org Operations.
  2. Select any Scratch Org
  3. Click Load Metadata. The Metadata source displays two options—Git Packages and Unlocked Packages.
    We have removed these from the list:
  • First-Generation Packages: Deprecated and will no longer be supported. 
  • Second-Generation Packages: Will be redesigned and added again in the future. 
  • Patch a release (beta): Will be redesigned and added again in the future. 
  • Branch: Will be redesigned and added again in the future. 
Copado Version Control

In our commitment to provide new products to extend Copado's functionality, we are happy to announce Copado Version Control. This is a Git-based source code repository hosting service intended for teams that currently have no version control or have infosec challenges. 

This product provides the fundamental features every team needs to perform multi-cloud DevOps with an experience very similar to what you're used to from other version control systems. It lets you and others work together on projects from anywhere and is tightly integrated with the Copado Platform.

A brand new category called Copado Version Control is now created on our documentation site where you can find more details on this new product. 

This is a separate product that's not part of the Core package. To acquire it, please contact your CSM/AE.
Key Features and Enhancements in the Change Management Integrations Package
  • Mapping Issue Types and Work Item Types with Record Types are now supported in the current Jira and Azure DevOps integration that Copado offers.
    • Record type mapping works bi-directionally, which means that when you change a Record Type on Salesforce and trigger Salesforce to a third-party integration, the Record Type (Issue Type, Work Item Type) also changes on the third party (Jira, Azure DevOps) work Item.
  • A new field has been added to the Project object called Enable Community Users. This allows you to include or exclude community users in the Jira and Azure DevOps sync with Copado. The default value is unchecked, so if you want to include any active community users for user field mapping, such as Assignee to Developer, you can check this field to enable them. 
  • Additional Jira custom field types support.
    • Copado now supports integration for label, dropdown, checkbox and people type custom fields for Jira. For custom field mapping to be successful, you need to:
      • Enable Exclude from Third Party update in Project.
      • Fields getting mapped on the Salesforce side should be of either multi-select (unrestricted) or text with maximum length, as there can be multiple values selected at the Jira end for these fields.
The integration is not compatible with mismatched field types between Salesforce and Jira.

For more information about the upgrade instructions of this package, check out the article Copado Change Management Summer '21 - Upgrade Instructions.

Copado Security Planning 

Copado Security Planning combines industry-leading tools and expertise to identify potential security and compliance risks that threaten the success of your digital transformation. First, you’ll meet with a certified security expert to assess your DevSecOps readiness and create your plan. Your tailored action plan uses value-driven prioritization to form your unique compliance and security requirements to your business, industry, and release process. The centralized dashboard shows your overall progress, areas for improvement, and your security score to keep you on track in your DevSecOps journey. 

For more information about Copado Security Planning and the enhancements included in the Summer ‘21 release, please review the article Security Planning Overview.

Key Features and Enhancements in Copado Analytics
  • Embedded URLs are now added to the Deployment Attempts and Deployment Complexity components.
    • When clicking on a specific column record on the Deployment Attempts chart, a show/hide table appears where all the URLs of the Deployment are displayed. You can click on each of them to be redirected to the record for that specific item. To exit the table, you need to click anywhere on the screen.
    • You can also click on the dots of the Deployment Complexity chart to be redirected to that specific record. If you hold your cursor over the dot, you can see the information of that specific deployment.
Key Features and Enhancements in Copado Value Stream Maps
  • Value Stream Maps have a new look and feel! Click the edit page to unlock the value stream map flexi page and enable your admins to customize and extend value stream maps. With this, you’re now able to:
    • Extend the Value Stream Map by adding any components to the Flexi page which gives you the capability of extending this product to fulfill your needs.  
    • Customize the header, the displayed buttons, the page extension, among other things with standard Salesforce configuration.
  • The Value Stream Map layout now include the following tabs for easier navigation:
    • Details where you can see any details related to the VSM such as name, description. 
    • Stages where you can view, edit, eliminate or add new stages. 
    • Mapping enables you to map and configure your value stream map. Also, a docked utility bar has been added so that you can edit and save easily throughout the process of making changes across any tab. 
    • The Chatter utility bar has been removed from the view page and it has been added as a tab. 
  • Three new panels have been added to the mapping tab to support additional work categories: 
    • Completed: shows mapping for completed work items. With this, you can measure the progress of work being done with exact ending criteria.  The panel will be displayed in green color.  
    • Cancelled: shows mapping for cancelled work items. The progress percentage will be shown. The panel will be displayed in red color.   
    • Backlog: shows mapping for work items that are in the backlog. . The panel will be displayed in yellow color.  

These panels have a criteria section where you can map multiple values. . 

If a value is mapped into one of these panels, the work items associated with the mapping are excluded from the standard metrics such as: Lead Time, Cycle Time, % C/A. 
  • The following buttons have been relocated on the value stream map page:
    • Configure Metrics which will redirect you to the metrics sorting modal where you can show/hide or sort metrics. 
    • Add New Metric where you can create as many custom metrics as you need. 
      • Custom metrics are limited to numeric fields. Ensure that there is a numeric field on the primary object, otherwise a warning message will be displayed before you attempt to save the record. 
  • There is a new button on the Value Stream Map page called Configure VSM Thresholds. When enabled,  the Threshold configuration page will appear where you can configure the threshold limits for each stage. 
Only numeric characters are supported in Thresholds configuration. 
  • The Threshold feature is new with Summer 21! Use Thresholds to help identify where a process block may have reached a critical point or acknowledge a bottleneck. For more information about the feature, check out the Value Stream Map Thresholds article. 
  • The metrics that are reaching the threshold that you have set will appear in red to better identify which ones have reached a critical point and you need to take action.  
  • A Show Thresholds toggle button is now on the Value Stream Map page. This can show or hide the thresholds on the value stream map page. When enabled, only the thresholds that have been configured will be displayed. 
  • The following enhancements have been made to the metrics sorting modal: 
    • Hide Metrics: A Show in VSM toggle button has been added to show or hide the metrics on the value stream map.
    • Sorting: Sort custom and standard metrics in the metrics sorting grid is now possible. Drag and drop the metrics to place them in any order. 
      • When creating a new value stream map from scratch, all standard metrics will be visible.
  • Edit and Delete Metrics Quickly: The individual metric cards have a menu in the top right. Sort and hide options on metric cards have been removed. Now, the only options available are Edit and Delete.
  • When navigating to the value stream map data you will be able to see in the stage columns the real-time value of the primary field, meaning that you’ll see the item’s particular stage and not all the process block stages.  
  • Filtering operations now support numeric fields. For example:  creating a filtered view using the user story Priority field is now possible. 
Copado Essentials

150,000 companies use Salesforce to manage their business. As their businesses evolve they need to be able to innovate quickly and safely. The hardest part of building on Salesforce is managing deployments. That's why Copado is excited to announce a new solution to make Salesforce deployments fast and easy. Introducing Copado Essentials. Log in and get started in minutes for free. Visit Copado Essentials documentation for more information.

Name Changes

  • The Org Credential object has been renamed Credential.

Bug Fixes

  • When you click Validate on the Pipeline page, the selected test level is applied (KI-00322).
  • If you are working with a Git repository on premise, you are now able to create pull requests from the User Story Metadata related list (KI-00331).  
  • While creating or modifying a Kanban board, Copado no longer throws an error if you choose a field in the Select the field to define the Kanban cards colors dropdown (KI-00337).    
  • Package dependencies are now created in the correct order. 
  • You can now assign a max static code analysis score to the source environment of a promotion and review it from the promotion page. 
  • Salesforce flows are now triggered in a queuable method so that callouts within the flow happen independently of the step DML update to In Progress. This way, you no longer need to add a Pause element at the beginning of the flow to avoid the Salesforce error of callouts happening after a DML. 
  • When creating a record matching formula for an object and generating the External ID field, the component converts the lookup fields to corresponding relationships (i.e. Pricebook2 to Pricebook2Id and vice versa). 
  • Now, you are able to run static code analysis on aura definition bundle components from a user story with CodeScan (KI-00311). 
  • When creating a validation deployment with post-deployment manual tasks included on it, the promotion status was being updated to Completed and the environment on the user story was being replaced by the destination environment of the deployment, although nothing was being deployed, since it was a validation deployment. This issue has now been fixed and the promotion and the user story reflect the correct information (KI-00305). 
  • The conflict resolution page no longer shows duplicate conflict files for the same component  (KI-00321). 
  • The apply_env_vars and apply_find_replace parameters in the Take a Git Snapshot webhook are no longer disregarded during the job execution when you schedule a job for Git snapshots.
  • Formula fields can now be selected in the Main Object Filter dropdown and in the record matching formula dropdown. 
  • When selecting a manual task as the second step in a multi-step deployment, the chatter and/or email notification is now sent to the owner of the task (KI-00308).
  • The arrows on the online conflict resolution panel are now displaying correctly (KI-00349).
  • When you promote a user story and then manually move it to a lower environment, Copado no longer updates the Status field on the Promoted User Story record for all promotions, only the Promoted User Story record related to the relevant promotion is updated (KI-00368).
  • Copado no longer changes the record type of user stories to Bug if the user that is editing the sprint wall doesn’t have access to all record types (KI-00388).
  • When adding the Owner column to the sprint wall columns field set, Copado no longer displays the following error message when opening the sprint tab: “Script-thrown exception” (KI-00395).
  • When trying to validate your user stories by clicking on the Validate Selections button in the pipeline, the following error message no longer appears: “Too many query rows: 50001” (KI-00316).
  • When syncing external user stories from Jira, you will no longer receive the following error message and they will be synced and created correctly in Copado: System.LimitException: copadoccmint:Too many callouts: 101 (KI-00409).
  • The option to View Report from a value stream map no longer fails if your value stream map is based on a primary object that doesn’t have a name field.
  • The sorting modal for custom metrics no longer displays duplicate numbers in the rows.
  • A new hierarchy custom setting has been created to store the last filter selected on the Value Stream Map.
  • When you open the value stream map, you will no longer be redirected to the All filter, but to the Last Viewed filter. Therefore, if your organization is reaching the limits on the Value Stream Map, you should be able to navigate to a specific filter to bypass the error message. 
  • Existing core functionality no longer breaks If you don’t select a picklist value in the Platform field. Blank values are now equivalent to Salesforce.
  • Significant refactors have been made to the IndexMetadataJob class to handle large attachments in the user story, so you will no longer receive the automation error email after committing a large number of attachments and refreshing the metadata index (KI-00341). 
  • When resolving conflicts in Apex classes with the online conflict resolution panel, line breaks are no longer added between the conflicts. (KI-00376).
  • Deployment with Apex Test with Validation or Validation quality gates, are now deploying correctly (KI-00380). 
  • Metadata components, previously committed as retrieve only, are visible as preselected when using the recommit files operation (KI-00385). 
  • When you commit from snapshot differences you’re now able to click, after selecting the user story,  on the Go to commit page button and the following error message will no longer be displayed: System.StringException: Invalid ID (KI-00389). 
  • You can add the Status field to the Mass Back Promote field set in the User Story object (KI-00406).
  • When adding multiple quality gate steps in a deployment with execution sequence after, the steps run in the assigned execution order (KI-00412).
  • Copado no longer displays the “Maximum view state size limit (170KB) exceeded. Actual view state size for this page was 197.907KB” error message when you view a data template or create a new data template for an object that has a lot of fields (KI00336).
  • The Get Vlocity Dependencies button is removed from Git Snapshot page(KI-00424).

How did we do?