This node represents an interaction with the user. It is used to display a piece of UI (defined in the UI Designer or a custom Angular component. You can also define actions available for the users to interact with the process.
User task nodes allow you to define and configure UI templates and possible actions for a certain template config node (ex: button components).
canGoBack
false, all steps found behind it will become unavailable.When encountering a step with canGoBack
switched to false, all steps found behind it will become unavailable.
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.
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.
To access the UI Designer, follow the next steps:
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:
Root components
These elements are used to group different types of components, each having a different purpose:
More details in the following section:
UI components
The root component can hold a hierarchical component structure.
Available children for Card and Container are:
More details in the following section:
Form elements
This type of elements are used to allow the user to input data, and can be added only in a Form Component. They have have multiple properties that can be managed.
More details in the following section:
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:
This node represents an interaction with the user. It is used to display a piece of UI (defined in the UI Designer or a custom Angular component. You can also define actions available for the users to interact with the process.
User task nodes allow you to define and configure UI templates and possible actions for a certain template config node (ex: button components).
canGoBack
false, all steps found behind it will become unavailable.When encountering a step with canGoBack
switched to false, all steps found behind it will become unavailable.
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.
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.
To access the UI Designer, follow the next steps:
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:
Root components
These elements are used to group different types of components, each having a different purpose:
More details in the following section:
UI components
The root component can hold a hierarchical component structure.
Available children for Card and Container are:
More details in the following section:
Form elements
This type of elements are used to allow the user to input data, and can be added only in a Form Component. They have have multiple properties that can be managed.
More details in the following section:
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: