Task node
This type of node will be used in several cases:
  • a business rule needs to be run on the process instance data
  • a subprocess needs to be started
  • a subprocess needs to send data to the parent process
  • some data needs to be sent to the frontend applications

Configuring task nodes

One or more actions can be configured on a task node. These will be run in the configured ordered.
Multiple options are available for this type of action and can be configured via the FlowX Designer:
  1. 1.
    Name - used internally in order to differentiate between different actions on nodes in the process. We recommend defining an action naming standard to be able to easily find the process actions.
  2. 2.
    Order - if multiple actions are defined on the same node, their running order should be set using this option
  3. 3.
    Time Expression - it can be used if a delay is required on that action. The format used for this is ISO 8601 duration format (for example, a delay of 30s will be set up like PT30S )
  4. 4.
    Action type - defines the appropriate action type
  5. 5.
    Trigger type - (options are Automatic / Manual) - choose if this action should be triggered automatically (when the process flow reaches this step) or manually (triggered by the user); In most use cases, this will be set to automatic.
  6. 6.
    Required type - (options are Mandatory / Optional) - automatic actions can only be defined as mandatory. Manual actions can be defined as mandatory or optional.
  7. 7.
    Repeatable - should be checked if the action can be triggered multiple times

Business Rules

A business rule is a Task action that allows a script to run. For now Mvel syntax can be used. More details about a business rule configuration can be found here

Websocket send Action

Being an event driven platform FlowX uses web socket communication in order to push events from the frontend application. More details about a business rule configuration can be found here.

Upload file

Upload file action will be used to upload a file from the frontend application and send it via a kafka topic to the document management system. More details can be found here

Start Subprocess

In order to create reusability between business processes, as well as splitting complex processes into smaller, easier to maintain flows, the start subprocess business rule can be used to trigger the same sequence multiple times. More details about how to configure it can be found here.

Append params to Parent process

Used for copying data in the subprocess from its parent process. More details about configuration can be found here.
Last modified 6mo ago