Summer '21 (v18.28.4) - Release Notes

Updated 1 week ago by Copado Solutions

Key Features

Copado Plan
  • In the previous release, we brought you the Sprint Wall. Now we bring you the renewed version of:
    • Epics
    • Features
    • Applications
    • User Story Tasks
  • To get access to these new features, get the Copado Plan license, which replaces the old Guest license.
Copado Data Deploy 

The new Lightning record page for Data Template is here with an intuitive user experience and enhanced features like:

  • Simplified and intuitive user interface: 
    • View with a better queue: select and view more than 500 fields under the main object. 
    • Configuring the record matching formula is no more a tedious process; we’ve made the whole experience simple and fast.
  • Lightning-fast performance: no more page reloads after you perform any action on the data template.
  • Finer search & sorting and select all experience: sort, search, and select all fields from a search result for higher control and granularity.
    Check out what’s new in the Data Templates for Lightning feature.
Multi-Cloud
  • Copado has created Job Engine, a redesigned multi-cloud architecture that replaces automation templates and enables you to commit, promote and deploy changes across the different environments in your pipeline as part of your multi-cloud DevOps process. Copado’s Job Engine consists of three main features:
    • Job Templates
    • Job Executions
    • Job Steps
    A new permission set called Job Engine has been designed to work with this feature so don’t forget to assign it to the users that will be working with Multi-Cloud. For more information about this new functionality, review the article Introduction to Copado Job Engine.
  • As part of the new job engine architecture, Copado has created a series of standard actions that will run the commit, promotion, and deployment processes through a function step in the job template. For more information about this, review the Copado Actions Overview article.
  • Copado now has a new User Story Commit page for Multi-Cloud, which provides a better and more intuitive experience when committing changes made in the source environment.
    This new experience can be extended and customized through custom components depending on the Copado Multi-Cloud extensions installed in your org.
    This new experience is not applicable to Copado classic.
    For more information about the Multi-Cloud User Story Commit page, review the article User Story Commit Page for Multi-Cloud. For further information about Multi-Cloud, review the article Introduction to Multi-Cloud
  • The multi-cloud Promotion record includes a new tab named Changes, where you can see the metadata of the user stories included in the promotion.
  • There is a new related list on the user story, Deployment Steps, that enables you to add different steps that will be executed once the user story is deployed. The steps that are currently supported are:
    • Salesforce Flow: It enables you to execute a Salesforce flow.
    • Function: It enables you to execute a function.
    • Manual Task: It enables you to perform a manual task.
    Please note that this related list is only available if the user story is linked to a multi-cloud pipeline. If you are working with Copado classic, you can use the existing User Story Deployment Tasks related list.

Upgrade Instructions

If you are working with Multi-Cloud, assign yourself the new Job Engine permission set.

If you are using the Copado_User permission set, you don't need to follow the below 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 the corresponding access to the below objects, fields, and tabs:

Object: Package

Type

Name/Label

API Name

Permission

CustomObject

Package

copado__Artifact__c 

Read/Write

CustomField

Last Job Execution Id 

copado__LastJobExecutionId__c

Read/Write

Object: Package Version

Type

Name/Label

API Name

Permission

CustomObject

Package Version

copado__Artifact_Version__c

CustomField

Last Job Execution Id 

copado__LastJobExecutionId__c

Read/Write

CustomField

Data JSON

copado__Data_JSON__c

Read/Write

Apex Classes

Make sure the relevant profiles and permission sets have access to the below Apex classes. See Setting Apex Class Access from Permission Sets for elaborate steps.

The following classes has been added to the Copado User permission set:

  • ActivateExtensionConfigurationCtrl
  • ConnectionDetailsCtrl
  • CreateAttachmentAction
  • DataTemplateActivateTemplateCtrl
  • DataTemplateCloneCtrl
  • DataTemplateConfigurator
  • DataTemplateDeactivateCtrl
  • DataTemplateDefineDataSourceCtrl
  • DataTemplateDeploymentTemplateCtrl
  • DataTemplateExportCtrl
  • DataTemplateMainObjectTableCtrl
  • DataTemplateObjectFiltersCtrl
  • DataTemplateRecordMatchingFormulaCtrl
  • DataTemplateTabContainerCtrl
  • DelegateApexTestsExecutionAction
  • DestinationEnvironmentBranch
  • EnvironmentBranchHelper
  • GetConflictResolutionAttachments
  • GenerateScaRulesetAction
  • GenerateScaRuleSetCtrl
  • GlobalFindAndReplaceDestinationId
  • GlobalFindAndReplaceHelper
  • GlobalFindAndReplaceSourceId
  • PromotionUserStoryMetadatasHandler
  • QueryApexTestResultsAction
  • RetrieveOrgTestClasses
  • RollbackWizardExt
  • ScaRulesSelector
  • SourceEnvironmentBranch
Layouts

Object: Package

The instructions for the Package and Package Version objects are only required if you are working with the DX plugin.

Add the Create Package Version and Distribute Package buttons in the Mobile & Lightning Actions section in the Package Layout.

Object: Package Version

Add the Data JSON field to the Artifact Version Layout.

Object: Job Step

Make the following changes to the Job Step Layout:

  1. Remove the Execute Manual Step mobile & Lightning action.
  2. Add the Complete Manual Task mobile & Lightning action.

Object: Epic

You need to enable both Detail Page and the Edit Page for the Information Section. To do this, perform the following steps:

  1. Hover the mouse pointer over the Information Section title, till you see a wrench icon appear at the far right corner.
  2. Click the wrench icon, select both Detail Page and Edit Page.
  3. Click Ok. You will now notice that the greyed-out Information Section looks highlighted.
Perform the steps above in the layouts for the following objects as well:
Feature
Application
User Story Tasks

Here is how you need to arrange and configure the new Epic page layout:

What You Need to Remove

What You Need to Add

Remove the sections and their fields:

  • Epic Details

Add the following fields to the Information section:

  • Epic Title
  • Application
  • Release
  • Epic Ref
  • Status
  • Canceled reason

Add the following sections and the fields:

  • Section name: Description
    Number of columns: 1
  • Fields:
    • Description
    • Technical Assumptions
  • Section name: Owners
    Number of columns: 2
  • Fields:
    • Created By
    • Owner
    • Last Modified By
To find a used field easily on the layout, just click on the field name in the field box and it gets highlighted in yellow in the layout.

Refer to the Salesforce article Create a new section in a page layout for more information.

Object: Feature

Here is how you need to arrange and configure the new Feature page layout:

What You Need to Remove

What You Need to Add

Remove the sections and their fields:

  • Additional Details

Add fields to the following existing sections:

  • Section Name: Information
  • Fields:
    • Feature Name
    • Epic
    • Application
    • #Users
    • Status
    • Value Type
    • Estimated Value
    • Complexity
  • Section Name: Description
  • Fields:
    • Description
    • Technical Assumptions
  • Section Name: Owners
  • Fields:
    • Product Owner
    • Created By
    • Owner
    • Architect
    • Last Modified By

Refer to the Salesforce article Create a new section in a page layout for more information.

Object: Applications

Here is how you need to arrange and configure the new Application page layout:

What You Need to Remove

What You Need to Add

  • NA

Add fields to the following sections:

  • Section Name: Information
  • Fields:
    • Name
    • Parent Application
    • Stability
    • Release Status

Add the following sections and the fields:

  • Section name: Description
    Number of columns: 1
  • Fields:
    • Description
  • Section name: Owners
    Number of columns: 2
  • Fields:
    • Product Manager
    • Created By
    • Owner
    • Last Modified By

Refer to the article Create a new section in a page layout for the instructions.

Object: User Story Tasks

Here is how you need to arrange and configure the new User Story Tasks page layout:

What You Need to Remove

What You Need to Add

  • NA

Add fields to the following sections:

  • Section Name: Information
  • Fields:
    • User Story
    • Status
    • Created By
    • Subject
    • Comments
    • Last Modified By

Refer to the Salesforce article Create a new section in a page layout for more information.

Object: Data Template

To enable the new data template experience, you’ll have to selectively retain and remove a few fields. Follow these steps:  

  1. Navigate to Setup > Object Manager > Data Template.
  2. Click Page Layouts > Data Template Layout.
  3. From the Data Template Detail tab, drag and drop all fields back to the Data Template Layout palette and retain the following fields: 
    1. Data Template Name 
    2. Description
  4. Click Save.

Object: User Story

We have introduced the following changes to the User Story Layout:

  1. Added the related lists—User Story History, Bundled Version, and Bundled Stories. To add these in your org, perform the following steps:
    1. Go to Setup > Object Manager > User Story.
    2. Click Page Layouts.
    3. Click Related Lists.
    4. Drag and drop User Story History, Bundled Version, and Bundled Stories into the Related Lists section.
  2. Add Comments instead of Hours Remaining in User Story Task related list. To do this in your org, perform the following steps:
    1. Go to Setup > Object Manager > User Story.
    2. Click Page Layouts.
    3. Click Related Lists.
    4. Scroll down to the User Story Task related list.
    5. Click the wrench icon to launch the properties screen.
    6. Select Hours Remaining from the right pane and click Remove.
    7. Select Comments from the left pane and click Add.
    8. Click Ok.
    9. Click Save.
  3. Page layout assignment for Utility record type of the User Story object to be set as User Story Layout. To do this perform the following steps:
    1. Go to Setup > Object Manager > User Story.
    2. Go to Record types.
    3. Click Page Layout Assignment.
    4. Click Edit Assignment.
    5. If you are unable to view Utility as the column header, click Next.
    6. Click the column header Utility, to select the entire column.
    7. Select User Story Layout from the dropdown list.
    8. Click Save.
Compact Layout

Object: Job Execution

Update the compact layout assignment in the Job Execution object to Job Execution:

Object: Job Step

Update the compact layout assignment in the Job Step object to Job Step:

Object: Epic, Feature, and Application

Ensure that the primary compact layout assignment for the Epic, Feature and Application objects are set to:

  • Epic Highlight Panel 
  • Feature Highlight Panel 
  • Application Highlight Panel

For example:

Lightning Record Pages

Package Record Page

  1. The default Package Record Page has been updated with the new packageVersionCreationPublishMessage and Result Status lightning web components. If you’re not using this record page as the default, you need to activate it in order to see and use all new implementations. If you have already activated it, it will be automatically upgraded.
  2. If you are using a cloned version of it, you need to manually add the packageVersionCreationPublishMessage and Result Status lightning web components. To do so, follow these steps: 
    1. Navigate to Setup > Object Manager > Package.
    2. Click on Lightning Record Pages and then on Package Record Page.
    3. Click on Edit.
    4. In the canvas, click on Record Detail. If you have not upgraded to Dynamic Forms, you must perform these additional steps; otherwise, continue with the next step:  
      1. Click on Upgrade Now and then on Next.
      2. Select the Package Layout and click on Finish.
      3. Add the Result Status Lightning web component component above the Tabs Lightning web component.
    5. Add the packageVersionCreationPublishMessage Lightning web component under the Highlights Panel.
    6. Click on Save

Package Version Record Page

  1. The default Package Version Record Page has been updated with the new packageVersionCreationPublishMessage and Result Status Lightning web components. If you’re not using this record page as the default, you need to activate it in order to see and use all new implementations. If you have already activated it, it will be automatically upgraded. 
  2. If you are using a cloned version of it, you need to manually add the packageVersionCreationPublishMessage and Result Status Lightning web components. To do so, follow these steps: 
    1. Navigate to Setup > Object Manager > Package Version.
    2. Click on Lightning Record Pages and then on Package Version Record Page.
    3. Click on Edit.
    4. In the canvas, click on Record Detail.  If you have not upgraded to Dynamic Forms, you must perform these additional steps; otherwise, continue with the next step:  
      1. Click on Upgrade Now and then on Next.
      2. Select the Artifact Version Layout and click on Finish.
    5. Add the Result Status Lightning web component above the Tabs Lightning web component.
    6. Add the packageVersionCreationPublishMessage Lightning web component under the Highlights Panel.
    7. Click on Save

Static Code Analysis Settings Record Page

  1. The default Static Code Analysis Settings Record Page has been updated with the new Generate Default Rule Set quick action. If you’re not using this record page as the default, you need to activate it in order to see and use all new implementations.  If you have already activated it, it will be automatically upgraded.
  2. If you are using a cloned version of it, you need to manually add the Generate Default Rule Set quick action. To do so, follow these steps: 
    1. Navigate to Setup > Object Manager > Static Code Analysis Settings.
    2. Click on Lightning Record Pages and then on Static Code Analysis Settings Record Page.
    3. Click on Edit.
    4. In the canvas, click on the Highlights Panel.  If you have not upgraded to Dynamic Actions, you must perform these additional steps; otherwise, continue with the next step:  
      1. Click on Upgrade Now.
      2. Select Start From Scratch and then on Finish.
    5. Click on Add Action.
      1. Type Generate Default Rule Set and select the one that’s under Quick Action
      2. Click on Done.
    6. Click on Save.

