Tasks filed by workflows
How an automated Rhazes workflow files follow-up tasks linked back to the run and the patient, so nothing it found is lost.
Updated
What gets filed
A workflow that finishes with a Create tasks step files one task per item it found. A results sweep that finds four outstanding results files four tasks, not a summary you then have to act on by hand.
They are traceable
A filed task is linked back to the workflow that created it, the run it came from, and the patient it concerns.
That link is what makes automated tasks trustworthy. A task appearing on your list without explanation is noise; one you can open and trace to the run that produced it is evidence.
They are ordinary tasks
Once filed, they behave like any other task. Complete them, re-date them, move them onto a list, or delete them. There is no separate automated-task inbox to check.
They outlive the workflow
Deleting a workflow does not remove the tasks it filed. The follow-up still needs doing whether or not the workflow that spotted it still exists. See Deleting a workflow.
Setting it up
Due dates and the list they land on are configured on the workflow, not here. See Filing tasks from a workflow.