Form Table

1. Description

Allows displaying a table with external data in the scheme form.

The block (Fig. 1.(1)) is placed in the field for building the scheme. Clicking the block opens the component settings panel (Fig. 1.(2)).

2. Form Table block

The Form Table block (Fig. 1.(1)) consists of the following elements:

• Component name;

• "In" branch — incoming (connects with the previous block);

• "Out" branch — outgoing (connects with the next block).

When hovering over the "Out" field, a switch appears allowing the component to be connected to another block that already has a connection.

If the icon is visible, the switch is enabled, and the component can connect to another already connected block.

Toggling the switch removes the outgoing branch.

The button deletes the block from the scheme.

3. Form Table settings panel

The Form Table component's settings panel (Fig. 2) consists of the following elements:

3.1. ID

A unique identifier for the component in the scheme (Fig. 2.(1)).

The value selected by the operator in the service selection field will be saved in a variable with this ID. It can be used in the next steps of the scheme.

3.2. Source

A text input field (Fig. 2.(2)) where a variable with a JSON object can be passed. The table will be formed based on it.

3.3. Use system sources

If enabled – — the System sources field becomes active, and the "Source" field is disabled (Fig. 2.(3)).

3.4. System sources

Webitel system object selector (Fig. 2.(4)):

• "Users";

• "Roles";

• “Contacts“;

• “Calendars“;

• “Lists“;

• “Queues“;

• “Communication Types“;

• “Cases“;

• “Contact Groups“;

• “Case Sources“;

• “Agents“;

• “Priorities“.

Data from this source is used to populate the table.

3.5. View block

The View block (Fig. 2.(5)) is used to configure the appearance of the table in the after-call form. It allows you to set the table header and define whether the table will be expanded or collapsed by default.

Fields of the block:

• Table header;

• Collapsed by default.

3.5.1. Table header

A text field, optional. Here you can specify the name of the table that will be displayed in the after-call form in Workspace. If the field is not filled in, the default name Table is displayed.

3.5.2. Collapsed by default

A switch.

• If turned off (default), the table in the after-call form in Workspace is displayed immediately in expanded view.

• If turned on, the table will be shown in collapsed view.

3.6. Display columns

This block (Fig. 2.(6)) is used to configure the columns displayed in the table:

• Display column;

• Display name;

• Format;

• Width (px).

3.7. Field “Display column”

The name of the column (for example, phone_number) that will be displayed (Fig. 2.(7)).

3.8. Field “Display name”

The name of the system column for selection, which is displayed in the form (Fig. 2.(8)).

3.9. Field “Format”

The field (Fig. 2.(9)) is used to define the format in which data will be displayed in the table column. It is mandatory for each column.

Available formats:

• text — the value is displayed as a text string. If the attribute contains an array (for example, a list of numbers), it will be shown as text separated by commas;

• number — a numeric value;

• bool — used for boolean values. In the table, they are automatically displayed as icons:

  • if the value equals true (“yes”);

  • if the value equals false (“no”);

• datetime — used to display date and time. If the data contains a timestamp (for example, 1727936700), the system will automatically display it in a readable date and time format (for example, 03.10.2025 09:25:00);

• link — the value is displayed as a clickable hyperlink.

3.10. Width (px)

Column width in pixels. If not specified, it is calculated automatically (Fig. 2.(10)).

3.11. Add

Clicking the "Add" button (Fig. 2.(11)) adds a new column (Fig. 3). The remove tool becomes available to remove it.

3.12. Fields block

The block (Fig. 2.(12)) is designed to store additional fields of a system object in a variable. These values are not necessarily displayed in the table but are available for further processing in other components of the scheme.

3.13. Field

The Field (Fig. 2.(13)) is used to enter the name of a system attribute from the data source that needs to be stored in a variable.

The user can add multiple such fields to ensure access to the required values later, even if they are not displayed in the table.

Adding new fields is done using the ![add icon], and deleting fields — using the ![delete icon].

