Glossary of Terms
This glossary provides you with a definition of all Copado products and terms, grouped by categories, that are frequently used in our documentation.
Copado Branch Management
Feature-based license that enables a connection between two orgs in a pipeline in order for Copado to create feature branches and execute Git-based promotions between the orgs.
Copado Compliance Hub
User-based license that allows you to monitor and enforce compliance rules on your business for all metadata changes made within your environments.
Copado Data Deploy
User-based license that allows you to configure a data set deployment by using point-and-click data templates.
Copado Permissioner is an application that allows you to have better control of permission set assignments to users.
Copado Selenium Testing
User license that allows you to record, store, run and schedule Selenium tests within Copado.
User-based license that is designed to help you better manage the release management process of requirements from one or multiple sandboxes to production.
License that gives you access to manage planning records such as user stories, sprints, epics, etc., and functionality such as Kanban Boards, Sprint Wall, and Work Manager.
An API key is a unique code passed into an API to identify the application or user making the API request.
A test code written mostly in two formats–class and trigger.
An application is a program that has been designed to create value for a group of customers.
A back promotion is a process that allows you to promote user stories from higher environments to lower environments.
A credential is a connection between a user and an environment.
A template used to define the promotion, back-promotion behaviors, automations, and quality gates that are applied throughout your DevOps process.
A testing metric that helps you determine the quality of the code that you want to test.
Deployment is a process of moving one or multiple changes from one environment to another.
A deployment step is an action that is performed during a deployment.
A destination branch is a copy of the content included in the destination environment.
An environment in Copado is a representation of a Salesforce organization or instance of an application in other clouds such as Heroku or MuleSoft.
Environment Variables is a feature that allows you to make commits, deployments, branch validation and Selenium test cases environment agnostic.
An epic is a large user story that needs to be split up into smaller user stories prior to its implementation.
A feature is an Agile and scrum element that can be described as a large piece of work that delivers some type of business value.
A feature branch is an auxiliary branch that Copado creates when you commit changes to a user story.
A text file that tells Git about the files and folders that should be ignored from the repository.
A Git repository is a storage location where the versions of your files are stored. This may be a hosted location or your own Git server.
A Git snapshot in Copado is a connection between a Salesforce org and a Git repository/branch.
Elements of the metadata grid in the Classic Copado User Story commit page (in the Multi-Cloud US commit page, the metadata components are called "files").
An org difference is a comparison between two Salesforce orgs.
A project is a proposed or planned undertaking of changes that are going to be made in Salesforce.
A promotion is a container used to deploy one or multiple user stories from one environment to another following a designated pipeline.
A promotion branch is a branch created by Copado’s backend that combines the content in the feature branch with the content in the destination environment.
A release is a feature that allows you to group user stories to promote them together as well as to keep track of the version of changes that your application experiences after every deployment.
A field on the Environment Variable wizard that specifies where a particular variable will be applied.
A Salesforce org that carries all your changes to be promoted to the next environment. For example, if you want to promote your changes from Dev1 to UAT, Dev1 will be your source environment.
A snapshot difference is a comparison between two Salesforce orgs, two Git commits or a Salesforce org and a Git commit.
A trail of value elements containing different Ids, variables and characters.
A team is a group of people that work together on the same project.
A theme is a group of user stories that contribute to a common goal. It is the highest level in the user story hierarchy.
A user story is an element used in Agile software development that contains a short, simple and complete description of a task that needs to be completed by a user.
A data-oriented language that is used to create a configuration and provide a human-readable file format.
Copado Continuous Delivery
An automation is a set of tests or flows that will run as part of a continuous delivery process to ensure quality by identifying failures prior to deploying.
A connection behavior is a template that is used to define the promotion and back-promotion behaviors, and automations and quality gates that will be applied throughout your DevOps process.
A metadata item is a representation of a Salesforce metadata type.
A metadata group is a collection of metadata items to which you can apply different automations or quality gates.
A pipeline is a unidirectional flow that defines the order in which changes will be migrated, starting with the development orgs and finishing in a production org.
Copado Data Deploy
A data set is a container that stores, in CSV files, a snapshot of the data included in a particular environment for use in the future.
A data template is a configuration file that defines a data structure you want to migrate between Salesforce orgs.
Reusable template that contains a set of steps that can be executed in the future.
Set of predefined variables that can be used in a Salesforce Flow deployment step.
A function is a script that contains a series of commands and can be executed from Copado.
A system property is a value that is stored in Copado and can be referenced in a function.
Quality and Compliance
A compliance rule contains the criteria relevant to an organization that Copado's scanner uses to query and analyze your org's metadata and match when a metadata item is out of compliance.
Compliance Rule Group
Compilation of compliance rules that can be assigned to an environment.
Copado Compliance Hub’s analysis performed to monitor metadata changes in your environments or Git branches.
A persona represents a group of users clustered based on shared behavior, motivations, goals, pain points, or other characteristics.
A pull request is a mechanism that allows you to let your team know about the changes you have pushed to a branch in a repository so that you all can discuss them.
Selenium Test Case
A Selenium test case is a set of conditions or actions that are performed to verify the expected functionality of an app.
Selenium Test Group
A Selenium test group is a group of test suites to be executed in parallel in one or more environments, as one or more users (credentials).
Selenium Test Run
A Selenium test run is the execution of a test suite in a credential with the given Selenium settings.
Selenium Test Suite
A Selenium test suite is a collection of test cases.
A test script is a list of predefined steps that you need to follow to test the specifications of a system.
Agile is a collaborative approach to software development based on incremental and iterative developments.
A burndown chart is a graphical view that compares the current progress of the items in a sprint with the planned progress.
Kanban is an Agile framework based on a JIT (Just-In-Time) approach and incremental improvements, where all the work is organized on a Kanban board.
A Kanban board is a tool that helps you visualize Salesforce records distributed among different columns as well as filter them to fit your needs.
Scrum is an Agile methodology used in software development that helps teams work together using iterations called sprints.
A sprint (or iteration) is a time-boxed period during which a team needs to complete a certain amount of work. The duration of the sprint is set in advance and usually ranges from one week to a month, a two-week period being the most common.
A sprint wall is a view that shows you the status of the sprint and a whole picture of its content.