Summer '20 (v16.2) - Release Notes

Updated 1 year ago by Copado Solutions

Key Features

  • Copado now supports Apex pages (Visualforce), Apex components and Apex triggers when working with PMD.
  • A new picklist value named Resume Url has been added to the Dynamic URL Parameters field in the URL Callout deployment step. When you select this value, Copado sends the resume URL to the third-party tool involved in the callout step so that this third-party tool can easily update the job as completed or failed.
  • Security enhancement when registering with the Copado server in Copado Playgrounds. This registration process is entirely performed by Copado’s backend.
  • Quality gates in connection behaviors now support org-to-org user story metadata deployments.

Upgrade Instructions

If you are using the Copado_User permission set, you don't need to follow the 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 field:



API Name


Static Code Analysis Rule



Rule Reference


  • Add the Rule Reference field (copado__Rule_Reference__c) to the Static Code Analysis Rule layout.
PMD Instructions

As part of Copado’s enhancement to support Apex pages, components and triggers in PMD, there are some manual steps you need to take in order to start leveraging the new functionality:

  • Copado has implemented two new endpoints for static code analysis. Existing endpoints will still be used for older versions of Copado, but if you upgrade to Summer ‘20, you need to use the below endpoints instead:
    • Org Static Code Analysis: The new endpoint for this webhook is
    • User Story Static Code Analysis: The new endpoint for this webhook is
      If you are using any of these webhooks in a scheduled job, a continuous delivery quality gate or any other places where you may be using static code analysis webhooks, you will need to recreate them to ensure they include the updated endpoint.
  • To populate the new Rule Reference field and get the new Visualforce pages rules, you need to recreate the ruleset for the PMD static code analysis settings. To do this choose one of the options below:
    • Navigate to an existing Static Code Analysis Settings record and click on Generate Default RuleSet.
    • If you have made any customizations to the ruleset and don’t want these customizations to be overwritten, follow the steps below:
      1. Export your current ruleset (Static Code Analysis Rule records) with the relevant fields:
        Message (copado__Message__c)
        Rule Name (copado__Rule_Name__c)
        Priority (copado__Priority__c)
      2. Use the Generate Default RuleSet button to recreate the ruleset.
      3. Once the ruleset is generated, export the Id and the Rule Name (copado__Rule_Name__c) of the generated rules.
      4. In a spreadsheet, use the Rule Name to match rules (you can use the Vlookup formula) and retrieve from your ruleset’s backup (step 1) the corresponding Message and Priority values. 
      5. Update the resulting file.

Bug Fixes

  • The “Maximum view state size limit” error returned when promoting or back-promoting user stories in bulk from the Pipeline page has been fixed.

How did we do?