Release Notes

Version 9

 
Important: This is a major release. Please, read the Upgrade Instructions before upgrading, and follow them carefully afterwards. 

Key Features:
  • Back Promotion Feature on User Stories
    • User stories ahead and behind are now displayed in the Branch Management application and in the User Story layout so that you can promote the ones that are ahead and back-promote the ones that are behind. (more information)
  • Redesigned and Improved Branch Management Page
    • Promote and Back Promote User Stories with their metadata and related Deployment Tasks (more information).
    • Add as many environments as required with our infinite canvas size.
    • Manage more environments with less screen real estate.    
  • User Story Enhancements
    • New record types created for user stories allowing you to manage different types of records: bugs, user stories and investigations.
    • User Story Deployment Tasks now support: Data, Bulk Data, Apex Code, URL Callout, Custom Settings, Delete Metadata, and more (more information).
    • Quickly identify failing methods or lack of code coverage within the User Story Page.
    • Stop Indexing Medatada:  Allows Copado users to decide which User Stories should be considered by Copado's Overlap Awareness to indicate potential conflicts.
  • Deployment Task Custom Settings Enhancements.
    • Copado automatically filters through components to show only custom settings instead of all objects.
  • New License, Copado Agile Delivery (CAD)
    • Affordable and specially designed to bring all stakeholders onboard.
  • Support for Community and Portal Users in Copado License Manager.
  • Agile Sprint Virtual Wall
    • Easily Manage  your Sprints through Copado's Sprint Wall (more information).
  • Security Improvements.
    • Copado force.com application now works without passing the user session id to the backend. Instead it will fully rely on the OAuth2 protocol. With this change, now Copado forces users to create the Org Credential for their Copado user. If the user does not have an Org credential for it's Copado User, the application will throw an error.
  • Blocked Branches an Queued Jobs
    • Copado awares you whenever there are branches being updated while you are on a screen that also could write to the same branch (more information).
  • Lightning Experience Kanban Board
Upgrade Instructions:
  • Create an Org Credential for each user
    • Every Copado user must create his own Org Credentials to continue using the application. Avoiding this, will completely restrict the interaction with Copado.
    • Exclude Old User Stories from CBM 
      • From now on Copado scans for User Stories that are in higher environments and that have not been back promoted. This is to make users aware of components promoted ahead of them from a different Source Org. Since this feature is new and there are no previous records of User Stories Ahead and Behind, you need to exclude all old User Stories from the count. 
      • The User Story Page has an Exclude From CBM checkbox. Mass Update it for all the closed or released user stories that you don't want to keep track of in User Stories Ahead and Behind. You can accomplish this by executing an apex anonymous snipped, or by mass updating records with a list view.
# Use this snipped to exclude all previous User Stories
# from back promotion calculations
# or tailor the WHERE clause to your needs
for(List<
copado__User_Story__c> uss:[select Id from copado__User_Story__c where copado__Exclude_from_CBM__c = false limit 6000]){
  for(copado__User_Story__c us:uss){
    us.copado__Exclude_from_CBM__c = true;
  }
  update uss;
}
  • Grant access to the following new components:
    • OLS & FLS: 
      • Copado_Notification__c 
      • Deployment_Task__c 
      • User_Story_Task__c 
    • FLS: 
      • User_Story__c.Stop_Indexing_Metadata__c 
      • User_Story__c.Exclude_From_CBM__c 
      • User_Story__c.Triggers_Without_Coverage__c 
      • User_Story__c.Classes_Without_Coverage__c 
      • User_Story__c.Failing_Methods__c 
      • User_Story__c.Order__c 
      • Promotion__c.Back_Promotion__c 
      • Copado_Notification__c.Status__c 
      • Copado_Notification__c.isSuccess__c 
      • Copado_Notification__c.isFinished__c 
      • Copado_Notification__c.Type__c 
      • Copado_Notification__c.Matching_Key__c
      • Deployment_Flow_Step__c.Commits_Ahead__c
      • Deployment_Flow_Step__c.Commits_Behind__c
      • Deployment_Flow_Step__c.Destination_Branch__c
      • Deployment_Flow_Step__c.Last_Merge_Base__c
      • Deployment_Flow_Step__c.Last_Merge_CBM_Sync__c
      • Deployment_Flow_Step__c.Last_Pull_CBM_Sync__c
      • Deployment_Flow_Step__c.Merge_Auto_Resolved_Files__c
      • Deployment_Flow_Step__c.Pull_Auto_Resolved_Files__c
      • Deployment_Flow_Step__c.Sync_Merge_State__c
      • Deployment_Flow_Step__c.Sync_Pull_State__c
    • Visual Force Page: 
      • SprintVirtualWall
      • ViewDeploymentTask
      • EditDeploymentTask
    • Record Type Assignment: 
      • User_Story__c.User_Story 
      • User_Story__c.Bug 
      • User_Story__c.Investigation 
    • Tab Visibility 
      • Copado Notifications 
    • Chatter 
      • Enable FeedTracking for the Sprint Object on Setup > Customize > Chatter > FeedTracking.
