Guided Workflow Screen Components - Record Table Component

Updated 

Overview

The Record Table Component within the Guided Workflow is a feature that allows you to display the Record Manager on the Guided Workflow. It is designed to streamline the presentation of data within the workflow interface. It allows you to showcase selected fields from a record manager, which can be based on either standard or custom entities. By enabling the display of only a few critical columns from potentially extensive datasets, the Record Table helps you to focus on the most relevant information without being overwhelmed by excessive details. On a certain entity, you can create multiple record managers.

Enablement

To utilize the Record Table Component within the Guided Workflow, you must have access to CRM Studio, and a Record Manager should be created at the partner level.

Key Benefits 

  • Focused Information Display: The Record Table gives you the option to showcase only the most relevant columns from a record manager, thereby enabling you to concentrate on critical data without the distraction of unnecessary information. 

  • Enhanced Usability: By providing a user-friendly interface that supports inline editing, the Record Table streamlines data management, giving you the opportunity to make quick updates directly within the table, thereby improving overall efficiency. 

  • Customizability: You can also tailor the Record Table to meet specific needs by selecting the desired entity and record manager, ensuring that the displayed information aligns with your business requirements and enhances the workflow. 

  • Reduce duplication of work: The Record Table component also reduces the duplication of work. If a record manager is already created, it can be directly presented to the agent, eliminating the need to recreate the data display. 

Various Fields in Record Table Component

  • API Name: The API Name is a unique identifier used to reference a particular object, field, or component in an application programmatically. 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: To mark the field mandatory, if the field is not a field, it will not allow the user to move to the next step. 

  • Entity Type: You can either choose a standard entity or a custom entity from the dropdown.

  • Flavour: The flavor is defined in the record manager JSON. If the Record Manager ID is not configured, the flavour can be checked from the relevant JSON file and can be added manually in the configuration.

  • Record Manager ID: This is a unique identifier for each Record Manager, used to ensure that the correct manager is linked to the Record Table component within a Guided Workflow. A Record Manager allows you to control which specific columns from an entity are displayed, making it especially useful when dealing with entities that contain a large number of fields. Instead of displaying all fields (e.g., 100), you can configure the Record Manager to show only the most relevant 4–5 key fields, streamlining the user experience and improving data focus.

  • Height: You can select the table and row height that you want.

  • Variant: You can select the kind of background/table variant that you want. The available options are:

    • Default: Grey Background

    • White Background

  • Set Record Table Context: When creating a record form in Entity Studio, users have the option to apply a filter to refine the data displayed. To make this filter dynamic, the required value must be passed using Set Record Table Context.

    • Define a filter in the Entity Studio by selecting a column value and setting it to a filter variable.

    • Use the corresponding filter variable (data) in Set Record Table Context and pass the corresponding value to filter the data.

    • For example, if you want to filter products based on the brand, you can define a filter in Entity Studio. Once you select a brand, such as XYZ, this selection is passed as a parameter to apply the filter, ensuring that only relevant products are displayed.

Inline Editing Capability Within the Record Table in the Guided Workflows 

  • The Inline Editing capability of the Record Table component within the Guided Workflow significantly enhances your experience by allowing you to modify data directly within the entity itself, without navigating to other sections or interfaces. This feature reduces the complexity of updating data by enabling real-time edits to the displayed records, making the process more efficient and seamless. The values entered are seamlessly updated in the corresponding entity without additional navigation or steps. You can view, edit, and save changes instantly, streamlining workflows and reducing the time spent on manual updates, thus improving overall productivity.

  • How to enable inline editing - Inline editing is configured in Entity Studio. When creating a record form, there is an option to enable inline editing, allowing you to select specific columns for which it should be applied.

  • If you need the record table to be editable, ensure that the Record Manager is configured for inline editing. In the Record Manager settings, you can specify which columns should be editable. Only the columns marked as editable will allow agents to make changes directly in the record table during workflow execution. 

Frequently Asked Questions  

A. Not all Record Tables are editable by default. The ability to edit data in a Record Table depends on the configuration set at the entity level in CRM Studio or Entity Studio. To make a Record Table editable, you need to go to the Record Manager in CRM Studio, edit the record manager, and specify which columns are allowed for inline editing. Only columns marked as editable can be modified directly in the table.