Winter '21 (v17.13) - Release Notes

Updated 1 day ago by Copado Solutions

This is a minor release of Winter ‘21 that includes the following enhancements and fixes.

Key Features

Multi-Cloud

Copado has developed a new set of features that enable you to implement a DevOps process that works with different clouds such as MuleSoft or Copado backend. For more information about Multi-Cloud, review the article Introduction to Multi-Cloud

If you are interested in joining our pilot program, please fill out this form.

Copado Functions

There is a new deployment step for functions that enables you to execute a function as part of your deployment and trigger different automations before or after a metadata deployment or other deployment steps. This feature is in the pilot stage. For more information, review the article Deployment Step: Function.

Copado Continuous Delivery

Copado has introduced an enhancement in the user stories ahead and behind calculation. Now, when you create a new environment, the user stories that were in production before the date of creation of the new environment are no longer available for back-promotion.

Copado Compliance Hub
  • A new Compliance Scope lightning web component has been created for Compliance Rule that replaces the old Visualforce component. The new features that have been included are the followings:
    • Error messages have been added when creating a new rule if an error is found. For example, if you’re missing an API key or a Copado Compliance Hub license, you will receive a message with the error and you’ll not be able to save the record until fixed.  
    • 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 have been 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 will be displayed and you will not be able to save the record until the error is fixed.
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. 
Static Code Analysis
  • The Rule Reference field has been marked as a required field on the Static Code Analysis Rules record.
Copado Core
  • A new global method to return recent changes in Global API class has been 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 full refresh or refresh recent changes, the components will be 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 have been added in the Online Conflict Resolution panels to provide more information about how the panels work, and the following labels have been renamed:  
    • In the 2 panels view:
      • Feature Branch label has been renamed Conflicts in Feature branch.
    • In the 3 panels view:
      • Feature Branch label has been renamed Conflicts in Feature branch.
      • Promotion Branch label has been renamed Conflicts in Promotion branch.
Copado CLI
  • New commands are added to the Copado CLI.
  • You can upgrade using the command sfdx plugins:update.
  • For more information, refer to CLI Commands.

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 the relevant profiles and permission sets have read and write access to the following objects and fields:

Type

Name/Label

API Name

CustomObject

Environment

copado__Environment__c

CustomField

Deployment Automation Override

copado__Deployment_Automation_Override__c

CustomField

Platform

copado__Platform__c

CustomField

Promotion Automation Override

copado__Promotion_Override__c

Type

Name/Label

API Name

CustomObject

Credential

copado__Org__c

CustomField

Platform

copado__Platform__c

Type

Name/Label

API Name

CustomObject

Deployment

copado__Deployment__c

CustomField

Api Name

copado__ApiName__c

CustomField

Do Not Update Promotion

copado__Do_Not_Update_Promotion__c

CustomField

Parent Deployment

copado__Parent_Deployment__c

Type

Name/Label

API Name

CustomObject

Pipeline

copado__Deployment_Flow__c

CustomField

Deployment Automation

copado__Deployment_Automation__c

CustomField

Promotion Automation

copado__Promotion_Automation__c

CustomField

Platform

copado__Platform__c

Custom Metadata Types
  • MultiCloudAutomation
  • StandardResources
Tabs

Standard Records

FieldSets, Visualforce Pages, and Apex Classes

Apex Classes

Make sure relevant profiles and permission sets have access to the following Apex classes:

AuthGrantService

CheckCBMLicense

ComplianceRuleCriteriaSelector

ComplianceRuleCriteriaValidator

ComplianceRuleLogicValidator

ComplianceRuleManagerCtrl

ComplianceRulePermissionsValidator

ComplianceRulesSelector

ContentDocumentLinksSelector

CreateDefaultOrg

CreateLocalConnection

CreateRegularConnection

CreateStandardRecords

CredentialRecordPageHandler

CredentialRedirectionHandler

CredentialsButtonsHandler

DeploymentFlowStepsSelector

DeploymentsSelector

FunctionStepExecutionCallback

InvokeApexTestCallForCredential

InvokeComplianceScanForCredential

InvokeStaticCodeAnalysisForCredential

MultiCloudAutomationsSelector

NonSalesforcePipelineOperationService

PipelineConnectionCreateService

PipelineOperationsHelper

PipelineOperationsInterface

ResultMonitor

SalesforcePipelineOperationsService

SetDefaultAutomationTemplate

