Entering the realm of FlowxX unlocks a spectrum of possibilities for elevating processes and workflows. From automation to data-driven decision-making, several straightforward approaches pave the way for leveraging this platform efficiently. Let’s delve into the ways to kickstart a process.
To trigger a process using a Kafka Send Action:
KAFKA_TOPIC_PROCESS_START_IN
environment variable from your process-engine deployment.For clarification on the topic, in FLOWX.AI Designer visit Platform status → Flowx Components → process-engine-mngt -> kafkaTopicHealthCheckIndicator → details → configuration → topic → process → start_in:
{"processInstanceId": ${processInstanceId}}
The headers section should resemble this structure:
To initiate a process using a Start Timer Event:
Starting a process through registered timers necessitates sending a process start message to Kafka, requiring a service account and authentication. For detailed guidance, refer to:
For deeper insights into the Start Timer Event, refer to the section below:
To initiate a process using a Message Catch Start Event, two processes are required. One utilizes a throw message event, while the other employs a start catch message event to initiate the process.
Message correlation is vital and achieved through message subscriptions, involving the message name (must be identical for both throw and catch events) and the correlation key (also known as the correlation value).
Now, we will configure the process that will be started with the start catch message event:
Once both processes are configured, commence the parent process. At runtime, you’ll notice the initiation of the second process:
Initiating processes through hooks involves the creation of a hook alongside two essential processes: one acts as the parent process, while the other is triggered by the hook.
Hooks play a crucial role in abstracting stateful logic from a component, facilitating independent testing and reusability.
Users granted task management permissions can utilize hooks to initiate specific process instances, such as triggering notifications upon event occurrences.
Follow the next steps to create a hook:
For further details about hooks, refer to the section below:
Establishing appropriate roles and permissions within the parent process (or the service account used) is mandatory to enable it to trigger another process.
Now proceed to configure the process that the hook will trigger.
To configure the process triggered by the hook, follow the initial three steps above. Ensure that the necessary roles and permissions are set within the process.
Upon running the parent process, instances will be created for both the parent and the child processes.
Entering the realm of FlowxX unlocks a spectrum of possibilities for elevating processes and workflows. From automation to data-driven decision-making, several straightforward approaches pave the way for leveraging this platform efficiently. Let’s delve into the ways to kickstart a process.
To trigger a process using a Kafka Send Action:
KAFKA_TOPIC_PROCESS_START_IN
environment variable from your process-engine deployment.For clarification on the topic, in FLOWX.AI Designer visit Platform status → Flowx Components → process-engine-mngt -> kafkaTopicHealthCheckIndicator → details → configuration → topic → process → start_in:
{"processInstanceId": ${processInstanceId}}
The headers section should resemble this structure:
To initiate a process using a Start Timer Event:
Starting a process through registered timers necessitates sending a process start message to Kafka, requiring a service account and authentication. For detailed guidance, refer to:
For deeper insights into the Start Timer Event, refer to the section below:
To initiate a process using a Message Catch Start Event, two processes are required. One utilizes a throw message event, while the other employs a start catch message event to initiate the process.
Message correlation is vital and achieved through message subscriptions, involving the message name (must be identical for both throw and catch events) and the correlation key (also known as the correlation value).
Now, we will configure the process that will be started with the start catch message event:
Once both processes are configured, commence the parent process. At runtime, you’ll notice the initiation of the second process:
Initiating processes through hooks involves the creation of a hook alongside two essential processes: one acts as the parent process, while the other is triggered by the hook.
Hooks play a crucial role in abstracting stateful logic from a component, facilitating independent testing and reusability.
Users granted task management permissions can utilize hooks to initiate specific process instances, such as triggering notifications upon event occurrences.
Follow the next steps to create a hook:
For further details about hooks, refer to the section below:
Establishing appropriate roles and permissions within the parent process (or the service account used) is mandatory to enable it to trigger another process.
Now proceed to configure the process that the hook will trigger.
To configure the process triggered by the hook, follow the initial three steps above. Ensure that the necessary roles and permissions are set within the process.
Upon running the parent process, instances will be created for both the parent and the child processes.