Promotion Record Page

If you are using a cloned version of the Promotion Record Page, make the following changes:

  • Replace the Promoted User Stories tab with the User Stories tab. To do this, perform the following steps:
  1. Click on the Tabs section of the canvas.
  2. On the right pane, click on the x next to Promoted User Stories.
  3. Next, click on Add tab to add the new User Stories tab.
  4. Select Custom as the tab label and type in User Stories, and click on Done.
  5. Finally, drag and drop the Promotion User Story Datatable custom component from the left pane into the User Stories tab:
    Promoted User Stories tab
  • Create a new tab called Changes:
  1. On the right pane, click on Add Tab to add a new tab.
  2. Select Custom as Tab Label and type in Changes, and click on Done.
  3. Drag and drop the Promoted User Stories Metadatas custom component from the left pane into the Changes tab.
  4. Move the tab on the right pane to locate it between User Stories and History & Approvals.

PIpeline Record Page

If you are using a cloned version of the Pipeline Record Page, make the following changes:

  • Remove the Promotion Automation and Deployment Automation fields and add the Commit Job Template, Promotion Job Template, and Deployment Job Template fields.
Additional Instructions

Picklist Value Updates

  • Navigate to the Execution Sequence field in the Job Step object and update the label of the picklist values as follows:
    • before -> Before Deployment
    • after -> After Deployment

Activate Chatter for Feed Tracking in Copado Plan

Enable chatter for the feed tracking of the following objects:

Object name

Feed tracking to be enabled for these fields

Application

  • Description
  • Name
  • Parent Application
  • Product Manager
  • Release Status
  • Stability

Epic

  • Application
  • Canceled Reason
  • Description
  • Epic Details
  • Epic title
  • Owner
  • Release
  • Status
  • Technical Assumptions

Feature

  • Application
  • Architect
  • Complexity
  • Description
  • Epic
  • Estimated Value
  • Feature Name
  • Owner
  • Priority
  • Product Owner
  • Status
  • Technical Assumptions
  • Value Type

User Story Tasks

  • Comments
  • Status
  • Subject
  • User Story

Here are the steps for you:

  1. Go to Setup, enter Feed Tracking in the Quick Find box.
  2. Select Feed Tracking.
  3. Select the object, for example, Epic.
  4. Select Enable Feed Tracking.
  5. Select the fields you want to track.
  6. Click Save.

Refer to Salesforce Help for more information on this topic.

Add Help Texts to Data Template Fields

We've updated the help texts for some of the fields under the Data Template object. If you are upgrading from a previous version of Copado, you’ll need to manually update the help texts for the following fields from the Data Template object:  

Field Name

Help Text

copado__Template_Source_Org__c

The main objects, fields, and related objects will be listed based on the Salesforce org data model of the selected credential. The Salesforce user linked to the credential must have access to all the fields and objects necessary for your deployments.

copado__Match_Record_Type__c

When matching record types, the records in the target Credential are assigned to the same record type as in the source Credential, if found. Otherwise, they are assigned to the default record type in the deploying user's profile.

copado__Match_Owners__c

When not matching owners, the owner of the deployed records in the target Credential will be automatically assigned to the user executing the deployment.

copado__Attachment_Options__c

Insert, update or remove attachments of the records that will get deployed.

Follow the steps below to add help text for a field:

  1. Navigate to Setup > Object Manager > Data Template.
  2. From the Fields & Relationships page, click the dropdown arrow next to the field that you want to edit. 
  3. Click Edit and enter the Help Text content in the text box.
  4. Click on Save.
Data Template View for Salesforce Classic

We’ve created a new and customized data template view for a better experience in Lightning. If you want to keep using the Data Template for Classic, please follow the following steps to override the standard view for Salesforce Classic:

  1. Log in to your Salesforce account and click Setup.
  2. Navigate to Object Manager > Data Template > Buttons, Links, and Actions > View.
  3. Click the dropdown arrow next to View and click Edit
  4. From the Salesforce Classic Override, select Visualforce page and choose DataTemplateSetup [copado__DataTemplateSetup] from the dropdown.
  5. Click Save.


How did we do?