Contents
1. Before You Start
2. Create the Workflow
3. Conditions on Answers
4. Actions that Use Answers
5. How It Works
6. Frequently Asked Questions
1. Before You Start
You will need: an active Screen Flow on the module and administrator access to Settings → Workflows.
Access requirements: same as any workflow. The workflow runs as the system administrator user, like every workflow.
2. Create the Workflow
Navigate to Settings → Workflows → New Workflow, name it and choose the module the flow belongs to. Under Trigger Workflow On select Screen Flow submitted and pick the flow.
Field | Description |
Target Module | The module of the flow; the picker only lists that module's active flows. |
Screen Flow | The flow whose Save & Close starts this workflow. |
Conditions | Optional: the record's fields and the flow's answers. |
Actions | Any workflow action. |
The workflow list shows the trigger as On (Module) screen flow submitted.
3. Conditions on Answers
In the condition builder the field list gains a group Screen Flow answers: (flow name) with one entry per field. Every entry is named Field label (Screen Flow - flow name - step name) - the step's own title, or Step n if it has none - here and in every action's field or token list, so the same label used on two flows, or on two steps, is always told apart. Renaming a step in the builder renames these entries too. Combine them freely with the record's own fields, for example Admission Type is Refer Out and Last Name contains Smith.
Tip: a field that was hidden for the agent (by a rule or by the record's version) arrives with its default value - usually empty. Use "is not empty" when an action should only run for fields that were actually shown.
4. Actions that Use Answers
Action | How answers are used |
Update Fields | Choose a field of the record and, as the value, pick a Screen Flow answer ("copy from field") or write an expression with the answer, e.g. concat(screenflow_text, ' / ', screenflow_picklist) . |
Create Record | Same picker when mapping the new record's fields. |
Send Email / Send SMS / Log Comment | Insert answer tokens from the token picker; two extra tokens give the flow's name and the record's version. |
Dates, numbers, picklists, multipicklists and checkboxes are written in the target field's own format.
5. How It Works
1. The agent clicks Save & Close; the CRM checks the answers.
2. The record is read fresh and the answers are attached to it for this run only.
3. Every active workflow with the trigger "Screen Flow submitted" for that flow is evaluated: conditions first, then the actions in order.
4. Ordinary "record saved" workflows may run afterwards if an action changed the record.
Answers are not stored. Actions delayed by minutes or business hours run later and no longer see the answers - keep answer-dependent actions immediate.
6. Frequently Asked Questions
Q: The workflow did not run. Check it is Active, targets the right flow, and that its conditions are met by the answers given. A field hidden from the agent counts as empty.
Q: Can I use the answers in a scheduled (Time Interval) workflow? No. Answers exist only at submission time.
Q: Can one flow have several workflows? Yes; each runs independently, in sequence order.
Q: What if the flow is deleted? The workflow keeps its trigger but nothing can submit that flow any more; retarget or delete the workflow.
Need Help?
1. Open the workflow and confirm the trigger, the flow and the conditions.
2. Run the flow once on a test record and check the record's Updates / related lists. 3. Contact Dazos support with the workflow name and reference CRM-3865.