Summer '20 (v16.5) - Release Notes
- There is a new record matching formula functionality in Copado Data Deploy that allows you to build a formula in order to populate a value for the external Id field in the records you are migrating in your data template.
- Copado now prevents users from entering duplicate names for Compliance Rule Groups.
- The error message defined in a compliance rule can now also be found in the Compliance Findings object.
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:
Record Matching Formula
Configuration Source Org
Hash External ID Formula
Rule Error Message
Record Matching Formula
FieldSets, Visualforce Pages and Apex Classes
Make sure the relevant profiles and permission sets have access to the below Apex classes and Visualforce pages:
Add the Rule Error Message field (copado__Rule_Error_Message__c) to the Compliance Finding Layout.
Add the Field 1, Field 2, Field 3, Hash External Id Value and Configuration Source Org fields, in this order, to the Record Matching Formula’s Default search layout
Add the Field 1, Field 2, Field 3, Hash External Id Value and Configuration Source Org fields to the Record Matching Formula tab. To do this, follow the steps below:
- Navigate to the Record Matching Formula tab.
- Select the All list view.
- Click on the gear icon at the top right corner and click on Select Fields to Display.
- Move the Field 1, Field 2, Field 3, Hash External Id Value and Configuration Source Org fields to the Visible Fields column.
- Click on Save.
- The online conflict resolution feature is no longer triggered due to empty lines, Copado just trims them (KI-00271).
- The Disable Auto-Resolve functionality no longer applies to conflicts in files that are not part of user story commits. Those files will continue to be marked as Auto-Resolve by default, and users will be able to choose whether they want to manually resolve them or let Copado resolve them.