Note: Copado User Permission Set has been updated adding all FLS & OLS required for Copado V9.
  • Add to Layout: 
    • Copado Notification Layout: 
      • Copado_Notification__c.Status__c 
      • Copado_Notification__c.isSuccess__c 
      • Copado_Notification__c.isFinished__c 
      • Copado_Notification__c.Type__c 
      • Copado_Notification__c.Matching_Key__c 
    • User Story Layout: 
      • User_Story__c.Stop_Indexing_Metadata__c 
      • User_Story__c.Failing_Methods__c 
      • User_Story__c.Triggers_Without_Coverage__c 
      • User_Story__c.Classes_Without_Coverage__c 
    • Deployment Flow Step Layout
      • Deployment_Flow_Step__c.Commits_Ahead__c
      • Deployment_Flow_Step__c.Commits_Behind__c
      • Deployment_Flow_Step__c.Destination_Branch__c
      • Deployment_Flow_Step__c.Last_Merge_Base__c
      • Deployment_Flow_Step__c.Last_Merge_CBM_Sync__c
      • Deployment_Flow_Step__c.Last_Pull_CBM_Sync__c
      • Deployment_Flow_Step__c.Merge_Auto_Resolved_Files__c
      • Deployment_Flow_Step__c.Pull_Auto_Resolved_Files__c
      • Deployment_Flow_Step__c.Sync_Merge_State__c
      • Deployment_Flow_Step__c.Sync_Pull_State__c
  • Remove from Layout: 
    • Deployment Flows Layout: 
      • DeploymentFlowConnections.page

Backend Upgrade 2017-09-04

Key Features:

  • Server Metadata API upgrade: we have upgraded to Salesforce Metadata v40
    • More supported Metadata types will be automatically available. 
    • IMPORTANT: Salesforce Permission sets behaviour changes:
      • Please read carefully the following Salesforce article.
      • When performing Org to Org deployments the entire permission set will be retrieved and it will replace the target entirely, this means that incremental deployment for Permission sets is not possible with out pre processing of the permission sets.
      • When using Copado Branch Management (CBM), Copado will merge the incremental permission set changes coming from multiple streams and deploy the resulting merged permission sets, therefore incremental permission set deployments are still possible.
      • With CBM + Copado Change Management (CCM) running on v39 Copado deploys only the incremental permission sets e.g. only the FLS of a User Story. With CBM + CCM running on v40 Copado must deploy the entire merged permission set, otherwise Salesforce revokes all the other permissions that are not part of the deployment. This means the permission set will be deployed on the target exactly as in Git, which is the predictability that Salesforce is trying to achieve with this change.
      • Additional reading:

BETA: Backend Upgrade 2017-08-21 (coming soon)

Key Features:

  • Server Metadata API upgrade: we have upgraded to Salesforce Metadata v40
    • More supported Metadata types will be automatically available. 
    • IMPORTANT: Salesforce Permission sets behaviour changes:
      • Please read carefully the following Salesforce article.
      • When performing Org to Org deployments the entire permission set will be retrieved and it will replace the target entirely, this means that incremental deployment for Permission sets is not possible with out pre processing of the permission sets.
      • When using Copado Branch Management (CBM), Copado will merge the incremental permission set changes coming from multiple streams and deploy the resulting merged permission sets, therefore incremental permission set deployments are still possible.
      • With CBM + Copado Change Management (CCM) running on v39 Copado deploys only the incremental permission sets e.g. only the FLS of a User Story. With CBM + CCM running on v40 Copado must deploy the entire merged permission set, otherwise Salesforce revokes all the other permissions that are not part of the deployment. This means the permission set will be deployed on the target exactly as in Git, which is the predictability that Salesforce is trying to achieve with this change.
      • Additional reading:
Version 8.8

Key Features:
  • Static Code Analysis for Org Credentials and User Stories (more information).
    • Expedited code review.
    • Quality Gates Enforcement.
    • Automatically Detect code inefficiencies, errors and bad practices.
    • Run Static Code Analysis for:
      • Complete Org.
      • Single User Storie Apex Classes.
      • Promotion with collection of User Stories Apex Classes. 
  • Type-Filtered MetaData Grid (more information).
    • Filter and Retrieve MetaData by Type.
    • Optional Activation (Interchangeable with Classic Grid).
    • Recommended when working with extensive MetaData.
Upgrade Instructions:

Activate the optional Type-Filtered MetaData Grid feature:
Setup > Custom Metadata Types > Copado Setting >
                         Edit Big MetaData > Check Enabled > Save.

Grant access to the following:
  • OLS & FLS
    • Static_Code_Analysis_Settings__c
    • Static_Code_Analysis_Result__c
    • Static_Code_Analysis_Rule__c
  • FLS:
    • Environment__c.Current_SCA_Score__c
    • Environment__c.Maximum_SCA_Score__c
    • Deployment_Flow__c.Static_Code_Analysis_Settings__c
  • Visual Force Page:
    • GenerateStaticCodeAnalysisRuleSet
    • UserStoryCodeAnalysisRequested
    • StaticCodeAnalysisSummary
  • Tab Visibility: 
    • Static_Code_Analysis_Settings__c
Note: We have Included Static_Code_Analysis Permission Set, that includes all the OLS, FLS, Tab Visibility and Visual Force Pages Visibility required for Static Code Analysis feature. This Permission Set can be assigned to the required users. 

Add to Layout:
  • User Story Layout:
    • Related List: 
      • Static_Code_Analysis_Result__c
    • Button:
      • Run_Static_Code_Analysis
      • Static_Code_Analysis_Summary
  • Deployment Flow Layout:
    • Field: 
      • Deployment_Flow__c.Static_Code_Analysis_Settings__c
  • Environment Layout:
    • Field:
      • Environment__c.Maximum_SCA_Score__c
      • Environment__c.Current_SCA_Score__c 
  • Org Layout:
    • Related List:
      • Static_Code_Analysis_Result__c

BETA: Backend Upgrade 2017-08-04

Key Features:

  • Server Enhancement: we have boosted the performance in many aspects
    • Any Git operation will run faster, even for huge repositories with thousands of branches and commits. 
    • As repositories grow over the time, Copado performance will not be affected, thanks to the Git efficiencies implemented in this release.
    • Git Snapshots run much faster, up to X8.

Backend Upgrade 2017-07-13

Key Features:

  • Server Enhancement: From now on, all CBM validation and deployments will generate a package.xml attachment within the Deployment Flow Step record. 
    • Note: Make sure you have the attachment related list included on the Deployment Flow Step layout.

Version 8.6.1

Key Features:

  • Integrate Copado with an external CI server, like Jenkins, using the new External CI Jobs. Click here for more information.
  • Github Pull Requests are now integrated within Copado User Stories. Click here for more information.
  • Added support for PUT, PATCH and DELETE methods on URL Callout steps in Copado deployments.
  • The user story metadata index is now updated automatically whenever you add/commit metadata in a user story. A new detail page shows you other user stories where potential conflicts has been detected. Click here for more information.
  • Improvement: Create validation deployments in Git Promotion records without having to Combine Metadata and Git Metadata.
