Page Comparison

Jira LegacyshowSummaryfalseserverJIRA (mqidentity.atlassian.net)serverId77fb3325-4051-36d9-bcc7-761f62050707keyDOCS-36 

...

Examples of non-repeatable workflows are often used in AppFacets.

placeholder for example of non-repeatable workflow

...

Instances of such workflow are started right after they are created. This is done by ensuring that all the input values of the workflow's initial task(s) have their values assigned in your source code (versus waiting for external events to give value). They are only useful if they are doing something  or communicating with some other entities [en-masse] which is difficult with non-repeatable workflows.

Placeholder for example of non-waiting workflow

...

These are workflows which have explicit “event handler”. Instances of these workflows wait for the external event to come and then start ("external" here means external to the workflow itself). The "event handler" is written as "Event" in the workflow definition. In ThingFacet (and AppFacet) workflows, the Event is typically the ActionArgument, which is triggered by the modification of actionable attributes of the model facet.

Placeholder for example of externally-activated workflows.

...

These have an invoke with the WaitFor modifier. Instances of such workflows can start, work for a while and then suspend and wait for an event in the middle of task (on the waitFor). Once wait is completed they continue until the next WaitFor or process completion (The "external" here means external to the workflow itself).

Placeholder for example of externally-continued workflow

...