Preview the starting condition, message text, recipients, and dates. A test result should be checked before the workflow is turned on.
Why this matters
A workflow repeats work for the right event at the right time. Rae can prepare a complete draft quickly; your team then checks every starting condition, recipient, message, and task before publishing.
Before you start
Know the event or lead condition that should start the workflow and who should receive each action.
In Releventful
In the workflow draft, click Save draft, then Review saved draft and Try the client portal.
Use a sample event to inspect the message, task, document, recipient and due date; click the wrong timeline item to edit it.
Click Save draft again, repeat the preview, then Review event impact before publishing.
How to make the most of this step
Save the current draft before using Try the client portal. Walk through the sample event as a client would: check the timing, visible tasks, documents, and messages. Return to the draft to correct anything wrong. The preview does not send a real message; publishing an enabled step can.
A useful decision
Before completing this task, compare the change with a sample record of the same kind. This confirms that the client, employee, amount, or timing affected is the one you intended.
Check the result
Preview a matching example and monitor the first live run. Confirm any message reached the intended person.
Important to know
A saved draft is not live. New items begin off for review. A published workflow can send real messages or create tasks when its conditions are met; existing events require their own impact review.