Implementing Copado

Updated 2 weeks ago by Copado Solutions

Getting ready to implement Copado? This article lists several items that you need to take care of when rolling out Copado in your organization.

  • Get Salesforce licenses for the users that will work with Copado. Check out the article What Salesforce Licenses or Permissions Do I Need to Start Using Copado? for more information.
  • Install and set up Copado by following the steps provided in the article Copado Base Setup.
    • Add the users to the Copado Deployer package in Setup > Installed Packages.
    • Assign Copado licenses to users in App Launcher > All Items > Copado License Manager.
  • If you have IP restrictions in your Salesforce org, you may need to whitelist Copado's static IP addresses in Setup > Security > Network Access.
  • Define your release process with the steps you would like to work with starting when stories are created and defined, until they are released.
    • Get a graphical overview of the steps.
    • Decide if admins and developers should submit their user stories for approval.
    • Define which Copado quality gates you will enforce at the beginning. Quality gates include Running Apex Tests, Static Code Analysis, Pull Request Reviews, Compliance Scans, Selenium Testing.
    • If your process includes review quality gates (e.g. business testing, peer review, documentation review) consider creating custom fields, validation rules and process builder flows to enforce those quality gates.
    • Consider modifying the main layouts developers will be working with (e.g. user story, project, epic, sprint) and add or remove fields if required. Having a defined process will help you focus on what to modify.
  • If you want to provide your developers with a more restrictive access to Copado, create a permission set that grants Copado access to the users that will work with Copado.
    • The Copado package provides a Copado User permission set with access to all Copado functionality. You can clone this permission set and customize it for other types of users (e.g. developers, QA, scrum master).
    • Please bear in mind that the license type will already restrict Copado Change Management users (no deployments to production, unable to create org differences, unable to create and execute snapshots, unable to create compliance rules, unable to create Selenium tests).
  • Organize training sessions for your users to see and practice what they need to do in Copado.
  • Create internal documentation with the list of steps that users need to follow in order to accomplish the most frequents tasks (how to commit, how to fix a bug, special commit cases). Share this document with all users so that they can access it any time. Developer and admin tasks usually include the following:
    • Creating an org credential for Copado as well as for the orgs from where they will need to commit and to which they will deploy.
      • Each user must create an org credential for the org where Copado is installed first. Otherwise, the user will not be able to use Copado properly.
    • Selecting or committing metadata components to a user story.
    • Validating the user story deployment.
    • Deploying a user story or submitting it for approval.
As each implementation of Copado is dependent on individual client requirements, a Copado expert can guide you and your team with a tailored implementation and best practices on release management for Salesforce. For more information contact your customer success manager.


How did we do?