Branch Components Tab

The Components tab shows all metadata that exists in a branch. It serves as the baseline for development and allows you to add, edit, filter, and delete branch components.

When you create a branch from Main or another source branch, the initial set of components forms the baseline. From there, branch components can be added in several ways:

• At the time of branch creation.

• By clicking Add Components.

• Through Pre/Post Destructive Changes.

• By merging a Pull Request.

• Automatically through commits.

Each component in the list includes key details such as:

• Name and Type (e.g., ApexClass, Profile, Dashboard).

• Source Branch where it originated.

• Commit Hash and Author.

• Latest Activity and timestamps.

• Salesforce Updated By user and update date.

Filtering Components

To make it easier to find and manage metadata, you can filter components using multiple options:

• Select Type – choose from 100+ Salesforce metadata types (e.g., ApexClass, ApexPage, Profiles).

• Latest Activity – sort by most recent or oldest activity.

• SF Updated By – filter by Salesforce users or automated processes.

• SF Update Date – use a date picker to narrow down updates by calendar date.

These filters give full visibility into when and how metadata was updated in both Revvy and Salesforce.

Editing and Deleting Components

Every row in the Components tab has a three-dot menu that allows you to:

• Edit – Opens the editor screen. You can manually update the component’s code or XML. Once changes are made, provide a commit message and click Commit to save. The edit will be recorded in branch history.

• Delete – Removes the component from the branch.

You can also click directly on a component name to:

• Open the built-in editor view.

• Review metadata in detail (e.g., Apex class code or XML).

• Make inline changes and commit them.

Best Practices

• Use filters when working with large metadata sets to quickly find the components you need.

• Always provide meaningful commit messages when editing components directly.

• Keep your branch clean by removing unused metadata with destructive changes when necessary.