See the process in your data and generate workflows in Duaer

What process Duaer reads

Every case, a sample, an order or an expense claim, goes through a few steps, each at a time. Duaer reads those steps from your data and writes them into the project’s built-in Duaer activities (one row per step) and Duaer cases (one row per case, with the step it is in now and since when).

From that record Duaer can tell how most cases go, where they wait longest, where they branch and who did each step, without changing your business systems first.

Five steps from data to workflow

1. Add a process source: open your project › Data tables › Duaer cases, select Process sources, then Add source. It can be a CSV or XLSX file, a database, a Feishu Base or Feishu approvals. Refer to Add a process source.
2. Read the process findings: every day Duaer finds the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule. Refer to Process findings and SOP conformance.
3. Compare with your SOP: choose the SOP in the knowledge base, Duaer reads its steps and shows how many cases follow it, which step they skip and which step runs over its limit.
4. Generate a workflow: under Workflows from process on the source, select Generate on the Watch, Coordinate or Execute workflow row. Refer to Watch, Coordinate and Execute workflows.
5. Replay, then publish: replay the version over the past 7, 14 or 30 days; a fit of 60% lets you publish it. Refer to Replay and publishing.

The three generated workflows

• Watch: when a case waits too long in a step, its owner gets a task card.
• Coordinate: when a case is at a step where cases branch, its owner gets a decision card whose options are the next steps cases really took; the choice is written back as the case’s next step.
• Execute: when a case waits too long, its owner is asked whether to start the next step now; on approval the workflow reaches a suggested action. The action is off until a person reviews it, connects it to their system and enables it.

All three are ordinary workflows: they start unpublished, carry the tag Generated from process and can be edited as usual. Cards appear in the Duaer employee portal and are written to the Duaer tasks table.

Who can do what

• Owners and admins: add and change sources, generate and regenerate workflows, run replays, and publish with a note when a replay falls short.
• Project members: see sources, findings, replay results and history, without changing them.
• Who sees the cases: in the source’s Schedule and audience step, list the people who see every case in the employee portal; owners and admins always do.

Owners and admins turn these features on and off under Settings › Features; one marked Not available to this organization has to be opened by the platform first. If Process sources is missing from your project, it is not on in your organization yet.