Glossary

This table contains Prodly terms and their definitions. The terms are initially sorted alphabetically. Click any heading to sort the table by that column.

TermDefinitionProductCategory
Agile developmentAgile development is an iterative process of plan, develop, and deploy used to rapidly respond to ever-changing client needs while ensuring accurate prototyping through the collaboration of all internal stakeholders.AllGeneral
Baseline resultsBaseline results are an initial snapshot of values (results) for the specified object fields, stored in the test case. AppOps Test compares the stored values to the values in future test runs.TestTest cases
BranchA branch is a container within a VCS repository that holds a copy of your data so you can edit that data without altering the original data.ReleaseVersion control
Centrally-controlled deploymentCentrally-controlled deployment allows you to install AppOps Release once in a central Salesforce org and control all deployments from there. Establish connections to all of your orgs and deploy between them, with any org being a source or destination based on your need at the time.ReleaseOrg-to-org deployment
Change managementWithin a computer system, change management is the controlled identification and implementation of required changes. In the context of AppOps Release, change management is the systematic process of determining, approving, testing, and implementing changes to the configuration data in your Salesforce orgs.ReleaseGeneral
Configuration dataConfiguration data for low-code apps is the reference data and metadata you create during app configuration to define your system.AllGeneral
ConnectionEach Prodly AppOps connection is a bridge between the Prodly AppOps service and your Salesforce control, schema, source, and destination orgs, which gives the service limited access to your orgs. Prodly uses industry-standard refresh OAuth (for authorized access) and JWT OAuth (for preauthorized access) to eliminate the possibility of exposing your login credentials.ReleaseOrg-to-org deployment
Control orgYour control org is the org where you install the Prodly AppOps managed package. For org-to-org deployments, it is where you build your data sets, store your data sets, execute deployments, and manage user security parameters. The control org is the key to AppOps Release’s centrally-controlled deployment architecture. For version-controlled deployments, it is where your source of truth data resides and where you maintain managed orgs via the management board.ReleaseOrg-to-org deployment
Data setA data set is a reusable set of reference data deployment instructions AppOps Release uses to determine which objects, records, and fields to copy during deployment. A data set identifies the structure of the data AppOps Release deploys, not the data in the structure.ReleaseOrg-to-org deployment
Data set elementA data set element is a portion of your data set containing deployment instructions specific to a single Salesforce object. Each data set element identifies a deployment object, element details, object fields, field properties, parent relationships, and child relationships.ReleaseOrg-to-org deployment
Data set element chainEach data set consists of a data set element for each deployment object in the data set, organized as a data set element chain. The chain defines the direction AppOps Release traverses your data during deployment.ReleaseOrg-to-org deployment
Data set relationshipA data set relationship is a parent-child relationship between two data set elements.ReleaseOrg-to-org deployment
DeployOrg-to-org deployment means to update data in a destination org with data from a source org directly, not including handling deletes, using a deployment plan or data sets. Data does not pass through or automatically get captured by the VCS, but you can manually capture snapshots of the data for versioning or backup. Version-control deployment means to update data in a Salesforce org with data from the VCS branch associated with the org, including handling deletes, without the need for a deployment plan or data sets.ReleaseGeneral 
Deployment objectA deployment object specifies the Salesforce object to use as the basis of a data set element.ReleaseOrg-to-org deployment
Deployment planA deployment plan is a reusable set of instructions that group data sets and define the order in which to deploy them.ReleaseOrg-to-org deployment
Deployment templatesDeployment templates are JSON-formatted files that contain the deployment plan and data set information AppOps Release needs to recreate the deployment plans and data sets.ReleaseOrg-to-org deployment
Destination orgA destination org is an org that receives the source data during deployment.ReleaseOrg-to-org deployment
Destination schema orgA destination schema org is an org containing the schema the data set editor uses as the basis for controlling data deployment in the destination org.ReleaseOrg-to-org deployment
Element detailsElement details are data set element settings that control various aspects of deployment of the Salesforce object.ReleaseOrg-to-org deployment
Field propertiesField properties are data set element options for adjusting destination fields during deployment.ReleaseOrg-to-org deployment
FunctionFunction specifies the type of functional test to run. For example, Calculate uses the Salesforce CPQ Calculate API to retrieve baseline values from the object fields specified in the test template.TestTest cases
Low-code appLow-code apps store much of their configuration setup in data records, called reference data, in the app’s objects, rather than as code or metadata.AllGeneral
Managed orgA managed org is a Salesforce org you place on the AppOps Release management board to control data deployment. For orgs you also place under version control, Prodly creates an associated VCS repository branch.ReleaseGeneral
MergeMerge means to integrate changes made in a branch into its parent branch.ReleaseVersion-control deployment
MetadataMetadata is a type of configuration data you create during app configuration that influences information architecture and look and feel of your environment.AllSalesforce
Object fieldsObject fields are the individual fields in the data set element’s Salesforce object. AppOps Release functionality allows for inclusion of all fields or individual fields you select.ReleaseOrg-to-org deployment
OrgAn org is any production, developer, sandbox, or scratch environment within a Salesforce customer account.AllSalesforce
Org-to-org deploymentOrg-to-org deployment means to update data in a destination org with data from a source org directly, not including handling deletes, using a deployment plan or data sets. Data does not pass through or automatically get captured by the VCS, but you can manually capture snapshots of the data for versioning or backup.ReleaseOrg-to-org deployment
Prodly AppOps managed packageThe Prodly AppOps managed package is the software you install in your Salesforce org that provides the user interface to the Prodly AppOps products.AllGeneral
Prodly AppOps serviceThe Prodly AppOps service is the backend portion of Prodly AppOps platform that runs on a server in the Prodly cloud and performs the data deployment.AllGeneral
Reference dataReference data is a type of configuration data you create during app configuration that is stored as record data within the app’s objects.ReleaseOrg-to-org deployment
Record matching methodThe record matching method tracks and determines what AppOps Release does during deployment when source records already exist in the destination org. ReleaseOrg-to-org deployment 
Regression testingRegression testing is a testing practice that ensures an app still functions as expected after any changes, updates, or improvements to the reference data, code, or environment.TestTest runs
RepositoryA repository consists of a master store of data (master branch) and other branches you use for feature development and testing. The master branch contains the data for all objects you place under version control.ReleaseVersion control
Roll backIn the context of version control, roll back means to revert changes to a previous version.ReleaseVersion control
Root elementA root element is a special instance of a data set element and the first element in a data set. The Salesforce object you choose as the deployment object in the root element becomes the starting point from which all other objects and fields to copy stems. Each data set contains exactly one root element.ReleaseOrg-to-org deployment
Save to branchIn the context of version control, save means to replace data in a VCS branch with data from the Salesforce org associated with the branch, including handling deletes.ReleaseVersion control
SchemaA schema is set of related objects in an org. The complete structure of the database. Just the structure, not the data in the structure. A schema defines the relationships between objects in an org or app.ReleaseOrg-to-org deployment
Schema orgA schema org is an org containing the schema the data set editor uses as the basis for building data sets in the control org. All objects in a data set must also exist in the source and destination org schemas.ReleaseOrg-to-org deployment
Source dataSource data is records in an org’s objects that Prodly AppOps Release uses as the data to copy during deployment.ReleaseOrg-to-org deployment
Source orgA source org is an org containing the source data to deploy.ReleaseOrg-to-org deployment
Test caseA test case specifies parameters for evaluating the accuracy of a particular feature during future test runs. Each test case consists of a test template (which specifies the objects and fields to test), the functionality to test, the ID of the Quote record to test, and baseline results (created on Save).TestTest cases
Test runA test run specifies a set of test cases and includes the results of running the test cases, indicating whether actual results differ from expected results.TestTest runs
Test run resultsTest run results provide a snapshot of values (results) for all test cases in the test run at the time you executed the test run. AppOps Test compares the values in the test run results to the values in the baseline results.TestTest runs
Test templateA test template specifies a list of fields (from one or more objects) for future use by test cases. You can use a template as the basis for multiple test cases.TestTest templates
Upsert methodSee record matching method.ReleaseOrg-to-org deployment
Version controlVersion control or revision control is the process of capturing snapshots of your configuration data at various moments in time, allowing you to track, record, and revert changes.ReleaseVersion control
Version-control deploymentVersion-control deployment means to update data in a Salesforce org with data from the VCS branch associated with the org, including handling deletes, without the need for a deployment plan or data sets.ReleaseVersion-control deployment
Version control systemA version control or revision control system is software you use to keep track of changes you make to your data and allows you to revert changes to a previous known state.ReleaseVersion control