Salesforce Certified Advanced Administrator Exam: Examining Configuration Changes

How Administrators Examine Configuration Changes

Question

SIMULATION - Describe how administrators can examine what configuration changes have been made:

Explanations

See the solution below.

1

Through the audit trail (at Setup | Security Controls)

2

It will show the 20 most; recent setup changes, you can download a complete history for the last 180 days 3

There are over three dozen items tracked (see "Monitoring Setup Changes" in help) 4

Alternatively, you might use Dream factory's Snapshot or other Metadata API-based tools.

As a Salesforce Administrator, you can examine what configuration changes have been made using the following methods:

  1. Setup Audit Trail: Setup Audit Trail provides a complete history of changes made to your organization's settings and configurations. You can use this tool to see who made changes, when they made them, and what changes they made. To access the Setup Audit Trail, go to Setup > Audit Trail. From there, you can view a list of all changes made to your organization in the last six months. You can also download the audit trail as a CSV file.

  2. Field History Tracking: Field history tracking allows you to track changes made to specific fields on standard and custom objects. You can use this tool to see when a field was changed, who made the change, and what the old and new values were. To enable field history tracking, go to the object you want to track, and then click the "Set History Tracking" button. From there, you can select which fields you want to track.

  3. Change Sets: Change sets allow you to move customizations from one Salesforce organization to another. When you create a change set, you can see a list of all the components that are included in the set. This allows you to examine what changes have been made before you deploy them to another organization.

  4. Apex Debug Logs: If you have developers working in your Salesforce organization, they may be making changes using Apex code. You can use Apex debug logs to see what changes they are making. To enable debug logging, go to Setup > Logs > Debug Logs. From there, you can create a new debug log and specify which users or Apex classes you want to monitor.

By using these methods, you can keep track of changes made to your Salesforce organization and ensure that any changes are documented and approved before they are implemented.