How It Works
As the page opens the optimized date range is preloaded into the From and To Date and a message showing the optimal days appears. In the screen shot notice 10.63 days.
That message will not change as you change your date selections; it remains as a reminder of a date span for maximum speed in result set and filtering.
The fewer configuration changes in your org the wider this preset range will be initially. It is calculated to return approximately 2,500 audit records.
Click to enlarge
Use the preloaded optimized date-time range or pick new From Date and To Date values.
On a browser the standard calendar view date picker will pop up and selections can be made that way. Or you can overtype date time values directly.
Your selected date range should ideally span the initial optimized days range.
However, if you select a range that is more than 3 times the suggested range you will receive a warning toast message indicating by
how much you have exceeded the range; shown in this screen shot.
You can close the toast message [X] and try the query anyway but with a sizable variance performance will degrade.
Note that using more that 8 times the range may result in less data than your range selection due to a generously set query limit of 20,000 records. The optimal preset days should return approximately 2,500 records. (But do try out whatever you like here and find what works best for your research. Just know that depending on time of day and server capacity you could see slower speeds.)
.jpg)
Click to enlarge
Click the Run Query button and you will see the results of your query.
Note the count of returned records in your header bar. <303 Audit Entries Selected and Filtered>.
Click to enlarge
Filter your results on Display (change description) and/or Created By (the admin user who made the config change). *All filtering is case sensitive.
Enter filter criteria as partial or full string (including spaces) and exit click anywhere outside of the given entry box (in a different text box or any open page space) to fire the search event.
Depending on the size of the query initial result set (as indicated by The header bar count changes with filter options selected: <18 Audit Entries Selected and Filtered>.
In the screen shot Display Filter using a single space before "flow" will eliminate "workflow" per se so will include flows and some process builder changes but not workflow rules.
(Be aware that some process builder entries appear as "workflow" and some appear as only "flow".)
Click to enlarge
Click the File Results button (1). A File will be saved with the queried and filtered data with the date-time stamped file name shown in a toast message (2).
Click to enlarge
Click to enlarge
*Note the additional fields on file are Section to show configuration groupings and Username to ensure unique reference to any admin who performed the configuration change.
.jpg)
Click to enlarge
Click to enlarge
If configured for mobile, per our deployment steps*, you will access the app from your mobile menu options.
* see Setting It Up.
Click to enlarge
Results are returned with the record count same as with browser. However, the output view is noticably different from a PC browser in Lightning Experience. Each record here is wrapped in a Lightning Card component with each field on its own line within a card. (Whereas on the PC you have a table row display for each record.)
This is of course scrollable with swipe up and down touch swipe actions.
*As with most app functional page refresh, touch and hard pull down from this top view point will refresh the view clearing results and setting new date/time.
Click to enlarge
This functions the same way the browser does because it's the same Lightning Component.
This screen shot example shows filtering to find validation rule configurations using the string "valid".
If you need to find some element with that word alone in it (e.g. fields created with the names "valid sum" and "valid entry") you could filter with "valid " to eliminate validation rules. You can use the longer criteria phrases like "validation rule" to narrow the results to validation rules only when you need to exclude finding the two fields in the first case.
Of course the functionality is identical with desktop Lightning Experience.
