Summer '21 (v18.23.1) - Release Notes

Updated 1 week ago by Copado Solutions

Key Features

Copado Plan

Copado Plan App

In this release, we are excited to introduce the Copado Plan app that is a one-point stop for all your project planning requirements. To support this application, there is a new license, Copado Plan, that replaces the old Copado Guest license.

Sprint Wall 2.0

The sprint wall view allows you to manage your sprints in a more friendly and agile way. This view provides very useful information regarding the status of the sprint and a whole picture of its content.

All New User Story Interface

We heard you and we have redesigned the user story to meet your requirements. User story tabs are now designed as per the user personas:

New US UI

This is a sneak peek of the Copado Plan features that will be released in WInter ‘22. More information available soon!

Pipelines
  • The user stories ahead and behind calculation enhancements where user stories in production are no longer available for back-promotion when:
    • You create a new sandbox based off of your Production environment.
    • You refresh a sandbox are now also available for mass back-promotions.
Functions

We have introduced new dynamic expressions and renamed some existing expressions to make them clearer. For more information about the new expressions, review the article Dynamic Expressions (New).

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.

If you have created custom tabs for the User Story Task or Team Dependency objects, remove them before installing this package. These have been created and added to our new app called Copado Plan.
OLS, FLS for New Object Fields and Tab Visibility

Make sure relevant profiles and permission sets have access to the below objects, fields and tabs:

Object: User Story Metadata

Type

Name/Label

API Name

Permission

CustomObject

User Story Metadata

copado__User_Story_Metadata__c

CustomField

Type

copado__Type__c

Read/Edit

CustomField

Json Information

copado__JsonInformation__c

Read/Edit

CustomField

Category

copado__Category__c

Read/Edit

CustomField

Action

copado__Action__c

Read/Edit

CustomField

File Name

copado__Metadata_API_Name__c

Read/Edit

CustomField

Directory

copado__ModuleDirectory__c

Read/Edit

Object: Sprint

Type

Name/ Label

API Name

Permission

CustomObject

Sprint

copado__Sprint_c

Custom Field

Actual Velocity

copado__ActualVelocity__c

Read/Edit

CustomField

Initial Planned Velocity

copado__InitialPlannedVelocity__c

Read/Edit

CustomField

Planned Velocity

copado__PlannedVelocity__c

Read/Edit

CustomField

Working Days Left

copado__Working_Days_Left__c

Read Only

Object: Pipeline

Type

Name/Label

API Name

Permission

Custom Object

Pipeline

copado__Deployment_Flow__c

CustomField

Commit Job Template

copado__CommitJobTemplate__c

Read/Edit

Object: Environment

Type

Name/Label

API Name

Permission

Custom Object

Environment

copado__Environment__c

CustomField

Commit Job Template Override

copado__CommitJobTemplateOverride__c

Read/Edit

Object: User Story Commit

Type

Name/Label

API Name

Permission

Custom Object

User Story Commit

copado__User_Story_Commit__c

CustomField

Status

copado__Status__c

Read

CustomField

Last Job Execution Id

copado__LastJobExecutionId__c

Read/Edit

CustomField

Commit Message

copado__CommitMessage__c

Read

Tabs

The relevant permission sets must have visibility set for these tabs:

  • Commit Changes
  • User Story Tasks
  • User Story Dependencies
Custom Metadata Types

The relevant permission sets must have visibility set for these custom metadata types:

  • copado.UISection
  • copado.ExtensionPackageConfiguration
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.

  • CommitAction
  • DatatableColumnsConfiguration
  • DatatableConstants
  • DatatableQueryConfiguration
  • DatatableServiceColumnConfig
  • DatatableServiceCtrl
  • FilterComponentController
  • FilterConstant
  • PromoteAction
  • PromoteActionService
  • PromotionDeployAction
  • ResultMonitorLWCHandler
  • SprintTriggerHandler
  • SprintVelocityRollUp
  • UserStoryCommitRequest
  • UserStoryCommitCtrl
  • UISectionHelper
  • UserStoryTriggerHandler
  • UserStoryTriggerHelper
  • UISectionHelper

