Guided Workflow Screen Components - Dynamic Table

Updated 

The Dynamic Table screen component lets Guided Workflow builders present structured data directly within a workflow step. This component is designed for admins and workflow designers who need to show real‑time information—such as search results, catalog items, availability lists, or status updates—to agents as they progress through a process. With Dynamic Tables, agents can scan large datasets, sort or select information, and take action without navigating away from the workflow.

Sprinklr also offers a Matrix Table layout within the Dynamic Table component. This layout displays data in a two‑dimensional grid, enabling agents to view and interact with information across both rows and columns.

Key capabilities include:

  • Display data in a structured table within a workflow step

  • Support for real‑time, dynamic values

  • Allow agents to sort, select, and act on data without leaving the workflow.

  • Support configurable sorting for entity-based Dynamic Tables using text, number, and date fields

  • Export Dynamic Table data to Excel or CSV for offline analysis and reporting.

  • Present information in a two‑dimensional grid using the Matrix Table layout

  • Dynamically expand rows and columns based on incoming data

  • Enable side‑by‑side comparisons and cross‑referenced selections

  • Support complex use cases such as:

    • Attribute mapping

    • Multi‑category or multi‑level selections

    • Option comparisons

    • Interactive availability or configuration grids

This gives workflow builders the flexibility to display structured or multi‑dimensional data in an intuitive, easy‑to‑scan format—helping agents make faster and more informed decisions.

Dynamic tables support features such as pagination, configurable filtering, search, multi-selection, and data export. Workflow builders can control whether the filter bar is displayed during runtime. Refer to the article on solving use cases with Groovy.

Various Fields in a Dynamic Table