Upgrade Instructions:
  • Go to Setup -> Create Objects -> User Story -> User Story Layout, and add the "User Story Pull Requests", "User Story Metadata", "External CI Jobs" and "External CI Job Results" related lists. Edit the "User Story Metadata" related list and add the new "Status Icon" field.
  • Go to Setup -> Create Objects -> Environment -> Environment Layout, and add the "External CI Jobs" and "External CI Job Results" related lists.
  • Go to Setup -> Create -> Apps -> Branch Management -> Edit -> Add the "External CI Settings" and "External CI Jobs" tabs.

New Objects and Fields:
(Make sure OLS, FLS, Tab Visibility and Layouts are properly set for the following components).

  • New Custom Fields:
    • User_Story_Metadata__c.Status_Icon__c
  • New Visual Force Pages:
    • UserStoryMetadata
    • EditExternalCISetting
    • ViewExternalCIJob
    • ViewExternalCISetting
    • EditExternalCIJob
  • New Tabs:
    • External CI Setting
    • External CI Job
  • New Layouts:
    • External CI Job Layout
    • External CI Job Result Layout
    • External CI Setting Layout
    • Pull Request Review Layout
    • Pull Request Layout
  • New Objects:
    • External CI Job Result
    • External CI Setting
    • External CI Job
    • Pull Request Review
    • Pull Request

Backend Upgrade 2017-06-22

Key Features:

  • Enhancement:   Boosted performance when processing YAML files for big orgs with loads of rules .

Version 8.0

Key Features

  • Explore all FLS, OLS, System Permissions and User Permissions of a Copado Permissioner Persona with the new Permission Set Explorer tab. Follow this link to get more information.
  • Change Management is now integrated with Selenium Testing. You can manage Regression and User Story Selenium Tests from a very simple UI. This lets you increase your quality standards by running automated tests for both new features and regression testing. Follow this link to get more information.
  • Promotion Selenium Tests: easily run and view results of Regression and User Story tests within a promotion page. Follow this link to get more information.
  • On top of the user story page you will see the different Environments of the Deployment Flow starting with the Environment where the user story is located.
  • Create and upload global "find and replace" rules in a .YML file for the rules to be applied in Git commits and Org-to-Org and Git-to-Org deployments. Follow this link to get more information.

Upgrade instructions
  • Go to Setup -> Create Objects -> Deployment Flow -> Deployment Flow Layout, and add the button "Manage Regression Tests".
  • Go to Setup -> Create Objects -> User Story -> User Story Layout, and add the button "Manage Selenium Tests", and add the "User Story Selenium Tests" related list above the "Test Scripts" related list.
  • Go to Setup -> Create -> Apps -> Copado Permissioner -> Edit -> Add the "Permission Set Explorer" tab.
  • Go to Setup -> Create Objects -> Selenium Test Group -> Selenium Test Group Layout, and add the new fields "Status Date", "Environment" and "Type"
  • Go to Setup -> Create Objects -> Selenium Test Run -> Selenium Test Run Layout, and add the new field "Last Status Date".

New Objects and fields: make sure OLS, FLS, Tab Visibility and Layouts are properly set for the following components

  • New custom Fields:
    • Selenium Test Group: Status Date
    • Selenium Test Group: Environment
    • Selenium Test Group: Type
    • Selenium Test Run: Last Status Date
  • New Visualforce pages:
    • ManageSeleniumTesting
    • PermissionSetExplorer
  • New tabs:
    • Permission Set Explorer (Copado Permissioner App)

BETA: Backend Upgrade 2017-05-29

Key Features:

  • Enhancement:   When doing Git Promotions, Copado will deploy from Git only the selected components selected on the User Stories, with support to nested components. This means that if a User Story includes 1 field and 1 FLS, Copado will deploy from Git only 1 field and 1 FLS, and avoid deploying existing components. This will make deployments fasters and increase the success rate when environments are out of sync. More over, this functionality can be use to select Test Classes, even if they haven't change, so that those test classes will be used to measure the User Story code coverage, and later RunSpecifiedTest deployments.
  • Enhancement:   Standard tabs are now listed on the Metadata cache. Since the Metadata describe doesn't list the standard tabs, Copado has to retrieve the list using SOAP API.

Backend Upgrade 2017-05-11

