​
Configuring a user task node

User Task Node
User task nodes allow you to define and configure UI templates and possible actions for a certain template config node (ex: button components).

​
General Config

  • Node name - the name of the node
  • Can go back - setting this to true will allow users to return to this step after completing it. When encountering a step with canGoBack false, all steps found behind it will become unavailable.
  • Flow Names - leave this field empty if the node should be included in all flows
When encountering a step with canGoBack switched to false, all steps found behind it will become unavailable.
  • Swimlane - choose a swimlane (if there are multiple swimlanes on the process) to make sure only certain user roles have access only for certain process nodes- if there are no multiple swimlanes, the value is Default
  • Stage - assign a stage to the node

​
Response Timeout

  • Response timeout - can be triggered if, for example, a topic that you define and add in the Data stream topics tab does not respect the pattern, the format used for this is ISO 8601 duration format (for example, a delay of 30s will be set up like PT30S)

​
Data stream topics

  • Topic Name - the topic name where the process engine listens for the response (this should be added to the platform and match the topic naming rule for the engine to listen to it) - available for UPDATES topics (Kafka receive events)
A naming pattern must be defined on the process engine configuration to use the defined topics. It is important to know that all the events that start with a configured pattern will be consumed by the Engine. For example, KAFKA_TOPIC_PATTERN is the topic name pattern where the Engine listens for incoming Kafka events.
  • Key Name - will hold the result received from the external system, if the key already exists in the process values, it will be overwritten

​
Task Management

  • Update task management - force Task Management plugin to update information about this process after this node

​
Configuring the UI

The FlowX Designer includes an intuitive UI Designer (drag-and-drop editor) for creating diverse UI templates. You can use various elements from basic buttons, indicators, and forms, but also predefined collections or prototypes.

​
Accessing the UI Designer

To access the UI Designer, follow the next steps:
  1. Open FLOWX Designer and from the Processes tab select Definitions.
  2. Select a process from the process definitions list.
  3. Click the Edit process button.
  4. Select a user task node from the Pro dcess Designer then click the brush icon to open the UI Designer.

Creating a user interface

​
Predefined components

UI can be defined using the available components provided by FLOWX, using the UI Designer available at node level. Predefined components can be split in 3 categories:

​
Custom components

These are components developed in the web application and referenced here by component identifier. This will dictate where the component is displayed in the component hierarchy and what actions are available for the component. To add a custom component in the template config tree, we need to know its unique identifier and the data it should receive from the process model. More details in the following section:

Custom

 The sections that can be configured are as follows:
  1. Message - configure what data will be pushed to the frontend application
  2. Input keys - used to define the process model paths from which the components will receive its data
  3. UI Actions - actions defined here will be made available to the custom component. Multiple actions can be configured on a custom component and mapped to different triggers when developing it. Naming each action suggestively is important so the frontend engineer developing the component knows what actions should be triggered by certain events.
More information about configuration, [here](using ui designer).

​
Displaying a UI element

When a process instance is started the web application will receive all the UI elements that can be displayed in that process. When the process instance token will reach a User Task, a web socket message will be sent informing the SDK to display the UI element associated with that user task Example:
  1. Start a process: POST {{processUrl}}/api/internal/process/DemoProcess/start
The provided instruction involves initiating a process by making a POST request to the specified URL ({{processUrl}}/api/internal/process/DemoProcess/start). This API call triggers the start of a process named “DemoProcess” by sending relevant data to the server.
{
"processDefinitionName" : "DemoProcess",
  "tokens" : [ {
    "id" : 759224,
    "startNodeId" : null,
    "currentNodeId" : 662807,
    "currentNodeName" : null,
    "state" : "ACTIVE",
    "statusCurrentNode" : "ARRIVED",
    "dateUpdated" : "2023-05-31T09:44:39.969634Z",
    "uuid" : "d310996d-f3b9-44e5-983d-3631c844409e"
  } ],
  "state" : "STARTED",
  "templateConfig" : [ {
    "id" : 630831,
    "flowxUuid" : "80ea0a85-2b0b-442a-a123-2480c7aa2dce",
    "nodeDefinitionId" : 662856,
    "componentIdentifier" : "CONTAINER",
    "type" : "FLOWX",
    "order" : 1,
    "canGoBack" : true,
    "displayOptions" : {
      "flowxProps" : { },
      "style" : null,
      "flexLayout" : {
        "fxLayoutGap" : 0,
        "fxLayoutAlign" : "start stretch",
        "fxLayout" : "column"
      },
      "className" : null,
      "platform" : "DEFAULT"
    },
    "templateConfig" : [ {
      "id" : 630832,
      "flowxUuid" : "38e2c164-f8cd-4f6e-93c8-39b7cdd734cf",
      "nodeDefinitionId" : 662856,
      "uiTemplateParentId" : 630831,
      "componentIdentifier" : "TEXT",
      "type" : "FLOWX",
      "order" : 0,
      "key" : "",
      "canGoBack" : true,
      "displayOptions" : {
        "flowxProps" : {
          "text" : "Demo text"
        },
        "style" : null,
        "flexLayout" : null,
        "className" : null,
        "platform" : "DEFAULT"
      },
      "expressions" : {
        "hide" : ""
      },
      "templateConfig" : [ ],
      "dataSource" : {
        "processData" : {
          "parentFlowxUuid" : null
        },
        "nomenclator" : {
          "parentFlowxUuid" : null
        }
      }
    } ]
  } ],
  "uuid" : "44177340-5ac6-4591-89ad-04df0815fbd0",
  "generalData" : null,
  "backCounter" : 0,
  "startedByActionId" : null,
  "subProcesses" : null,
  "subprocessesUuids" : null,
  "baseUrl" : null
}
  1. ProgressUpdateDto will trigger the SDK to search for the UI element having the same nodeId with the one in the SSE event.
  2. Additionally, it will ask for data and actions that are required for this component via a GET request {{processUrl}}/api/process/db573705-71dd-4216-9d94-5ba2fb36ff2a/data/42062 
...
nodeDefinitionId" : 662856,
      "processDefinitionId" : 662952,
      "actionParams" : [ {
        "id" : 759458,
        "key" : "headers",
        "value" : "{\"processInstanceId\": ${processInstanceId}}",
        "replaceValues" : true,
        "actionDefinitionId" : 759403
      }, {
        "id" : 759457,
        "key" : "customId",
        "value" : "folder",
        "replaceValues" : true,
        "actionDefinitionId" : 759403
      }, {
        "id" : 759456,
        "key" : "documentType",
        "value" : "document",
        "replaceValues" : false,
        "actionDefinitionId" : 759403
      }, {
        "id" : 759455,
        "key" : "topicName",
        "value" : "test.topic",
        "replaceValues" : false,
        "actionDefinitionId" : 759403
      } ],
      "actionRuleDefinitions" : [ ],
      "callbackActions" : null,
      "timerExpression" : "",
      "order" : 1,
      "manual" : false,
      "repeatable" : false,
      "optional" : false,
      "autoRunChildren" : false,
      "allowTokenReset" : false,
      "restartFromSnapshot" : false,
      "keysForRestart" : [ ],
      "keys" : [ ]
 ...