Introduction
Gearset's automated change monitoring feature gives you a detailed audit trail of metadata CPQ and RCA configuration changes to your Salesforce orgs - on a daily basis. It works by comparing daily snapshots of your org's metadata CPQ and RCA configuration and highlighting any new, changed, or deleted items per run. You can also run the monitoring job on-demand to check for the latest state of your org at any time.
Configuring your change monitoring job with CPQ and RCA configuration
Navigate to the Monitoring page, found under
Automationin the nav menu on the left.Click
ADD NEW JOB...From the
General settings tab, specify the time you want the job to run, the org that you wish to monitor changes for, and give the job a friendly name for easy identification.From the
Notification settingstab, specify how you'd like to be notified about the results of the change monitoring check (e.g. Slack, MS Teams, Email or SMS).From the
Metadata filtertab (see below), choose the metadata, CPQ or RCA configuration you want the monitoring job to detect changes for. This can also include Advanced Approvals and Billing.Note: Any related Salesforce metadata upon which your CPQ or RCA configuration also has a dependency should also be included. These would typically include, though not be limited to,
Custom object,Global value set,Profiles, andGlobal picklist. It is also important to consider anyApexorAutomation(Flows, etc.) that interacts with your CPQ/RCA data.You need to also include the
SBQQmanaged package(s). If you have Advanced Approvals and/or Billing, you'll also need to include thesbaaandblngmanaged packages.
Change monitoring snapshots
When you first create the job, it will have the status Pending. The job will start taking the first snapshot immediately. Once this is completed, the status will update to Initial snapshot taken (requires page refresh once completed to see latest status). The second snapshot will be run at the time specified when the job was configured.
When two snapshots have been taken, you will be able to view the history of detected changes, the exact type of changes to items and, depending on the type of change, perform a rollback of changed items, and deploy detected changes to a different org. This is particularly helpful to prevent drift from occurring between your environments.
Change monitoring history and viewing changes
To view the daily history of your change monitoring job, visit the monitoring dashboard, and select View history for the job you created.
You'll see a complete audit history of the outcome of each change monitoring job run and a top level summary of the detected changes to your metadata, CPQ or RCA configuration.
To view the specific details of a job run, click on the View comparison button. The comparison result will show you the exact differences detected in your CPQ and RCA configuration compared to the previous day.
Use the buttons Previous comparison and Next comparison in the top right corner to navigate between comparisons.
Deploying detected changes to other orgs and rolling back changes
From the history of the job run, expanding the row for a particular entry will give you several follow-up actions such as deploying those same changes to another target, or rolling back changed items detected. At this time, rolling back any new CPQ or RCA items is not supported - only changes to existing CPQ or RCA configuration that was made.
