--- title: "Dynamic Tag Values" slug: "dynamic-tag-values" updated: 2026-10-23T21:32:18Z published: 2026-10-23T21:32:18Z canonical: "documentation.decisions.com/dynamic-tag-values" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt > Use this file to discover all available pages before exploring further. # Dynamic Tag Values Dynamic tag values allow you to populate tag values automatically based on window data such as titles, URLs, or extracted identifiers. This removes the need for predefined or hard-coded tags and enables more accurate, real-time visualization of how users interact with documents and applications. This capability is especially useful for customers who work extensively with documents such as Excel, Word, or PDFs, where file names frequently change. Dynamic tags ensure that document names appear exactly as users see them, across dashboards and views. Dynamic tag values work consistently across **Process View**, **Business Apps**, and **Data Transfer** views, and apply to all document types and application screens. --- ### **How Dynamic Tag Values Work** Dynamic tags use variable syntax (`${...}`) to reference runtime data collected from application windows. ### **Example Configuration** ```json {  "key": "content-category",  "value": "${title}" } ``` With this configuration, a window titled: ```plaintext Purchase Orders 07/25.xlsx ``` Produces the following tag value: ```json {  "key": "content-category",  "value": "Purchase Orders 07/25.xlsx" } ``` --- ### **Supported Dynamic Variables** Dynamic tag values support the following variables: - `${title}` - `${title_lower}` - `${active_process_name}` - `${url}` - `${extract_identifiers.<identifier_name>}` These variables resolve automatically based on the captured window event. --- ### **How to Configure Dynamic Tag Values** ### **Step 1: Add or Edit an Application Rule** Add an application (for example, **Microsoft Excel**). 1. Go to `Admin Panel -> Configure Data Collection` . 2. From the top menu, click **View Application Catalog**. The **Application** list displays. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-JFNSW4A7.png) 3. In the **Microsoft Excel** row, click **Add Application**. The app is listed. 4. Click **Rules & tests** for the added app. 5. Go to the bottom of the page to see the default rules: ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-2PVUNSZR.png) 6. Click the **plus (+)** icon for the default rule **Rule 1**. 7. Click the **Code** tab. The JSON code displays. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-6KX9Z1J0.png) --- ### **Step 2: Add a Dynamic Tag** Locate the existing `tags` list: ```json "tags": [  { "key": "appname", "value": "Microsoft Excel" } ] ``` Add a new dynamic tag, for example: ```json [  { "key": "appname", "value": "Microsoft Excel" },  { "key": "content-category", "value": "${title}" } ] ``` ✅ **Result:** All window titles are captured dynamically and displayed as window names across dashboards and views. --- ### **Capturing Only Part of a Title or URL** Dynamic tags can also capture **specific parts** of a window title or URL using **regular expressions** and **extracted identifiers**. --- ### **Example 1: Capture Only a GitHub Pull Request Number** **Typical window title:** ```plaintext Fix bug process data fetching bug by jannekavander-workfellow · Pull Request #160 · ProcessMaker/sluice ``` **Goal:** Capture only `Pull Request #160`. **Step 1: Create an Extracted Identifier** ```json "extract_identifiers": [  {    "id": "d0d501ed-1da2-457e-84bd-b08d5627a020",    "identifier_name": "github_pr_number",    "regex_pattern": "(Pull\\s+Request\\s*#\\d+)",    "from_fields": ["title"]  } ] ``` **Notes:** - Generate a random UUID4 for the `id`. - Use underscores in `identifier_name`. - Choose the correct `from_fields` value (`title` or `url`). --- **Step 2: Reference the Identifier in Tags** ```json [  { "key": "appname", "value": "Github" },  {    "key": "content-category",    "value": "${extract_identifiers.github_pr_number}"  } ] ``` ✅ **Result:** The window name displays only the Pull Request number. --- ### **Example 2: Capture Only the Path from Jira URLs** **Typical Jira URLs:** ```plaintext https://processmaker.atlassian.net/browse/FOUR-16248 https://processmaker.atlassian.net/jira/software/c/projects/FOUR/boards/714 ``` **Goal:** Capture only the path after `atlassian.net/`. **Steps** 1. Edit the Jira application rule. 2. Add a new `extract_identifiers` entry: - Generated UUID - Regex pattern that extracts the URL path - `from_fields`: `["url"]` 3. Reference the identifier in the tags list: ```json {  "key": "content-category",  "value": "${extract_identifiers.}" } ``` 4. Save the configuration. ✅ **Result:** The window name displays only the relevant Jira path.