Calculated Field Set Processes

Process of Setup/Configuration

cfs setup.drawio
  1. The user creates a new Calculated Field Set

  2. The user selects the master table to be processed by the Calculated Field Set and optionally also the filter, if only limited list of rows should be processed.

  3. The user selects the logic to be used for this Calculated Field Set process.

  4. The system will execute the selected Calculated Field Set logic in Input Generation mode, in order to find out, if this logic requires the user to enter some inputs as part of the Calculated Field Set setup

  5. The system will collect the input field definitions from the logic context, and present them to the user on the Calculated Field Set setup page

  6. The user enters values to the input fields (if any)

  7. The user sets up the mapping of the visible logic elements to the fields of the data table. This is optional, the user does not have to do that. In that case the process will still execute for filtered rows, but no results will be mapped back.

  8. The user saves the Calculated Field Set definition.

Process of Execution

cfs calculation.drawio
  1. the Calculated Field Set process can be started in many ways, e.g.:

    • by the user

    • from Calculation Flow logic

    • via REST API, e.g. by Integration Manager or other integration tool

  2. The system queries the filtered list of rows to be processed

  3. For each row, the system will do:

    1. the system puts into the logic context the following:

      • the content of data row under CurrentItem

      • the values of inputs provided in the Calculated Field Set setup under input[] binding variable

    2. the system executes the Calculated Field Set logic in standard execution

    3. the logic calculates the results and provides the results as outputs of the visible logic elements

    4. the system takes the values from visible logic elements and using the mapping, it puts the values back to the row

    5. the system saves the updated row back to the database

Found an issue in documentation? Write to us.

Â