Terminate
How-to4 minPractitioner
Before you start
A Terminate step ends the workflow right there, with the response and message you choose. It suits a workflow that checks rules before a save, and refuses the save with a clear reason.
When should I use Terminate?
Section titled “When should I use Terminate?”Put it at the end of a Decision path that should not continue. For example, if a contract has no end date, stop and tell the user. A Terminate ends its path.
Add a Terminate
Section titled “Add a Terminate”- Click + on the path that should stop and choose Terminate. It sits in the Logic group.
- Under End the workflow as, choose Success, Warning or Failed.
- Under Message, write what the person should read. Use Insert data to include a value.
End the workflow as decides how the run is treated.
Message is what the person reads.
What do the endings mean?
Section titled “What do the endings mean?”| Ending | What happens |
|---|---|
| Success | Stops here. Everything above stands |
| Warning | Stops and shows the message as a warning |
| Failed | Stops, marks the run as failed and, before a save, blocks the save |
The Message is a Smart Script: plain text works, and you can add values from fields.
Worked example: refuse a contract without an end date
Section titled “Worked example: refuse a contract without an end date”Omar’s contract workflow runs before the save. A Decision checks Contract end date is empty. On Yes, a Terminate set to Failed shows: “Add an end date before saving this contract.” The record is not saved until someone fills it in.
What should I watch for?
Section titled “What should I watch for?”- It ends the whole workflow, even inside a loop or on one path of a Decision.
- In a workflow that runs before the save, this message is what the person saving sees.