Glossary of Terms
In this glossary, you will find a definition of all Copado products as well as frequently used terms 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: Copado Permissioner is an application that allows you to have a 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.
- Copado User: User-based license that is designed to help customers to better manage the release management process of requirements from one or multiple sandboxes to production.
- Guest: License that gives you access to manage Change Management records such as user stories, sprints, epics, etc. and functionality such as Kanban Boards, Sprint Wall and Work Manager.
- API Key: An API key is a unique code that is passed into an API to identify the application or user that is making the API request.
- Continuous Integration: A Continuous integration is a trigger that automatically deploys new changes committed in a specific Git branch to a specific Salesforce org.
- Org Credential: An org credential is a connection between a user and a Salesforce environment.
Copado Change Management
- Application: An application is a program that has been designed to create value for a group of customers.
- Back Promotion: A back promotion is a process that allows you to promote user stories from higher environments to lower environments.
- Data Template: A data template is a configuration file that defines a data structure you want to migrate between Salesforce orgs.
- Deployment: A deployment is the process of moving one or multiple changes from one environment to another.
- Deployment Step: A deployment step is an action that will be performed during a deployment.
- Destination Branch: A destination branch is a copy of the content included in the destination environment.
- Environment: An environment is a representation of a Salesforce organization.
- Environment Variables: Environment Variables is a feature that allows you to make commits, deployments, branch validation and Selenium test cases environment agnostic.
- Epic: An epic is a large user story that needs to be split up into smaller user stories prior to its implementation.
- Feature: 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.
- Feature Branch: A feature branch is the branch Copado creates when you commit changes in a user story.
- Git 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.
- Git Snapshot: Git snapshot in Copado is a connection between a Salesforce org and a Git repository/branch.
- Org Difference: An org difference is a comparison between two Salesforce orgs.
- Pipeline: 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.
- Project: A project is a proposed or planned undertaking of changes that are going to be made in Salesforce.
- Promotion: A promotion is a deployment of multiple user stories from one environment to another, following a designated pipeline.
- Promotion Branch: 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.
- Release: 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 Salesforce application experiences after every deployment.
- Snapshot Difference: A Snapshot difference is a comparison between two Salesforce orgs, two Git commits or a Salesforce org and a Git commit.
- Team: A team is a group of people that work together on the same project.
- Theme: A theme is a group of user stories which contribute to a common goal. It is the highest level in the user story hierarchy.
- User Story: 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.
Copado Continuous Delivery
- Connection Behavior: A connection behavior is a template that is used to define the deployment, back-promotion and quality gate behaviors that will be applied throughout your release management process.
- Automation: 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.
- Metadata Item: A metadata item is a representation of a Salesforce metadata type.
- Metadata Group: A metadata group is a collection of metadata items to which you can apply different quality gates.
- Automation Template: A reusable template that contains a set of steps that can be executed in the future.
- Dynamic Variables: Set of predefined variables that can be used in a Salesforce Flow deployment step.
Quality and Compliance
- Compliance Rule: Contains the criteria of a rule that is relevant to an organization, to match when a metadata is out of compliance.
- Compliance Rule Group: Compilation of compliance rules that can be assigned to an environment.
- Compliance Scan: Analysis performed by Copado Compliance Hub to monitor metadata changes in your environments or Git branches.
- Persona: A persona represents a group of users clustered based on shared behavior, motivations, goals, pain points, or other characteristics.
- Pull Request: 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 (org credentials).
- Selenium Test Run: A Selenium test run is the execution of a test suite in an org credential with the given Selenium settings.
- Selenium Test Suite: A Selenium test suite is a collection of test cases.
- Test Script: A test script is a list of predefined steps that you need to follow in order to test the specifications of a system.
- Package: A package is a logical set of metadata that represents a subset of an org.
- Scratch Org: A scratch org is a source-driven and disposable deployment of Salesforce code and metadata.
- Second-Generation Package: Feature that enables system integrators to create packages in a source-driven development environment and distribute them to customers.
- Unlocked Package: Feature that give Salesforce customers a means to organize their metadata into a package and then deploy the metadata (via packages) to different orgs.
- Agile: Agile is a collaborative approach to software development based on incremental and iterative developments.
- Burndown Chart: A burndown chart is a graphical view that compares the current progress of the items in a sprint with the planned progress.
- Kanban: 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.
- 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: Scrum is an Agile methodology used in software development that helps teams work together by means of iterations called sprints.
- Sprint: 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.
- Sprint Wall: A sprint wall is a view that shows you the status of the sprint and a whole picture of its content.