Summer '20 (v16.6) - Release Notes

Updated 1 week ago by Copado Solutions

Key Features

  • There is a new deployment step named Salesforce Flow that allows you to trigger a Salesforce flow as part of your deployment. For more information about this new step, check out the article Deployment Step: Salesforce Flow.
  • There is a new user story task named Salesforce Flow that allows you to trigger a Salesforce flow as part of your user story deployment.
  • There is a new object named Results where Copado will store all job execution and test run results. This way, you won’t need to scroll endlessly down on the user story related lists to find your test results or navigate to any other objects to find the results you are looking for. For more information about this object take a look at the Results Object article.  
  • Copado Data Deploy can now generate external Id values for the records that don’t have one in order to match them across all orgs in the pipeline. If this feature is enabled, you will find a new column in the data deploy results summary table that displays the IDs that have been generated by Copado’s automatic record matching functionality. This results summary table has been updated both in the data deployment wizard and in the Data Template deployment step.
  • 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.
  • 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.
  • 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.
    If you are upgrading from a previous version of Copado, the following manual steps are required to get this updated:
    • Navigate to Setup > Object Manager > Promotion.
    • In the Promotion object, go to Field Sets and select Pipeline Manager.
    • Drag Source Environment and drop it before Destination Environment:
    • Click on Save.

Additional Changes
  • Name changes:
    • 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).
  • The help text on the Block Commits field on the Pipeline object has been updated. If you are upgrading from a previous version of Copado and want to get it updated, follow these steps:
    • Navigate to Setup > Object Manager > Pipeline.
    • From the Fields & Relationships section, click on Block Commits.
    • Edit the help text and replace the existing content with the following: If checked, committing changes on user stories linked to this pipeline will not be allowed:
    • Click on Save.

Upgrade Instructions

If you are using the Copado_User permission set, you don't need to follow the OLS, FLS, and tab visibility upgrade instructions, as this permission set is already updated by Copado with each new version. However, if you are using a cloned version of this permission set, you need to manually upgrade it.

OLS, FLS for New Object Fields and Tab Visibility

Make sure relevant profiles and permission sets have read and write access to the following objects and fields:

Type

Name/Label

API Name

CustomObject

Result

copado__Result__c

CustomField

User Story

copado__User_Story__c

CustomField

Status

copado__Status__c

CustomField

Start Time

copado__Start_Time__c

CustomField

Link

copado__Link__c

CustomField

Job Type

copado__Job_Type__c

CustomField

Job Id

copado__Job_Id__c

CustomField

Error Message

copado__Error_Message__c

CustomField

Error Code

copado__Error_Code__c

CustomField

End Time

copado__End_Time__c 

CustomField

Duration

copado__Duration__c

CustomField

Description

copado__Description__c

CustomField

Deployment Job

copado__Deployment_Job__c

Type

Name/Label

API Name

CustomObject

Step

copado__Step__c

CustomField

Automated Behavior

copado__Automated_Behaviour__c

Tabs

Results

Layouts

Add the fields, buttons and related lists to the required layouts:

Step

Add the Automated Behavior field (copado__Automated_Behaviour__c) to the Step Layout.

User Story

Add the Result related list to the User Story Layout.

New Picklist Values
  • In the Type field (copado__Type__c) of the Step object (copado__Step__c), add a new picklist value for Salesforce Flow.
  • In the Type field (copado__Type__c) of the Deployment Task (copado__Deployment_Task__c) add a new picklist value for Salesforce Flow.

Bug Fixes

  • 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.


How did we do?