--- title: "Config Search Dashboard Tool" slug: "config-search-dashboard-tool" description: "Streamline your updates with the Config Search Dashboard tool, efficiently locating JSON configuration values across applications and modules." updated: 2026-04-27T18:11:00Z published: 2026-04-27T18:11:00Z canonical: "docs.unqork.io/config-search-dashboard-tool" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Config Search Dashboard Tool The **Config Search Dashboard tool** lets Creators locate specific configuration values in their applications and modules. These values might include the Property ID of a [Panel](/v1/docs/panel-component) component or the Canvas Label Text of a [Decisions](/v1/docs/decisions-component) component. More precisely, the tool searches JSON values. This is useful when updating values shared across multiple applications and modules. Submit a search request and the tool generates a list of all module components containing the specified value. Use this report as a checklist to streamline the update process and avoid manually inspecting each module. ## Accessing the Config Search Tool To access the Config Search Dashboard tool, navigate to your environment, click **Resources**, and select **UDLC Toolkit**: ![A static image displaying the Resources section of the UDesigner to access the UDLC Toolkit.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/UDLC in Resources.png?sv=2026-02-06&spr=https&st=2026-11-04T15%3A52%3A06Z&se=2026-11-04T16%3A52%3A06Z&sr=c&sp=r&sig=ujFAQkmkIVmn450McEHQ5w0xnAOFEaukyKH%2BkwZKbNI%3D) Under the **Build and Test** section of the UDLC Toolkit, locate the **Search Config** tool and click on the **Use this tool** button: ![A static image displaying the Config Search Tool option in the UDLC Toolkit.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Config Search --Use this tool button.png?sv=2026-02-06&spr=https&st=2026-11-04T15%3A52%3A06Z&se=2026-11-04T16%3A52%3A06Z&sr=c&sp=r&sig=ujFAQkmkIVmn450McEHQ5w0xnAOFEaukyKH%2BkwZKbNI%3D) ## Submitting a Config Search Request To initiate a search, select the location to query. The available options include: - **Specific Applications**: Displays the **Applications** drop-down menu, letting you select one or more applications in your environment. - **Specific Modules**: Displays the **Modules** drop-down menu, letting you select one or more modules in your environment. ### Search Scope The Config Search Dashboard tool searches only JSON values associated with components. These values typically represent data entered manually during component configuration. The tool does not support searches for system settings or submission data. Examples of searchable values include: - Property IDs - Labels - Email addresses - values - values - URLs ### Entering Search Values You can enter one or more values in the search field. When entering multiple values, separate them with a line break. Doing so organizes all values into a single, structured list. Here is an example of searching for Label Text values: - First Name - Last Name - Email Address The image below shows you how to format your values: [![A static image displaying the configuration of the Config Search Request tool in the UDLC Toolkit.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Config Search-- Request.png?sv=2026-02-06&spr=https&st=2026-11-04T15%3A52%3A06Z&se=2026-11-04T16%3A52%3A06Z&sr=c&sp=r&sig=ujFAQkmkIVmn450McEHQ5w0xnAOFEaukyKH%2BkwZKbNI%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Config%20Search%2001.jpg?sv=2026-02-06&spr=https&st=2026-11-04T15%3A52%3A06Z&se=2026-11-04T16%3A52%3A06Z&sr=c&sp=r&sig=ujFAQkmkIVmn450McEHQ5w0xnAOFEaukyKH%2BkwZKbNI%3D) After making your selections, click **Submit** and **OK** in the pop-up modal. Another pop-up Modal displays your **Request Number**. Unqork uses this number to track the request internally. ## Viewing Your Config Search Report After submitting a request, you receive an email with an attached spreadsheet called `Config Search {your-environment} {timestamp in UTC}.xlsx`. This spreadsheet is your search report. To view your report: 1. Click the attachment's link in the email. 2. Check your **Downloads** folder for the `.xlsx` file. 3. Open the file in **Microsoft Excel** or **Google Drive**. When you open the spreadsheet, you see three tabs at the bottom of the worksheet: - index - Summary - customSearch Here is an example of a typical Config Search Report: [![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Config_Search_02_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-04T15%3A52%3A06Z&se=2026-11-04T16%3A52%3A06Z&sr=c&sp=r&sig=ujFAQkmkIVmn450McEHQ5w0xnAOFEaukyKH%2BkwZKbNI%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Config%20Search%2002.jpg?sv=2026-02-06&spr=https&st=2026-11-04T15%3A52%3A06Z&se=2026-11-04T16%3A52%3A06Z&sr=c&sp=r&sig=ujFAQkmkIVmn450McEHQ5w0xnAOFEaukyKH%2BkwZKbNI%3D) The following sections describe the information each tab provides. **Index Tab** This tab provides details of the `customSearch` operation the tool runs on your applications and modules. These are the columns you see in this tab: | Attribute | Description | | --- | --- | | Test | The test the tool ran. It'll always be `customSearch`. | | Severity | The test's severity. For the `customSearch` test, the severity is **Informational**. | | Test Description | A brief description of what the test does. | | Action Item | Here you find more search suggestions the test does not return the information you need. Following these suggestions ensures you use the Config Search tool correctly. | | Overview | A general description of the test and its purpose. | | Columns Explanation | The specific operation of the tool and the format you'll see in the **customSearch** tab for the values you searched. > [!TIP] > In the example image above, the test runs a reference (`_REF`) operation. This operation looks for a match between the values you entered and the ones in your environment. The result is either a Boolean of **true** or **false**. | **Summary Tab** The Summary tab displays the number of times the test found a match. The three columns are: - Test - Severity - Results Count **customSearch Tab** This tab displays the most details about your search. Here you see all the applications, modules, and components included in your searched value(s). You see the following columns in this tab: | Attribute | Description | | --- | --- | | Application ID | The unique identifier of the application whose value(s) matched your search. | | Application Name | The unique name of that application. | | Module ID | The unique identifier of the module whose value(s) matched your search. | | Module Name | The unique name of that module. | | Label | The Label Text or Canvas Label Text of the module's component. | | Component | A module's component whose value(s) matched your search. | | _REF | The value you searched. Each value has its own column. If a match exists for that value, a Boolean of **true** displays for each matching application and module. The format you'll see in the column heading is the following: `/{VALUE-SEARCHED}/_REF`. | | Modified time (UTC) | The timestamp of the last change made to the application or module. Time displays in UTC (Coordinated Universal Time). | | Ancestors | The ancestors of the module's component. | Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. A Property ID is the unique field ID used by Unqork to track and link components in your module. Canvas Label Text indicates the purpose of the corresponding field or component. For non-input components, the Canvas Label Text isn't end-user facing, and only appears in the . JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data. The UDLC (Unqork Development Lifecycle) Toolkit is a set of tools designed to manage Unqork applications. A query lets you retrieve, access, manipulate, and delete data in a database. Scope is a tool that limits an application's access to a user's account. An application can request one or more scopes, this information is then presented to the user in the consent screen, and the access token issued to the application will be limited to the scopes granted. Also known as Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections. A Property ID is the unique field ID used by Unqork to track and link components in your module. Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. A modal is a window that appears on top of the content you are currently viewing. A modal is a window that appears on top of the content you are currently viewing. The Number data type accepts integer or floating point values. The number data type does not use quotes around numerical values. The location of an element in an array. The Boolean data type accepts one of two values: true, or, false. In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module. Label Text conveys what the input component is and what information it displays. Enter the purpose of the corresponding component or field. Coordinated Universal Time (UTC) is a standard, globally-accepted timezone used to regulate clocks and time around the world. Coordinated Universal Time (UTC) is a standard, globally-accepted timezone used to regulate clocks and time around the world.