...
(each incarnation of workflow only executed once,
Workflows run on top of pipelines, that is, workflow uses pipelines to be instantiated and triggered. We call the pipeline that instantiate a workflow the originating pipeline. Based on the relationship between the workflow and its originating pipeline, workflow can be categorized into non-repeatable workflows and repeatable workflows.
In TQL, each instance of a workflow (or process) can only be executed once. Repeatable workflows are represented as process streams where each process instance is a self-contained independent copy of the original workflow [definition] run with specific arguments.
...
These may look like a, b or c, but suspend on pipeline operation instead of event handler or waitFor. Conceptually it’s the same as waiting for a response after an HTTP request, only without actual request. RFID reader is an example. The process starts by itself (1, 2a) of by an external event (2b, 2c) and suspends on the pipeline operation. Once a “response” is received from the device, process continues to next wait or completion. (event originator is within the workflow itself, waiting for pipeline operation to happen, such as a message from a device coming, or from a remote system coming, it is a synchronous execution on the pipeline. not an event handler) timeout
| Expand | ||
|---|---|---|
| ||
Workflow instances run on top of pipelines, that is, they use pipelines to be instantiate, trigger or communicate. We call the pipeline that instantiate a workflow instance the originating pipeline. Based on the relationship between the workflow and its originating pipeline, workflow can be categorized into non-repeatable workflows and repeatable workflows. |