Workflow considerations for table fields

You can use active links and filters to modify data in the source form of a table field as follows:

  • Create a Set Fields action to pull request data from a row into a set of fields.
    Users can then modify the values in the set of fields.
  • Create a Push Fields action to push the new values into the request on the source form.
  • Create a Change Field action to refresh the table.
    You can create active link and filter guides that loop through rows in a table. A guide selects each row in a table field (without highlighting) and performs a series of workflow actions on the row. For more information, see Creating-a-filter-guide-that-loops-through-a-server-side-table-field.
    You can also select rows and create statistics on columns such as sums, averages, maximum and minimum values, and total number of rows or total number of non-NULL values in a column. For more information about functions you can use with table fields, see Controlling-row-selection-in-a-table-field.

Related topics

Creating-table-fields

Defining-a-context-menu

See the following sections for further workflow considerations.

Workflow in tree view tables

In a tree view, a node can represent one or more requests. If a node representing multiple requests is selected, the first request listed under the node is considered the primary request, and the other requests are secondary. Workflow uses the primary request for all field value references except those in table loop guides. In table loop guides, all the requests (primary and secondary) are processed in turn. See Tree-view-table-fields.

Workflow in cell-based tables

Workflow in cell-based tables (for example, running active links on row selection or setting the current row by using an active link Set Field action) works the same as it does in other table types, such as list view. Workflow in cell fields works the same as it does in list view table column fields. 

Clicking a button runs workflow that executes on a Button/Menu Field selection for the cell field. Workflow associated with the control field to which the cell field is linked, however, does not fire. No other field-based workflow execution options, including gain focus and lose focus, are supported for cell fields.

Workflow in dynamic context menu

AR System menus can be attached to the table context menu item through indirect change field action. At run-time the Character Field accepts the fieldId of the context menu to which the AR System menu later attaches. Menu selection triggers the workflow that is tied to the table context menu item. Workflow can discover the value of the menu item that is selected through $context menu item id$. 

The dynamic menu follows the properties of the context menu. For example, if the context menu is hidden, the dynamic menu cannot be seen. Similarly, you can enable or disable the dynamic menu. When disabled, users can view the menu items but cannot select any of them. The menu items are accessible when the context menu is enabled.

Workflow considerations for images in tables

When the Set Fields action uses the column with images as a source ($columnFieldName$), the value of the column field is always the text, never the image.

If the Set Fields action is performed on a table cell that has an image and a text value, the action overwrites the text value. The image is never overwritten. 

Images are not accessible by workflow because images are decoration, not data. No value is associated with the image.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*