The following classes have been removed from the Copado User permission set:

  • DeployCallback
  • DeploymentExecutionService
  • PromoteandDeployCallback
  • PromoteCallback
  • PromotionExecutionService
  • PromotionInvocableTest
  • ResultDetailService
  • ResultStatusContainerLWCHelper
  • ResultStatusHelper
  • ResultStatusLWCInterface

Field sets

SprintWall_Columns

  1. Go to Setup> Object Manager > User Story.
  2. Click Field Sets.
  3. Click SprintWall_Columns.
  4. Drag and drop these fields to the field set:
    1. User Story Reference
    2.  Record Type (Record Type ID)
    3. User Story Title
    4. Status
    5. Owner ID
    6. Priority
    7. Planned Points
    8. Epic
    9. Theme
    10. Last Modified Date

SprintWall_MassUpdate

  1. Go to Setup> Object Manager > User Story.
  2. Click Field Sets.
  3. Click SprintWall_MassUpdate
  4. Drag and drop these fields to the field set:
    1. Status
    2. Progress
    3. Owner
    4. Sprint
    5. Epic
    6. Theme
    7. Project
Layouts

Object: User Story Commit 

Make the following changes to the User Story Commit Layout in the User Story Commit Object:

  • Remove the View in Git field from the Information section.
  • Create a new section called Commit Information with two columns and order left-right, and add the following fields:
    • Commit Message
    • Status
    • View in Git
  • Remove the External ID from the layout

Object: User Story

  • Add the User Story History related list to the Bug Layout, Investigation Layout, and User Story Layout.
  • Add the Bundled Stories related list to the User Story Layout.

Object: Environment

  • Add the Installed Package Versions related list to the Environment Layout.

Object: Package Version

  • Add the Installed Package Versions related list to the Artifact Version layout.
Search Layouts

Promotion

Add the following fields to the Default Layout search layout in the Promotion object:

  • Promotion Name
  • Source Environment
  • Destination Environment
  • Project
  • Release
  • Status
  • Created Date
  • Last Modified By

Kanban Board

Add the following fields to the Default Layout search layout in the Kanban Board object:

  • Kanban Board Name
  • Field to read/update
  • Owner Alias
  • Last Modified Date

User Story Task

Add the following fields to the Default Layout search layout in the User Story Task object:

  • User Story Task Name
  • Subject
  • Status
  • User Story
  • Comments

Theme

Add the following fields to the Default Layout search layout in the Theme object:

  • Theme Name
  • Active
  • Status
  • Owner First Name
  • Theme Details

Team

Add the following fields to the Default Layout search layout in the Team object:

  • Team Name
  • Active
  • Department
  • Owner First Name

Sprint

Add the following fields to the Default Layout search layout in the Sprint object:

  • Sprint Name
  • Start Date
  • End Date
  • Status
  • Working Days Left
  • Release
  • Team
  • Project
  • Owner First Name
  • Sprint Goal

Release

Add the following fields to the Default Layout search layout in the Release object:

  • Release Name 
  • Project
  • Version
  • Planned Date
  • Status
  • Base Branch

Epic

Add the following fields to the Default Layout search layout in the Epic object:

  • Epic Ref
  • Epic Title
  • Status 
  • Release
  • Application
  • Owner First Name
Edit the existing tabs in All list view to show these fields.

Application

Add the following fields to the Default Layout search layout in the Application object:

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

User Story

Add the following fields to the Default Layout search layout in the User Story object:

  • User Story Reference
  • Record Type
  • Title
  • Status
  • Priority
  • Order
  • Feature
    Here you will find two fields with the same name Feature. To be able to select the correct field, you can update the name of the field by performing these steps to implement an override:

    1. Go to Setup > User Interface > Translation Workbench > Override.
    2. Select the criteria:3. Now, the row where Master Field Label: Feature and Field Type: Feature (Deprecated), enter the Field Label Override value as Feature (deprecated).
  • Epic
  • Theme
  • Project
