Following types of workflows supported
| Jira Legacy | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Stream workflow, deploying pipeline, triggering pipeline (in repeatable workflows, they are often differently from deploying pipelines)
(each incarnation of workflow only executed once,
In TQL, each instance of a workflow (or process) can only be executed once. Repeatable workflows . However, in many circumstances, you may want a workflow to be executed multiple times, for instance, the process to update an attribute value may needs to be repeated every time a sensor event comes in. Such "repeatable workflows" are represented as process streams where each process instance is a self-contained independent copy of the original workflow [definition] run running with specific arguments.
1. Non Non-repeatable (single run, non-stream) workflows (used in AppFacets)
Such workflow is Such workflows runs for a single time and never repeats. If you do not specify the "While" modifier for the first workflow task, a workflow will run only once. (By default a task's while = "false".) Non-repeatable workflows should be started immediately after compilation (i.e. after it is deployed) and executes synchronously (in relation to the originating pipeline). That is the pipeline will wait until workflow completes. This precludes such workflow from waiting on any events.
(initial task(s) should start without waiting) - recommended
example Broadcast to a number of http end points concurrently
If it is waiting for a value, the whole pipeline will be waitingwithout waiting for any events for it to activate or continue.
Examples of non-repeatable workflows are often used in AppFacets.
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
place holder for example of non-repeatable workflow |
2. Repeatable (multi-run, stream) workflows - usually used to process (sequence of) events
...
| Expand | |||||
|---|---|---|---|---|---|
| |||||
|