Note: You can hover over the info icon next to each field for a description.

  • API Name: It is a unique identifier that can be used as a reference to the value of this component. In this field, ensure that there are no hyphens or spaces. It is typically used in backend code, integrations, or API calls. API Names are often system-generated and follow a specific naming convention, such as using underscores instead of spaces (e.g., Customer_Status__c). 

  • Mark Field as Mandatory: Clicking on the screen will mark filling this table as mandatory for the user.

  • Table Layout Type: When configuring a Dynamic Table, you can choose between two layout options:

    • Standard: The classic table view where you define static columns, and the rows are populated dynamically from a list variable. This is best used when the number of columns is fixed, but the number of data entries (rows) varies. By default, Standard Table is selected.

    • Matrix Table: A two-dimensional table where both rows and columns are generated dynamically from source variables. This layout supports Cell Selection, allowing users to select a specific intersection of data rather than selecting an entire row.

    Note: Some of the fields on the Dynamic Table page depend on the Table Layout selected.

    Standard Table Layout Fields

    The following fields are specific to Standard Table Layout.

  • Choose Data Source: There are 3 types of data sources available that you can choose from. This is applicable for Standard Table layout.

    • By Variable: Select data from pre-defined variables within the system.

    • By API: Fetch data dynamically using APIs.

    • By Entity Type: Utilize data linked to specific entities in the system.

  • Choose Variable: Add the name of the variable in this field. This field is used to define the data map to populate the dynamic table either directly or using a pre-defined variable.

  • Variable Name: In the Column Mapping section, again, add the variable name. This variable is the key name in the data map, which is used to map the values.

  • Column Name: Enter the column name to be displayed.

  • Variable Type: You can choose what type of variable it is - a text, an image, a pick list, a multiline, etc., from the dropdown menu.

    • For Text, Date, MultiValue, Picklist, MultiValue Picklist, Multi Line, and Media data types, you can configure the column width by clicking the Settings option next to the Variable Type drop-down.

    • For Number data type, you can configure the column width and alignment (start, center, end) of the value entered by clicking on the Settings option next to the Variable Type drop-down.

    • For Link data type, you can configure column width, Static Hyperlink Display Text, and Dynamic Hyperlink Display Text.

    Matrix Table Layout Fields

    The following fields are specific to Matrix Table Layout.

  • Choose Data Variable: This field is used to define the data map to populate the dynamic table either directly or using a pre-defined variable.

  • Principal Column Variable: Enter the variable name that defines the rows of the table.

  • Principle Column Title: Enter the title to be displayed for the index column. This is the static title for the very first column.

  • Dynamic Column Source Variable: Enter the list variable that defines the dynamic columns of the table.

  • Cell Value Variable: Enter the variable names that contain the actual value to display in the cell.

  • Width of Dynamic Columns: Set the width (in px) for dynamically generated columns. If left blank, auto width will be applied.

    Cell Selection and Visual Highlighting

    When a user selects a cell in the Matrix Table, the selected cell is visually highlighted with a distinct color or border to clearly indicate the active selection. The highlight persists for as long as the selection remains active and is removed when the selection is cleared. This makes it easy for agents to track their selections, especially when navigating across multiple workflow screens.

    Common Fields

    The following are the Common Fields for both Standard and Matrix Table Layouts:

  • Primary Key: Whatever Column Name variable you select will come as the primary key.

  • Default Value: You can configure the pre-populated value in a dynamic table when the Guided Workflow starts. You can choose a variable here or write custom code. You can specify default values based on the Primary Key defined for the table.

    For example, suppose the Choose Variable field contains the following array of objects:

    [{"Product": "Coffee", "Type": "Espresso", "Quantity": 2},{"Product": "Coffee", "Type": "Cappuccino", "Quantity": 1}]

    And your Primary Key is set to Type.

    If you want to pre-select only the row where Type = Espresso, your Default Value should be:

    {"Type": "Espresso"}

    To pre-select both rows (Espresso and Cappuccino), use:[{"Type": "Espresso"},{"Type":"Cappuccino"}]

  • Maximum Height / Row Height: In these fields, you can select the table and row height that you want.

  • Add on Select Action:

  • Freeze First Data Column: If you enable this toggle, the first column, particularly, will be frozen.

  • Enable Wrapping of Call Text: This toggle allows you to display complete cell content within a Dynamic Table by wrapping text across multiple lines instead of truncating it. When enabled, long text values are automatically adjusted to fit within the cell, increasing the height of the cell and corresponding row to ensure full visibility. This helps you view all information at a glance without needing to hover over cells, improving readability and overall workflow efficiency.

  • Enable Row Selection: To enable row selection, you can configure the dynamic table to allow either single or multi-selection. For example, if there are multiple items, and you enable a single selection, the user will only be able to select one item at a time. On the other hand, if you enable multi-selection, the user can select multiple items simultaneously, offering greater flexibility and control over the data they interact with.

  • Visibility Conditions: A rule or set of rules that determine whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

    • Example  

      • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High." 

      • Implementation: Visibility Condition: Ticket_Priority == 'High' 

      • Result: The "Priority Escalation" section appears only for high-priority tickets. 

  • Enable Pagination: You can enable pagination to control how many rows are displayed per page in the dynamic table. For example, if you want to show only 10 rows per page, the table will display the first 10 rows, and then the user can navigate to the next page to see the remaining rows. If you opt to show 5 rows per page, and there are 20 items in total, the data will be spread across four pages. This feature helps to keep the data manageable and user-friendly, especially when dealing with large datasets.

  • Color by Conditions: It lets you automatically apply a color to an entire table row (or a specific element) when selected field values meet defined conditions.

  • Enable Search – Enable this option to allow searching within the columns of a dynamic table.

    • To enable search in a Dynamic Table by API, the API must have paginated responses with search capabilities.

    • To enable search in a Dynamic Table by Entity, the specific column must be marked as Searchable in the Entity Studio.

  • Show Filter Bar

    Use this option to control whether the filter bar is displayed in the Dynamic Table during runtime.

    When enabled, users can filter table records using the configured filter options. When disabled, the filter bar is hidden from the runner, providing a cleaner interface for workflows where filtering is not required.

    Show Filter Bar is disabled by default.

    When you enable Show Filter Bar, the following configuration options become available:

    • Upfront Filter Columns – Select the columns that users can filter directly from the filter bar.
    • Preset Quick Filters – Configure predefined filter options that users can apply with a single click.

    When Show Filter Bar is disabled, the filter bar and its related configuration options are hidden.

    Note: Hiding the filter bar does not affect other table capabilities such as row selection, pagination, scrolling, sorting, or table export.