Mini Page Layouts

Promotion

Add the following fields to the mini page layout in the Promotion object:

  • Platform
  • Status
  • Source Environment
  • Destination Environment
  • Project
  • Release
Lightning Record Pages

Function

If you are using a cloned version of the Function  Lightning record page, make the following changes:

  1. Make sure you have the functionsParametersContainer component in the Parameters tab. If you don’t, drag it from the Components pane and drop it inside the Parameters tab.
  2. Enable the canAddParameters and enableRequiredInput checkboxes:
Functions Parameters Container
  1. Save the changes.

Promotion

If you have already activated the Promotion Record Page as part of v18.11’s instructions and are using a custom version of this page (if you are using the out-of-the-box page provided by Copado, it will be automatically upgraded) edit it and make the following changes:

  • Remove the old Result Status Container Lightning web component.
  • Drag & drop two Result Status components into the region to the right of Notes & Attachments:
    • Type in Last_Promotion_Execution_Id__c as Field API Name on the first component.
    • Type in Last_Deployment_Execution_Id__c as Field API Name on the second component.
If you want to use the new Result Status component in a flow, all you need to do is pass the Id of the Job Execution record as a parameter. To do that, you can create an input variable of type Text.

If you want to use this component on any other page, you just need to create a text field to collect the execution Id of the job you want to track.

Result

If you are upgrading from v18.11 and are using the Result Status Container component on a custom Result Lightning record page, edit the page and replace that component with resultStatusMonitor. This step is not required if you are using Copado’s out-of-the-box Lightning record page.

Environment Record Page

If you are using a cloned version of the Environment Record Page, edit the page and make the following changes:

  1. Navigate to Setup > Object Manager > Environment.
  2. Click on Lightning Record Pages and then on your custom record page.
  3. Add the Commit Job Template Override field to the Pipeline Behavior section.
  4. Set the field visibility to Record > Platform Not Equal Salesforce.
  5. Click on Save.

Also, you need to add the Installed Package Versions related list.

Additionally, if you are working with a Multi-Cloud pipeline, make the below changes:

  1. Click on the Environment Variables tab on the canvas and then on the Environment Variables box and remove the filter under Set Component Visibility:
    Set Component Visibility
  2. Click on the text area below Environment Variables and then on the bin icon to delete it.
  3. Save your changes.

User Story

There is a new Lightning record page for the User Story object. If you want to activate it (this is recommended if you are working with Multi-Cloud), follow the steps below:

  1. Navigate to Setup > Object Manager > User Story.
  2. Click on Lightning Record Pages and then on User Story Record Page.
  3. Next, click on View.
  4. At the top right corner of the page, click on Activation and then on Assign as Org Default.
  5. Select Desktop as form factor.
  6.  Click on Next and then on Save.

User Story Commit

There is a new Lightning record page for the User Story Commit object. If you want to activate it, follow the steps below:

  1. Navigate to Setup > Object Manager > User Story Commit.
  2. Click on Lightning Record Pages and then on User Story Commit Record Page.
  3. Next, click on View.
  4. At the top right corner of the page, click on Activation and then on Assign as Org Default.
  5. Select Desktop as form factor.
  6. Click on Next and then on Save.
Additional Instructions

Disable the Cancellation Reason Required validation rule in the User Story object.

Perform these steps to manually disable the Cancellation Reason Required:

  1. Navigate to Setup > Object Manager.
  2. Select the User Story object which contains the validation rule you want to disable and click on Validation Rules.
  3. Select Cancellation Reason Required and click on Edit.
  4. Uncheck the Active checkbox and click on Save.

Bug Fixes

  • The Online Conflict Resolution panel is now loading for all files when trying to resolve conflicts in the Promotion record (KI-00477).
  • Schedule back promotion with Copado Continuous Delivery is now working correctly even if the source org of the back promotion didn't get the user stories with a forward promotion (KI-00491).


How did we do?