Key Features:

  • Enhancement:  When using "Run Specified Tests" test level on Git Promotions, Copado will Run all apex test classes that where selected on the "Commit Files" screen, regardless if there were changes or not on the Git commit.

Backend Upgrade 2017-05-09

Key Features:

  • Enhancement:  Better and smarter auto-resolve conflicts. Copado conflict resolution engine now takes into account the User Story commit metadata selection to wisely merge XML files at the nested component level.

Copado v7.1.6 patch 2017-04-27

Key Features:

  • Enhancement:  CCM Only users are now able to Sync Environments within the Branch Management app, as long as they have been granted permissions at the Environment level.

Backend Upgrade 2017-04-27

Key Features:

  • Enhancement:  Support for committing nested Sharing Rules. This means that a developer can push a single sharing rule into Git, while preserving all the other sharing rules on the git repository, same as Custom Fields and FLS .

Backend Upgrade 2017-04-25

Key Features:

  • Enhancement:  An email is sent to the User when Copado performs an auto-resolve conflict with full details about the affected files.

Backend Upgrade 2017-04-18

Key Features:

  • Enhancement:  CBM sync functionality will only validate/deploy files that are different.

Backend Upgrade 2017-04-14

Key Features:

  • Enhancement:  added support for auto-resolve-conflicts within AuraBundles files

Backend Upgrade 2017-04-08

Key Features:

  • Bug fix: Quick Deploy + Git Promotions 
  • Enhancement: Better XML merge for RecordType Pick-list Values
  • Enhancement: When a file is created and deleted in Git, it will be ignored on the package.xml

Version 7.1

Key features:

  • New validations to enforce Best Practices and naming convention when using CBM Deployment Flows. Follow this link to get more information.
  • When using Copado Branch Management with Change Management, Change Management users can now promote and deploy User Stories to sandboxes.
  • New "Retrieve Only" checkbox for Commit Files. With this, you will be able to pull OLS/FLS for Profiles and PermissionSets, without having to commit/deploy the original fields or objects. This feature will give you a more granular control over Profiles and PermissionSets in regards Objects, Fields permissions, record Types and page layout assignment. Follow this link to get more information.
  • New Git Snapshot Field Set, so you can customize the information displayed in the Git Snapshot record.
  • New User Story and Promotion Field Sets, so you can customize the information shown in the User Stories related list on the Promotions, and in the Promotions Edit view. Follow this link to get more information.
  • Sharing button on Copado Visualforce pages so you can handle the manual sharing model even for Copado objects that have their layouts overridden. You will find this button available in the following objects: Org Credentials, Deployments, Git Repositories, Org Differences and Snapshot Differences.
  • Manage Environmental Variables from a Grid, so you can overview all Environmental Variables in a Deployment Flow in one single grid, boosting your productivity when editing values, creating new variables, etc. Follow this link to get more information.
  • URL links to commits and branches, so you can navigate directly from Copado to your Git repository provider.
  • Deploying a Process Builder Flow is easier than ever, now will be able to deploy a Flow that is active in the Source Org, and the Flow will be activated automatically in the Destination Org. You can commit an active flow to your repository, and deploy from the commit. Follow this link to get more information.
  • Improved troubleshooting in the Manage Branches page. It now has a section with the logs of the latest sync.
  • Recommit User Stories: now you can combine metadata selections from one or more User Stories and recommit them again, to quickly add several new changes, or remove unwanted items. If you need to remove unwanted items, make sure you delete the feature branch and reset the head of the Org's branch, before recommitting again.

