Glossary

This glossary provides definitions of common terms and features in Revvy, serving as a quick reference for users.

Activities

Central log of all actions across branches and pipelines. Use filters by type, status, or date to find jobs and drill into results.

Add Components

Brings metadata from a connection into a branch. Select a connection, pick items, enter a commit message, and run. Creates “Commit to Branch” and “Search Conflicts” jobs in Activities.

Applications (Security)

Manage application credentials and keys. View details, edit, or revoke as needed in Global Console.

Auto Retrieval

Metadata retrieval runs automatically on a schedule (about every 15 minutes). Manual retrieval is also available, with all runs logged in Activities.

Branch Components

The Components tab lists metadata in the branch: type, name, updated by/date, commit hash. Filter by type, activity, or Salesforce updated by/date. Add via Add Components, PR merges, or destructive sets. Edit or delete via ⋮ menu or by opening a component.

Code Coverage Settings (Connections)

Set required test coverage thresholds for validations and deployments. Helps enforce quality per org.

Code Tab

Workspace hub for branches. Lists All, Yours, Active, and Stale branches with search and sorting. Each card shows ahead/behind, PR tags, and last activity.

Commits Tab (Branch)

History of commits in a branch, with message, author, timestamp, and commit hash. Useful for auditing and reviews.

Components Changed (Pull Request)

Lists changed metadata in a PR. Open items to view diffs. Reviewers can Approve or Request Changes here.

Connections (DevOps)

Authenticated Salesforce orgs shown inside the DevOps app. If missing, set up in Global Console first. Used for retrieving metadata, validating, deploying, and pipelines.

Connections (Global)

Org authentications configured in Global Settings. These flow into the DevOps app once valid.

Delete Branch

From the branch header ⋮ menu, select Delete. Removes the branch and its components (permissions required).

Deploy (Branch)

Runs a deployment with selected components. Options include test levels, destructive changes, and selective profile/permission set deployment. Logs show backup, manifests, deployed items, and job ID.

Feature Branch

Isolated workspace for changes, created from a source branch (main or release). Used for committing, validating, and preparing features.

Global Settings

Admin console for tenant-level setup. Manage users, groups, roles, licenses, security, and connections. The DevOps app relies on this.

Groups

Collections of users that inherit a Role. Update the group’s Role to update permissions for all its users.

Help & Support

Accessed from the “?” icon. Includes product docs, in-app chat, and ticket support with searchable history.

Identity Providers (SSO)

Configure SSO (OIDC or SAML) in Global Settings. Appears with client ID details and can be edited or removed.

Jobs

Execution records for actions like Validate, Deploy, Rollback, or pipeline steps. Each job has timestamps, duration, actor, and logs.

Job Statuses

• Queued — scheduled but not running yet.

• In Progress — currently running.

• Completed — finished successfully.

• Aborted — stopped manually.

• Exception — failed with an error (check logs).

• Action Required — paused for manual approval in a pipeline.

Jira Integration (Settings)

Add Jira in Settings to link user stories with branches. Integrated stories appear in the Related Stories tab. Can view projects or delete via the recycle icon.

Latest Activity (Sorting)

Sort by A–Z, Z–A, Latest (most recently updated first), or Oldest. Available in PRs and branches.

Licenses

Controls how many users can access DevOps. Assigned automatically when users are created (default: System Administrator).

License Types

• Full Access — retrieve, manage code, pipelines, deploy.

• Read Access — view-only, no changes.

Light/Dark Mode

Theme toggle for the UI—no feature difference.

Logs

Detailed output of actions. Access from Activities → Jobs or “See logs” buttons.

Main Branch (Baseline)

The stable source of truth, synced with Production. Features are branched off here.

MFA Devices (Security)

Manage multi-factor authentication for tenant users (e.g., TOTP apps). Configured in Global Console.

Overwrite Protection

Prevents overwriting newer org metadata. Compares branch vs org, categorizes items as New, Same, or Different. Resolve conflicts with side-by-side diff and commit.

Pipeline Execution (Automatic)

Triggered by events such as PR merges. Runs pipeline automatically, with results in Activities.

Pipeline Execution (Manual)

Run pipeline from UI, select branch + pipeline, and execute. Logs appear in Activities and pipeline detail.

Pipeline Operation: Deploy

Applies metadata changes to a target org.

Pipeline Operation: Validate

Simulates a deployment without applying changes; checks compatibility and runs tests.

Pipeline Operation: Rollback

Reverts changes using the backup from a prior deployment.

Pipeline Operation: Webhook

Sends an HTTP callback to an external system during the pipeline.

Pipeline Operation: Manual Step

Pauses the pipeline for human approval or action.

Pipeline Operation: CodeScan

Runs static code analysis checks as a pipeline gate.

Pipeline Operation: Execute Apex

Executes Apex code or tests in the target org.

Pipeline Overview

Visual workflow from Start → Stop. Add steps with Name, Operation, Target Org, Test Options, and conditions (On Pass/On Fail).

Pipeline Step Editing

Click a pipeline step to edit org, test level, or pass/fail flow.

Pipelines (List)

Create, view, and run pipelines. Each shows name, branch, org count, creator, and activity. ⋮ menu allows edit or delete.

Pre-Deploy Fix

Check for missing dependencies before deploying. Options: Retrieve missing components into branch, or Remove unused references. Logs jobs into Activities.

Pre/Post Destructive Changes

Define items to be deleted during deployment. Added from Components tab (pre or post timing). Included automatically in deploy/validate.

PR Actions

Available in pull requests: Create, Edit, Approve, Request Changes, Merge, Close.

PR Conflicts

Shown as a banner when branch changes conflict with target branch. Merge is disabled until conflicts are resolved.

Pull Request Overview

Displays status, target/source branches, author, created/updated dates, and description. Panels for reviewers and activity. Merge enabled only when conflicts are resolved.

Pull Requests (List)

Central view of all PRs. Filters: Search, Authors, Status, Reviewers, Date Range, and Latest Activity. Columns: ID, Title, Path, Status, Author, Reviewers, Activity, Actions.

Quick Actions (⋮ in Branch)

Menu on branch header. Includes Create Pull Request, Run Pipeline, Validate, Deploy, Pre-Deploy Fix, Overwrite Protection, Rollback, Delete Branch, etc.

Release Branch

Integration branch to combine feature work, run validations, and promote downstream.

Related Stories (Jira)

Shows Jira stories linked to a branch. Add at creation or later. A branch can link to multiple stories, and stories can be unlinked.

Retrieve

Pull metadata from Salesforce into a branch. Runs logged in Activities. Can also happen automatically or via Pre-Deploy Fix.

Define access permissions. Configure license type, permissions (e.g., PR view/manage), and org-level rights (Retrieve/Validate/Deploy).

Rollback (Branch)

Restore a Salesforce org to its pre-deployment state using an automatic backup created at deploy time. Available in branch actions and pipelines.

Security – Network Access

Restrict org access by IP range.

Source Branch (New Branch)

The branch a new branch is created from (main, release, feature).

Three-Dot Menu (⋮)

Standard UI menu for contextual actions (Edit, Delete, Run, Deploy, etc.).

User

Created in Global Console. Belong to groups and inherit Roles. Can be deleted when no longer needed.

Validate (Branch)

Simulates a deployment against a target org without applying changes. Runs test levels (default, no tests, run local, run all, or specific tests). Logs results in Activities.

Webhooks (Pipeline Operation)

Pipeline step that sends events to external systems.