Note: Searching is supported only in the Dynamic Table by API and the Dynamic Table by Entity.

Note: Dynamic Tables now retain the last viewed page when users navigate back to the screen during the same Guided Workflow session. The page state is reset when the workflow is refreshed or restarted.

  • Hide Index Column: Hides the first column. This is applicable for Matrix Table Layout.

  • Hide Column Header: Hides the top row of headers. This is applicable for Matrix Table Layout.

  • Hide Footer: Removes the pagination footer. This is applicable for Matrix Table Layout.

Configuring a Dynamic table by various source types

  1. By Variable:

    Configuration Fields

    • API Name: Enter a unique identifier for the component. Do not use spaces or hyphens. API names are typically used in backend logic, integrations, and API references, and generally follow a system-friendly naming convention (for example, Customer_Status__c).
    • Mark Field as Mandatory: Enable this option to make row selection in the table mandatory.
    • Table Layout Type: Select Standard as the layout type.
    • Choose Data Source: Select By Variable.
    • Choose Variable: Specify the variable that contains the data used to populate the dynamic table. You can either use a directly defined data map or a predefined variable.

    Column Mapping

    Use column mapping to control how data is displayed in the table.

    • Variable Name: Enter the field name that contains the data value.
    • Column Name: Enter the label to display as the column header.
    • Variable Type: Select the appropriate data type, such as Text, Image, Picklist, Multi Line, or others, to ensure correct formatting and validation.

    Note:

    • For Text, Date, MultiValue, Picklist, MultiValue Picklist, Multi Line, and Media data types, you can configure the column width using Settings next to the Variable Type field.

    • For the Number data type, both column width and value alignment (Start, Center, End) can be configured.

    • For the Link data type, you can configure column width, Static Hyperlink Display Text, and Dynamic Hyperlink Display Text.

    • Primary Key: Select the column that uniquely identifies each record in the table.

    • Default Value: Specify a predefined value that is displayed when the component loads. This can be a static value or sourced dynamically from a variable.

    • Maximum Height: Enter the maximum table height in pixels.

    • Row Height: Enter the row height in pixels. The value must be greater than 24 px.

    Table Options

    • Make Row Copiable: When enabled, hovering over the row number displays a copy icon that allows users to copy the entire row and paste it elsewhere.
    • Freeze First Data Column: Keeps the first column fixed while horizontally scrolling through the table.
    • Enable Wrapping of Cell Text: Displays complete cell content by wrapping text across multiple lines instead of truncating it. Row height automatically adjusts to accommodate the wrapped content, improving readability.
    • Enable Row Selection

      : Configure the table to support either:

      • Single Selection – Users can select only one row at a time.
      • Multi Selection – Users can select multiple rows simultaneously.

    Visibility Condition

    A visibility condition determines when a component appears to users based on predefined criteria, such as field values or contextual information. This helps display only relevant information and improves the user experience.

    Example

    • Condition: Display a Priority Escalation section when Ticket Priority is set to High.
    • Visibility Condition: Ticket_Priority = 'High'
    • Result: The Priority Escalation section is displayed only for high-priority tickets.

    Enable Pagination

    Enable pagination to control the number of rows displayed per page. For example:

    • If 10 rows per page are configured, only the first 10 records are displayed, with navigation controls available for additional pages.
    • If 5 rows per page are configured and the table contains 20 records, the data is distributed across four pages.

    Pagination improves usability when working with large datasets.

    Hide Footer

    Enable this option to hide the table footer.

    Note: Dynamic table footer text is automatically localized when the user locale is set to Korean.

    Enable Table Export

    Enable this option to allow users to export dynamic table data during runtime. An Export action becomes available, allowing users to download data in:

    • Excel (.xlsx)
    • CSV (.csv)

    The exported file includes:

    • Current table data
    • Applied filters
    • Column headers
    • Data formatting

    This makes the exported data suitable for reporting and offline analysis.

    Note: The Export option is available only when Enable Table Export is enabled in the Dynamic Table configuration. The Export button appears alongside the Filter option in the Dynamic Table toolbar during runtime.

    Sample Configuration: Dynamic Table By Variable

    To populate a Dynamic Table using a variable, the variable output must be structured as an array of maps.

    Example

    JavaScript


    return [

    ["Product": "Coffee", "Type": "Espresso", "Quantity": 2],

    ["Product": "Coffee", "Type": "Latte", "Quantity": 3],

    ["Product": "Tea", "Type": "Green Tea", "Quantity": 5],

    ["Product": "Tea", "Type": "Black Tea", "Quantity": 4],

    ["Product": "Juice", "Type": "Orange", "Quantity": 6],

    ["Product": "Juice", "Type": "Apple", "Quantity": 2],

    ["Product": "Soda", "Type": "Cola", "Quantity": 7],

    ["Product": "Soda", "Type": "Lemon-Lime", "Quantity": 3],

    ["Product": "Smoothie", "Type": "Strawberry Banana", "Quantity": 1],

    ["Product": "Smoothie", "Type": "Mango", "Quantity": 4]

    ]

    After creating the variable:

    1. Select the variable in the Choose Variable field.
    2. Configure column mappings using the keys from the array of maps.

      • Product → Variable Name
      • Type → Variable Name
      • Quantity → Variable Name
    3. Enter user-friendly labels in the Column Name field.
    4. Select the appropriate Variable Type for each column.
    5. Configure a Primary Key to uniquely identify table records.



  1. By API: A Dynamic Table by API will be used when you have data coming from an API and you want to display the information in the form of a table. Ensure that the API response is in paginated format; if the API is not in paginated format, you should not use a dynamic table with the API. 

    Various Fields in a Dynamic Table By API 


    • API Name: It is a unique identifier that can be used as a reference to the value of this component. In this field, ensure that there are no hyphens or spaces. It is typically used in backend code, integrations, or API calls. API Names are often system-generated and follow a specific naming convention, such as using underscores instead of spaces (e.g., Customer_Status__c).

    • Mark Field as Mandatory: Clicking on the screen will mark the selection of the row of the table as mandatory. 
    • Table Layout Type: Choose the layout type as Standard.
    • Choose Data Source: Choose By API. 
    • Service Name: Select the API service name to be used as a data source. Only paginated APIs can be used in a dynamic table. 
    • Select Controlling Field: Select the field(s) to refetch values of the dynamic table based on a change in field values. For example, consider a Picklist field added on the screen with multiple options (for example, Option 1 and Option 2). When Option 1 is selected, the Dynamic Table makes an API call and displays data corresponding to that selection. If the user then changes the picklist value to Option 2, the Dynamic Table automatically refetches the data by triggering another API call and refreshes the table with the updated results.
    • Column Mapping: Use column mapping to define how data fields are displayed and interpreted in the table.

      • Variable Name: Specify the field name that stores the data value.
      • Column Name: Enter the label to be displayed as the column header in the table.
      • Variable Type: Select the appropriate data type for the field to ensure correct formatting and validation. You can choose what type of variable it is - a text, an image, a pick list, a multiline, etc., from the dropdown menu.

    Note:

    • For Text, Date, MultiValue, Picklist, MultiValue Picklist, Multi Line, and Media data types, the column width can be configured by clicking the Settings option next to the Variable Type drop-down.

    • For the Number data type, both the column width and value alignment (Start, Center, End) can be configured using the Settings option next to the Variable Type drop-down.

    • For the Link data type, the column width, Static Hyperlink Display Text, and Dynamic Hyperlink Display Text can be configured from the Settings option.

    • Primary Key: Primary key is something that defines the uniqueness in the table. Select the column name as the primary key to identify a unique table record.

    • Default Value: The default value for the component is a pre-populated entry displayed when the form or input field is initially loaded. This value can be either a static text entry or dynamically sourced from a variable.

    • Maximum Height: Enter the maximum height of the table in px.

    • Row Height: You can enter the row height in px. Make sure that the value you enter is greater than 24px.

    • Make Row Copiable: When this toggle is enabled, hovering over the number column in the configured Dynamic Table on the Agent-Facing Guided Workflows displays a copy button. This allows you to copy the entire row and paste it wherever required.

    • Freeze First Data Column: The first column of the table will be frozen even if you scroll.

    • Enable Wrapping of Cell Text: This toggle allows you to display complete cell content within a Dynamic Table by wrapping text across multiple lines instead of truncating it. When enabled, long text values are automatically adjusted to fit within the cell, increasing the height of the cell and corresponding row to ensure full visibility. This helps you view all information at a glance without needing to hover over cells, improving readability and overall workflow efficiency.

    • Enable Row Selection: To enable row selection, you can configure the dynamic table to allow either single or multi-selection. For example, if there are multiple items, and you enable a single selection, the user will only be able to select one item at a time. On the other hand, if you enable multi-selection, the user can select multiple items simultaneously, offering greater flexibility and control over the data they interact with

    • Visibility Conditions: A rule or set of rules that determines whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

      • Example  

        • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High." 
        • Implementation: Visibility Condition: Ticket_Priority == 'High' 
        • Result: The "Priority Escalation" section appears only for high-priority tickets. 
    • Enable Pagination: You can enable pagination to control how many rows are displayed per page in the dynamic table. For example, if you want to show only 10 rows per page, the table will display the first 10 rows, and then the user can navigate to the next page to see the remaining rows. If you opt to show 5 rows per page, and there are 20 items in total, the data will be spread across four pages. This feature helps to keep the data manageable and user-friendly, especially when dealing with large datasets.
    • Color by Conditions: This field lets you automatically apply a color to an entire table row (or a specific element) when selected field values meet the defined conditions.
    • Enable Search: Enable this option to allow searching within the columns of a dynamic table. To enable search in a Dynamic Table by API, the API must have paginated responses with search capabilities.
    • Hide Footer: If you enable this toggle, the footer of the table will be hidden.

    Note: The dynamic table footer text is localized for Korean when the locale is set to Korean, instead of always appearing in English.

    • Enable Table Export: Enable this option to export data from the Dynamic Table during runtime. When enabled, an Export action is displayed in the table, allowing you to download the displayed data in Excel (.xlsx) or CSV (.csv) format. The exported file includes the current table data along with the applied filters, column headers, and data formatting, making it suitable for offline analysis and reporting.
    • Filter Bar: You can enable or disable it to control the visibility of the Filter Bar on the dynamic table. If you enable this toggle, you can configure the following fields: 

      • Upfront Filter Columns: Select the columns to be displayed for filtering at all times. The upfront filtering option will not work if the API response does not include facet data, which is required to identify filterable values and apply filtering logic. Without facet information, the system cannot determine which values can be filtered upfront. To enable upfront filtering, the API response schema must be updated to include facet data. Until then, the expected filtering experience is not technically feasible.
      • Present Quick Filters: You can define static filters to control the display of data in the dynamic.

        • Filter Name: You can give a unique name to your filter.
        • Enable Filter by Default: If you enable this toggle, the filter will be enabled by default. If you keep this toggle disabled, you will have to apply the filter after running the Guided Workflow. 
        • Where: Define the conditions of the filter.

    Note: You can add multiple conditions in the same filter by clicking + Add Condition or add multiple filters by clicking + Add Filter. 

    Sample Configuration of a Dynamic Table by API

    To configure a dynamic table by API as a source, follow the following steps: 

    • Choose the API/Extension under the Service Name section. 
    • Pass the inputs to the API as defined in the API documentation under the Set Input Variables Mapping section. 
    • Write an adapter under the “Adapt API Response” section to adapt the response.
    • For Example, if the API Response is in the following format:

      OrderDetails : [ { "OrderNumber: 10, "OrderId": 123, "Description": "T-shirt" }, { " OrderNumber ": 11, " OrderId ": 115, " Description ": "Jeans" }, { " OrderNumber ": 12, " OrderId ": 164, " Description ": "hand bag" }]

      Then the Adapt API Response will be as given below:

      return response.OrderDetails;
    • The first variable name, in this case, would be "OrderNumber", and the corresponding column name, which is meant for a display to the user, could be "Order Number". The second variable name would be "OrderId", and the third variable name would be "Description", with their respective column names formatted appropriately for user-friendly display.
  2. By Entity: A Dynamic table by API will be used when you have data coming from a Sprinklr entity, like a standard entity, a custom entity, etc, and you want to display the information in the form of a table. To configure a dynamic table by Entity as the source, follow the following steps:

    • API Name: It is a unique identifier that can be used as a reference to the value of this component. In this field, ensure that there are no hyphens or spaces. It is typically used in backend code, integrations, or API calls. API Names are often system-generated and follow a specific naming convention, such as using underscores instead of spaces (e.g., Customer_Status__c). 
    • Mark Field as Mandatory: Clicking on the screen will mark the selection of the row of the table as mandatory.
    • Table Layout Type: Choose the layout type as Standard.
    • Choose Data Source: Choose By Entity Type. 
    • Entity Type: Select a Standard or Custom Entity to display records. 
    • Column Mapping: Use column mapping to define how data fields are displayed and interpreted in the table.

      • Variable Name: Specify the field name that stores the data value.
      • Column Name: Enter the label to be displayed as the column header in the table.
      • Variable Type: Select the appropriate data type for the field to ensure correct formatting and validation. You can choose what type of variable it is - a text, an image, a pick list, a multiline, etc., from the dropdown menu.

    • For Text, Date, MultiValue, Picklist, MultiValue Picklist, Multi Line, and Media data types, the column width can be configured by clicking the Settings option next to the Variable Type drop-down.
    • For the Number data type, both the column width and value alignment (Start, Center, End) can be configured using the Settings option next to the Variable Type drop-down.
    • For the Link data type, the column width, Static Hyperlink Display Text, and Dynamic Hyperlink Display Text can be configured from the Settings option.
    • Filter Records: You can apply a filter based on the fields available in the entity. You can apply multiple filters by clicking + Add Condition and applying And/Or logic.
    • Sort Record By: This field allows you to control how values in the Dynamic Table are ordered on the UI. Dynamic Tables use lexicographical sorting to organize the displayed records.
    • Sort Order: You can choose if you want to sort the order in ascending or descending order from the dropdown.
    • Primary Key: A primary key is something that defines the uniqueness in the table. Select the column name as the primary key to identify a unique table record.
    • Default Value: The default value for the component is a pre-populated entry displayed when the form or input field is initially loaded. This value can be either a static text entry or dynamically sourced from a variable.
    • Maximum Height: Enter the maximum height of the table in px.
    • Row Height: You can enter the row height in px. Make sure that the value you enter is greater than 24px.
    • Make Row Copiable: When this toggle is enabled, hovering over the number column in the configured Dynamic Table on the Agent-Facing Guided Workflows displays a copy button. This allows you to copy the entire row and paste it wherever required.
    • Freeze First Data Column: The first column of the table will be frozen even if you scroll.
    • Enable Wrapping of Cell Text: This toggle allows you to display complete cell content within a Dynamic Table by wrapping text across multiple lines instead of truncating it. When enabled, long text values are automatically adjusted to fit within the cell, increasing the height of the cell and corresponding row to ensure full visibility. This helps you view all information at a glance without needing to hover over cells, improving readability and overall workflow efficiency.
    • Enable Row Selection: To enable row selection, you can configure the dynamic table to allow either single or multi-selection. For example, if there are multiple items, and you enable a single selection, the user will only be able to select one item at a time. On the other hand, if you enable multi-selection, the user can select multiple items simultaneously, offering greater flexibility and control over the data they interact with.
    • Visibility Conditions: A rule or set of rules that determines whether a specific element, field, or component is visible to users in an application or interface. These conditions are typically based on factors such as field values or contextual data. Visibility conditions ensure that users only see relevant information, improving usability and security. 

      • Example  

        • Condition: Display a "Priority Escalation" section if the "Ticket Priority" is set to "High." 
        • Implementation: Visibility Condition: Ticket_Priority Equals 'High' 
        • Result: The "Priority Escalation" section appears only for high-priority tickets. 
    • Enable Pagination: You can enable pagination to control how many rows are displayed per page in the dynamic table. For example, if you want to show only 10 rows per page, the table will display the first 10 rows, and then the user can navigate to the next page to see the remaining rows. If you opt to show 5 rows per page, and there are 20 items in total, the data will be spread across four pages. This feature helps to keep the data manageable and user-friendly, especially when dealing with large datasets.
    • Color by Conditions: This field lets you automatically apply a color to an entire table row (or a specific element) when selected field values meet the defined conditions.
    • Enable Search: Enable searching of values within the dynamic table using a search bar. Only applicable for API type tables if searching is supported by the external API.
    • Hide Footer: If you enable this toggle, the footer of the table will be hidden.

    Note: The dynamic table footer text is localized for Korean when the locale is set to Korean, instead of always appearing in English.

    • Enable Table Export: Enable this option to export data from the Dynamic Table during runtime. When enabled, an Export action is displayed in the table, allowing you to download the displayed data in Excel (.xlsx) or CSV (.csv) format. The exported file includes the current table data along with the applied filters, column headers, and data formatting, making it suitable for offline analysis and reporting.
    • Filter Bar: You can enable or disable it to control the visibility of the Filter Bar on the dynamic table. If you enable this toggle, you can configure the following fields:

      • Upfront Filter Columns: Select the columns to be displayed for filtering at all times. You can add as many columns as you need.
      • Present Quick Filters: You can define static filters to control the display of data in the dynamic. 

        • Filter Name: You can give a unique name to your filter.
        • Enable Filter by Default: If you enable this toggle, the filter will be enabled by default. If you keep this toggle disabled, you will have to apply the filter after running the Guided Workflow. 
        • Where: Define the conditions of the filter.

    Note: You can add multiple conditions in the same filter by clicking + Add Condition or add multiple filters by clicking + Add Filter.

Sort Records By

When configuring a Dynamic Table with Data Source = By Entity Type, you can define how records are ordered when displayed in the table.

The Sort Records By field allows you to select an entity field and configure the sort direction.

Supported sorting behavior:

  • Text fields are sorted alphabetically (A–Z or Z–A).
  • Number fields are sorted numerically.
  • Date fields are sorted chronologically.
  • Any field configured as a Dynamic Table column can be selected as a sorting field.
  • All Date-type fields are available for sorting, even if they are not displayed as table columns.

This functionality is supported for both Standard Entities and Custom Entities.

Example

If a Dynamic Table displays Case records and includes the fields Case Number, Priority, and Created Time, you can configure the table to:

  • Sort by Created Time (Newest to Oldest)
  • Sort by Priority
  • Sort by Case Number

to control the order in which records appear during runtime.