Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Use data from a table field in GlobalCapture to update field lists. This node is commonly used in scenarios where GlobalCapture is being used to keep lists in sync between itself and a 3rd party ERP system.

Setup

Before you being, ensure the workflow includes a reference to a field that is bound to the list you wish to update. Additionally, a table field with at least one column should be present, and controls should exist in the workflow to ensure the table field has data at the point where the List Update node is hit.

  • Field Bound To Update List
    Select the Process Field that is bound to the list you wish to update. The list MUST be bound to the field selected here.

  • Table Field Containing List Values
    Select the table field with the data you wish to use when updating the list. The field may have one or more columns of data. Not all data in the table is required, so if the table is serving multiple purposes, that is okay.

  • Table Column Mapping
    Use field notation to set the values, referencing the columns of the table that should be used to set each list item. You can use multiple columns of the table. For example, if you had a table that included a column “number” and a column “displayName”, this node setting might look like:

    “{p_number} | {p_displayName}”

    Which would be expected to output something like “10029 | Square 9 Softworks, Inc.”.

  • Append To List - No Overwrite
    Enable this option if you want successive updates to be additive. By default, every time the node is hit, the list will be cleared and it’s contents fed from the current processes table data.

  • No labels