Upgrade instructions
  • CBM validations are implemented by default. You can disable them by checking the "Disable validations" checkbox.
  • For Change Management users to "Promote and Deploy" a User Story, the User Story's Project or Release must be linked to an active deployment flow that has assigned a valid Git Repository and a Main Branch. Also, the destination Environment of the Promotion must be a sandbox.
  • Edit the Git Snapshot field set in order to include your custom information in the Git Snapshot Visualforce page.
  • Edit the Promotion field set in order to include your custom information in the Promotion Visualforce page.
  • Edit the User Story field set in order to customize the columns that are shown in the Promotions Visualforce page. Notice the new image with the link that will take you to the User Story.
  • Notice that the new sharing buttons will be available depending on your Sharing Settings.
  • In the Git Repository, the Branch Base URL is the base url for all your branches (eg. https://github.com/account/repo/tree/)
  • In the Git Repository, the Commit Base URL is the base url for all your commits (eg. https://github.com/account/repo/commit/)
  • Go to Setup -> Create Objects - > User Story -> User Story Search Layouts and edit User Stories List View, and add the button Recommit User Story.

New Objects and fields: make sure OLS, FLS, Tab Visibility and Layouts are properly set for the following components

  • New custom FIelds:
    • Deployment Flow -> Disable_Validations__c
    • Deployment Flow -> Equal_Branch_Environment_Name__c
    • Git Repository -> Branch_Base_URL__c
    • Git Repository -> Commit_Base_URL__c
    • Git Snapshot -> View_in_Git__c
    • Snapshot Commit -> View_in_Git__c
    • User Story -> View_in_Git__c
    • User Story Commit -> View_in_Git__c
  • New Visualforce pages:
    • ManageEnvVars

Backend Upgrade 2017-03-27

Key Features:

  • Add Metadata API support for Geo Location fields.
  • Automatically transform v38 picklist into v39 valueSet

Backend Upgrade to Metadata v39 + much more

Key Features:

  • Metadata API version upgrade to  Spring 17 v39
  • Automatic merge conflicts resolutions for XML based Metadata, when Git is unable to merge two xml files, e.g. a Custom Object, Copado will perform a semantic XML merge, which means that Copado will combine the XML nodes of the conflicting files and produce a wellformed xml file to resolve the conflicts. This will avoid all merge conflicts.
  • Much faster! We introduced many performance enhancements that will make Copado be even faster

Version 6.1

This is a silent release, it contains same functionality as v6.0 but  without an unwanted Chatter dependency which was introduced in v6.0 and required Chatter enabled orgs upon installation. 

Version 6.0 - Continuous Delivery for CCM, Copado Permissioner and more ...

Key Features:

  • We are introducing Continuous Delivery (CD) for Copado Change Management (CCM). With a simple checkbox (Promote and Deploy) a User Story can be automatically promoted and deployed to the next Environment. More info here.
  • We are introducing Copado Permissioner (CP). Users now have the ability to define Personas and Persona Permissions, so that when assigning a Persona to a User, the User will get automatically the Permission Sets assignments permanently or for defined period of time.
  • The Copado application suite is now shipped with a variety of Permission Sets that will help customers to define their security model for Copado.
  • Copado Permissioner can be used to manage permissions of any Salesforce application, not just Copado.
  • Copado License Manager displays the user list sorted by name.
  • Default Org Credential for Promotions. Release managers won't have to own credentials to each environment if there is a Default one.

Upgrade instructions

User Story page layouts has to be edited in order to include the new User Story fields used for the new Continuous Delivery feature.

New Objects and fields, make sure OLS, FLS and Tab Visibility are properly set for the following components.

  • New Custom Objects: Persona, Persona Permission and User Persona Assignment.
  • New Custom Fields: 
    • User Story -> Promote and Deploy
    • User Story -> Promote as Single Step
    • User Story -> Promotion Test Level
    • User Story -> Validate Only.
    • Org Credential -> Default Credential

Server side enhancements

As from 2017-01-17 Copado backend will automatically handle Git conflict resolutions for Profiles, Permission Sets, Custom Objects, Workflows, Custom Labels, Autoresponse Rules, Assignment Rules and Zipped Static Resources that gets unzipped by Copado automatically. This will remove most of if not all unnecessary conflicts caused by the fact that XML and Git don't play nice together. This functionality is available for CCM and CBM.

Server side enhancements

As from 2016-12-05 Copado backend runs on Salesforce apis v38

Version 5.2 - Kanban boards, Promote releases, Deployment Summary and more ...

Key Features:

  • We are introducing Kanban boards that allows users to create a Kanban for any Salesforce standard or custom object (e.g. User Stories, Projects, Opportunity, Cases, etc.) to easily drag and drop records into respective columns to perform field updates (i.e. moving User Stories to different Sprints). More info here.
  • Users now have the ability to define a release that needs to be promoted. When creating a promotion, a user will now be able to select a Release or a Project, when selecting a Release Copado will take all User Stories against that release regardless of the Project and add these to the deployment. More info here.
  • New Email Template for Deployments listing all metadata components and result messages. Read upgrade instructions below.
  • Whilst not part of our package... we are publishing a Release Calendar on our website, where we are now able to expose to our customers our release schedule. Available information will include General Release availability and beta/preview windows.
  • We are introducing a Beta program for the Copado backend API, this means that Users will be able to test new versions of the Copado backend before is General Available. Please contact us to enable this feature on one of your sandboxes.
  • As of this version, Quick Actions can be deployed as any other Metadata components within the Copado Metadata step. The Quick Action step was introduced by Copado to fix a metadata API issue, but this is now resolved. We have therefore removed the Quick Actions step type.

Upgrade instructions

To start using the new Email Template for Deployments, locate and edit the Email Alert named: "Deployment Completed email alert" and change the email template with the new one called:  "Deployment Result Summary"
New Object and fields, make sure OLS, FLS and Tab Visibility are properly set for the following components.
  • New Custom Object: Kanban Board.

Version 5.1 - Copado Selenium Testing

Copado Selenium Testing is a platform that allows non-technical resources to easily create and maintain test cases and run these in the cloud with no infrastructure requirements. Quality Assurance departments will now be fully integrated into the release management cycle and can leverage the Copado Salesforce based platform together with developers and release managers to increase productivity.
Key Features:

  • Copado Selenium recorder - create test cases once & run in all orgs seamlessly.
  • Data driven testing
  • Leverage Copado OAuth - no need to store usernames and passwords in test cases.
  • Support for 900+ browsers including mobile browsers.
  • Copado's Webhook API to trigger tests from anywhere.
  • Introducing Copado scheduler - schedule any job (easy UI included)
  • Reports and Dashboards
  • Maintain Test Script versions - Each org can be assigned a different version.
  • Promote and roll-back test case versions.
  • Environment Variables for parameterized test scripts.
  • Test any web application, Salesforce portal or Salesforce org.

Upgrade instructions

Edit Deployment Flow views as follows
  • It's handy to add the new field "Manage branches" to quickly access CBM functionality"
Edit Environment layout as follows
  • Add related list called "Environment Variables"
New Object and fields, make sure OLS and FLS are properly set for the following components.
  • New Custom Field: Deployment Flow -> Manage branches
  • New Custom Object: Selenium * (all copado objects starting with the Selenium prefix)
  • New Custom Object: Environmental Variables

Server side enhancements

Copado's Git client now supports more nested components on the "Commit files" functionality. As from 19-September-2016, you will be able to commit individual components of the following nested types without committing the entire container file. These correspond to: Workflow, CustomLabels, AssignmetRules and AutoResponseRules parent types.

  • WorkflowRule
  • WorkflowAction
  • WorkflowFieldUpdate
  • WorkflowTask
  • WorkflowAlert
  • WorkflowOutboundMessage
  • WorkflowKnowledgePublish
  • CustomLabel
  • AssignmentRule
  • AutoResponseRule

This is added on top of the already supported nested components from the CustomObject parent type:

  • ActionOverride
  • BusinessProcess
  • CompactLayout
  • CustomField
  • FieldSet
  • HistoryRetentionPolicy
  • ListView
  • RecordType
  • SearchLayouts
  • SharingReason
  • SharingRecalculation
  • ValidationRule
  • WebLink

Version 4.4

Snapshot Differences

  • We have added the file names within the Difference viewer for your convenience.
  • A small bug where the status messages were not displayed has also been fixed.
  • You now have the ability to view the entire file in the Snapshot Difference calculation.

Metadata and Git Metadata steps

  • The Find and Replace labels have been made more user friendly.
  • On the Git Metadata step, the grid selector now includes Select/Unselect All buttons.

Detailed Deployment History

  • To facilitate SOX compliancy reports we have created a full deployment history that tracks the creation, updates and deletion (where applicable) for Deployment, Steps and Destination Orgs.

User Stories

  • Whilst the Has Apex Code picklist was very useful it did not in some cases provide enough flexibility for Approval Process routing. We have therefore created a multi-select picklist where all selected metadata types will be added automatically. We recommend that this is used moving forward for your approval processes and other automations.

Deployment Results

  • After a deployment has completed with errors, users would have had to flick between the Deployment Results tab and the Selected Metadata tab. To improve this process the Deployment Results can now be opened in a new tab/window to allow you to easily flick betwen the metadata step selections and the deployment errors.

Upgrade instructions

New Object and fields, make sure OLS and FLS are properly set for the following components.
  • New Custom Field: User Story -> Metadata Types in Selection
  • New Custom Object: Copado Deployment History
  • New Custom Fields: Copado Deployment History -> All fields
Edit User Story layout and add the following field
  • Metadata Types in Selection
Edit Deployment layout as follows
  • Add the related list called Copado Deployment History
  • Remove the "new" button from that related list called
  • Add the fields Name, Event, Object, Field, Old Value, New Value, User and Date
  • Sort related list by Date Ascending

Version 4.3

  • Apex Test Results Summary email template
  • Now you can email the Apex Test Results Summary page via email, learn how

Version 4.2

  • Introducing Pre/Post CI deployment jobs
  • Introducing Webhook Lookup on the URL Callout step

Upgrade instructions

Edit Continuous Integration layout and add new section called: Pre/Post-Build Automation
  • add Pre Deployment Options
  • add Pre Deployment Jobs
  • add Post Success Deployment Jobs
  • add Failed Deployment Jobs
New Object and fields, make sure OLS and FLS are properly set for the following components.
  • New Custom Field: Continuous Integration -> Pre Deployment Options
  • New Custom Field: Continuous Integration -> Pre Deployment Jobs
  • New Custom Field: Continuous Integration -> Post Success Deployment Jobs
  • New Custom Field: Continuous Integration -> Post Failed Deployment Jobs
  • New Custom Object: AuxiliaryObject

Version 4

  • Introducing Copado Branch Management application
  • Introducing Metadata indexing against User Stories and Overlap awareness functionality

Upgrade instructions

Edit Deployment Flow layout
  • add git repository
  • add main branch
  • add button "manage branches"
Edit Environment layout
  • add Branch Management Permissions related list.
Edit Project layout
  • add Index Metadata
Edit User Story layout
  • add related list: User Story Metadata (including Metadata API Name and Status fields) new button is not necessary.
Schedule job: IndexMetadataJob
  • Go to Setup, Apex Classes, Schedule Apex, choose class IndexMetadataJob, and your desired frequency
New Object and fields, make sure OLS and FLS are properly set for the following components.
  • New Custom Field: Project -> Index_Metadata
  • New Custom Field: Deployment Flow -> Git repository
  • New Custom Field: Deployment Flow -> Main branch
  • New Custom Field: Deployment Flow Step -> branch
  • New Custom Object: Branch Management Permissions

Version 3.11

  • New step type "URL Calloutto integrate with other systems, such as Selenium testing or any other system.
  • Find and Replace within Metadata files before deploying them. This will allow deploying Outbound Messages by replacing the Run as  username with the username of the destination org, replace hardcoded business hours ids within Entitlements Processes, even deactivating or activating Workflow rules is now possible with this new feature. 

  • ul>

    Version 3.10

    • Add existing commits to User Stories
    • Create commits straight from the User Story
    • Partial Snapshot Differences (instead of the full org)
    • Complete a manual task early (instead of waiting for Copado to reach that item so you can update the status).
    • Deploy from git using a starting commit and an ending commit. Copado will select all the files in the commits for you.
    • CI Email results has been improved with full details of errors as well as deployed content.

    Upgrade instructions

    The following changes need to be made in order to upgrade Copado to the latest version. When upgrading to the latest version of Copa do and some versions in between have been skipped, you will need to complete the previous versions' upgrade instructions too.

    FLS = Field Level Security
    OLS = Object Level Security


    Version 3.09 to 3.10

    • User Story Commit object and fields (FLS update)
    • Email Template Name field on the Continuous Integration Permission object (FLS update)
    • Permissions field on the Git Snapshot object (FLS update)
Comments