The Config Search Dashboard searches JSON configuration values across applications and modules. Use this tool to generate a report of every component containing a specific value, like a Property ID or label text. Creators can then update those components without manually inspecting each module.
Submitting a Search Request
To begin a search, select the scope and enter search values.
Search Scope
Choose where the tool searches:
- Specific Applications: Displays the Applications drop-down for selecting one or more applications.
- Specific Modules: Displays the Modules drop-down for selecting one or more modules.
The tool searches only JSON values associated with component configuration: values entered manually during setup. It does not search system settings or .
Searchable value types include Property IDs, labels, email addresses, input and output values, and URLs.
Entering Search Values
Enter one or more values in the search field. To search for multiple values, separate each with a line break. The tool treats each line as a separate search term.
After entering values, click Submit, then OK in the confirmation dialog. A second dialog displays a Request Number for internal tracking.
Viewing the Search Report
After submitting, an email arrives with an attached spreadsheet named Config Search {your-environment} {timestamp in UTC}.xlsx.
To open the report:
- Click the attachment link in the email, or check the Downloads folder for the
.xlsxfile. - Open the file in Microsoft Excel or Google Sheets.
The report contains three tabs:
Index Tab
Provides details of the customSearch operation the tool ran on applications and modules.
| Column | Description |
|---|---|
| Test | The test the tool ran. Always displays as customSearch. |
| Severity | The test severity. For customSearch, this is Informational. |
| Test Description | A brief description of what the test does. |
| Action Item | Additional search suggestions if the test does not return the expected results. |
| Overview | A general description of the test and its purpose. |
| Columns Explanation | A description of the operation and the format used in the customSearch tab. For example, a reference (_REF) operation looks for a match between the search values and the values in the environment, returning a Boolean of true or false. |
Summary Tab
Displays the number of times the tool found a match.
| Column | Description |
|---|---|
| Test | The test name. |
| Severity | The test severity. |
| Results Count | The number of matching components found. |
customSearch Tab
Displays the most detail about the search: every application, module, and component where a match was found.
| Column | Description |
|---|---|
| Application ID | The unique identifier of the matching application. |
| Application Name | The name of the matching application. |
| Module ID | The unique identifier of the matching module. |
| Module Name | The name of the matching module. |
| Label | The Label Text or Canvas Label Text of the matching component. |
| Component | The component whose value matched the search. |
| _REF | One column per search value, in the format /{VALUE-SEARCHED}/_REF. Displays true for each application and module where a match exists. |
| Modified Time (UTC) | The timestamp of the last change to the application or module, in UTC. |
| Ancestors | The ancestors of the matching component. |
Changelog
| Date | Change |
|---|---|
| 2026-07-16 | Editorial pass: fixed banned words, em dashes, See Also descriptions, and link paths. |
| 2026-04-28 | Updated to Reference Guide format. Fixed metadata and headings. Removed navigation screenshots. Restructured report tabs as named sections. Updated alt text. |