You can add new fields — or remove them — .

3.14. Filters

The block (Fig. 2.(14)) appears only when the "Use system sources" switch is enabled (see section 3.3). Allows specifying the conditions by which data from the selected source will be shown in the table.

3.15. Filter

The Filter field (Fig. 2.(15)) allows you to manually specify the condition for filtering data from the selected source.

To fill this field correctly:

1. Go to the section where the entity is located (e.g., CRM → Contacts).

2. Apply the necessary filter in the regular interface (Fig. 4).

3. Open Developer Tools ("DevTools") and go to the "Network" tab (Fig. 5).

4. Find the request that adds the filters (Fig. 6.(1)) and go to the "Payload" tab (Fig. 6.(2)).

5. Copy the parameter name and value (e.g., user true) (Fig. 7).

6. Return to the component in the scheme and enter the value in the "Filter" field in the following format:

user=true

The icon allows you to create an additional "Filter" field within the "Filters" block. This enables you to define multiple filtering conditions (Fig. 8).

To remove a condition, click the icon next to the field.

user=true&label=df

3.16. Test

The button (Fig. 2.(16)) checks whether the query returns results that will appear in the post-processing form.

3.17. Response

The field (Fig. 2.(17)) displays JSON data returned after clicking "Test". To view the entire content, click the expand or collapse .

Each new click on "Test" updates the field content.

If the query was valid, the objects with values are displayed (Fig. 10).

These values are then substituted into the dropdown in the post-processing form in Workspace (Fig. 11).

3.18. Action buttons

This block (Fig. 2.(18)) allows creating buttons in the table to be displayed in the specified columns.

Contains the fields:

• Column name;

• Action;

• Button name;

• Button color;

• Variable.

Button management:

• Add — adds the button to the table;

• Cancel — cancels the action.

3.19. Column name

The column (Fig. 2.(19)) where the button will appear. Can be an existing or separate column.

3.20. Action

The name of the event (exit in the scheme) (Fig. 2.(20)) triggered when the button is clicked. Also used as a variable to save the row.

3.21. Button name

The text on the button (Fig. 2.(21)).

3.22. Color

Button color (Fig. 2.(22)), selected from the list (Fig. 13):

3.23. Break

The toggle (Fig. 2.(23)) defines whether the scheme execution ends after this step.

• — ends scheme execution after this component;

• — toggle is off.

3.24. Add limit

Used to define the maximum number of passes through this component.

Clicking "Add limit" (Fig. 2.(24)) adds the "Max" field and the "Delete limit" button (Fig. 14). The "Max" field defines the allowed number of passes.

If the number of passes exceeds the value in "Max", the "Failover" branch will be used (Fig. 15), which appears in the component block after setting the limit.

Clicking "Delete limit" removes the limit and returns the "Add limit" button.

3.25. Add description

Clicking "Add description" (Fig. 2.(25)) adds the "Description" field and "Delete description" button (Fig. 16).

In the "Description" field, enter a comment about the component.

Clicking "Delete description" removes the description and restores the "Add description" button.

4. Display of the Component in the Post-Processing Form (Workspace)

In the post-processing form, the Form Table component is displayed as a section that is:

• initially collapsed if the Collapsed by default switch is disabled (Fig. 17);

• or expanded if the Collapsed by default switch is enabled.

Clicking the icon expands the component and displays the table with data (Fig. 18).

To expand the table when it is displayed in a collapsed state, click the . After this, the table with data will be displayed (Fig. 18).

4.1. Table content

The table displays the columns defined in the scheme settings in the "Display columns" block (see section 3.6). For example, id and name.

4.2. Row structure

Each row contains values corresponding to the selected JSON fields returned after filtering.

4.3. Action button

If buttons are configured (via the "Action buttons" block (see section 3.18)), each row will show a corresponding button (e.g., "CALL" or "CLICK"). Clicking it triggers a scheme event associated with the current row.