Watch, Coordinate and Execute: the workflows Duaer generates from a process

How to generate one

1. Open the process sources page. Under Workflows from process, each source lists the Watch, Coordinate and Execute workflows, each with one line on what it does.
2. Select one. Duaer creates the workflow in this project, unpublished, with the tag Generated from process, and opens it. Once generated, the row’s button becomes Open. Before the source has read data, or when the process has no step that keeps cases waiting too long or no step where cases branch, Generate is greyed out and the row says why; read the data first.
3. Each source gets one workflow of each kind. When the process has no step to watch or no step where cases branch, Duaer says so instead.

The Generated from process badge in the workflow header opens the evidence panel: which source and how many cases it came from, the figures behind each node, the nodes you removed, and the replay. On a phone the badge is an icon.

Watch: a reminder when a case waits too long

Duaer finds the steps where cases most often get stuck, up to five, with enough cases and a clear share over the limit. The limit is the larger of twice the median and the 85th percentile of how long past cases took, rounded up to whole days.

1. The daily check (08:00 by default) reads the cases in that step.
2. It keeps the cases over the limit that have an owner.
3. It skips cases that already have an open card, so a case gets one card per step.
4. It inserts a card into Duaer tasks for the case owner, such as “S-1042 · waiting in Received over 5 d”, saying how long cases usually take to move on.

Coordinate: ask the owner where cases branch

Duaer finds the steps where cases branch: left at least 20 times, for at least two next steps of 10% or more each. For example, after In production 73% went to QC passed and 27% to QC hold.

1. The daily check reads the cases in that step that have an owner and no open decision card, and hands each to its own run of the workflow.
2. Each case gets a decision card whose options are the next steps past cases really took (up to four), each with how many cases took it. Where cases with one attribute value (such as line 3) take one option 70% of the time or more, the card says so.
3. The workflow waits for the owner to choose in the employee portal, for up to 14 days.
4. It branches on the choice: records the step in Duaer activities (who chose, and when) and sets it as the case’s current step.

Each choice is recorded once, and re-reading the source keeps these decisions. The next findings pass counts them.

Execute: approve, then reach the suggested action

Execute uses the same steps Watch finds and suggests the step cases usually take next, for example Test started when a sample waits too long in Received.

1. The daily check reads the cases over the limit that have an owner and no open approval card, and runs each on its own.
2. The owner gets an approval card: “Test started now” or “Not now”. The workflow waits up to 7 days.
3. On approval it reaches the node “Test started · Received”: an HTTP Request placeholder that is disabled, has no credentials and an empty URL, with the note “Suggested — enable after review”.

To make it act: replace the node with the one that does this step in your system, or point the URL at it, connect credentials, then enable it. It must stay after the approval Wait or the workflow cannot be published; refer to Replay and publishing. Execute writes no step back: your system records the step when it really happens, and the next read brings it into the process.

Edit and regenerate

• Edit a generated workflow like any other: limits, schedule, card text, options, extra notifications. Every save is a new version, and a new version needs a new replay before publishing.
• When the process data changes, an owner or admin selects Regenerate in the evidence panel. An untouched workflow becomes a new version; an edited one gets a proposed update that keeps the nodes you edited and does not bring back the ones you removed, for you to Apply or Dismiss.
• Select Refine with assistant and the assistant reads the process and the workflow first, including its replay, then changes what you ask. It never publishes, replays or enables an action for you.