SObjectDataLoader

SourceMemberResult

StandardRecordStatusCtrl

StandardResourcesSelector

StaticResourcesSelector

SupportedObjectsSelector

TestAuthGrantService

TestPipelineConnectionCreateService

ValidatePlatformType

ValidationResult

Layouts

Add the new fields and actions to the relevant layouts and remove the fields, buttons and related lists from the required layouts:

Compliance Rule

  • Remove the AddCCHRuleCriteria Visualforce component from the layout.
  • Remove the Criteria section.

Credential

  • Add the following quick actions to the Org Credential layout:
    • Authenticate
    • Copado DX (only visible if the org type is a scratch org).
    • Open Credential
    • Run All Test
    • Run Compliance Scan
    • Run Static Code Analysis
  • Add the Platform (copado__Platform__c) to the Org Credential layout.

Environment

  • Add the following fields and related lists to the Environment layout:
    • Deployment Automation Override (copado__Deployment_Automation_Override__c)
    • Platform (copado__Platform__c)
    • Promotion Automation Override (Promotion_Override__c)
    • System Properties.

Pipeline

Add the following fields and related lists to the Pipeline Layout v17 layout:

  • Platform (copado__Platform__c)
  • System Properties

System Properties

The ParentId field (copado__ParentId__c) is no longer a required field. Follow the steps below to update it to read only:

  1. Navigate to Setup > Object Manager > System Properties.
  2. Click on Page Layouts and then on System Property Layout.
  3. Locate the Parent Id field and click on the wrench icon.
  4. Select the Read-Only checkbox.
  5. Click on Ok and then on Save.
Page Layout Assignments

Credential 

Update the page layout assignment for the Credential and Pipeline records and assign the relevant profiles these layouts:

  • Org Credential 
  • Pipeline Layout v17 
Additional Instructions
  • As part of Copado Compliance Hub’s new features, the default FlexiPage Compliance Rule Record Page has been updated with the new Compliance Scope lightning web component. 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. To do so, follow these steps: 
  1. Navigate to Setup > Object Manager > Compliance Rule.
  2. Click on Lightning Record Pages and then on Compliance Rule Record Page.
  3. Next, click on View.
  4. On the top right corner of the page, click on Activation and then on Assign as Org Default:

Activation: Compliance Rule Record Page

  1. Select Desktop as form factor. 
  2. Click on Next and then on Save.
  • A new picklist field called Platform has been created and added to the Pipeline and Environment objects to support multi-cloud pipelines. Navigate to these records and update this picklist based on the pipeline you are going to use:
    • Salesforce: Choose this option if you are working with a Salesforce pipeline.
    • Other: Choose this option for non-Salesforce pipelines.
Additional Upgrade Instructions for Multi-Cloud

If you are working with functions or want to use the new Multi-Cloud feature, you also need to perform the below instructions. These are only required for these two features. Otherwise, you don’t need to do any further upgrades.

  • There is a new FlexiPage for the Org Credential, Environment, Pipeline and Pipeline Connection record pages. To activate this new FlexiPage, follow these steps:
  1. Navigate to Setup > Object Manager > Credential.
  2. Click on Lightning Record Pages and then on Org Credential 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.
  7. Repeat the same process for the Environment Record Page, the Pipeline Record Page, and the Pipeline Connection Record Page.
  • Add the System Properties tab to the Pipeline Record Page. To do that, follow these steps:
  1. Navigate to an existing Pipeline record.
  2. Click on the gear icon at the top right corner of the screen and then on Edit Page.
  3. Next, click on the tabs section and then on Add Tab on the right-hand side of the screen.
  4. Click on the Details link and select Custom in the Tab Label drop-down menu.
  5. Type in System Properties for custom label and click on Done.
  6. Click on the System Properties tab and drag and drop a Related List - Single component to the canvas.
  7. Remove the default selection from the Related List picklist field and select System Properties:

System Properties in the Pipeline Record Page

  1. Click on Save and then on Activate to ensure the changes are displayed on the page.
  • If you are working with functions, you need to deactivate the Deployment Completed workflow rule to ensure your functions are working as expected. This workflow rule is used by Copado to send an email with the deployment results once a deployment completes. To deactivate this workflow rule, follow these steps:
  1. Go to Setup > Workflow Rules.
  2. Locate the Deployment Completed workflow rule and click on Deactivate.

Deployment Completed workflow rule

Bug Fixes

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


How did we do?