Autom Mate Team · Practical example
Some requests can proceed automatically; others need approval or a person to finish a task. Build that waiting point into the service so the continuation is clear.
For example, an access request may need a team lead’s decision before provisioning starts.
- Identify the exact decision and the person or system responsible for providing it. Keep the approval question specific.
- In the relevant Work Item, add Pause for resume. Put preparation actions inside Before Wait.
- Put the actions that depend on that decision inside After Resume. Actions below the pause on the normal path will not continue after resumption.
- Connect the approval response through the supported resume request to the same service. Validate the recorded decision and use the token issued for that waiting action. Only the approved branch should provision access; handle rejection separately.
- Run a development test, inspect the waiting Case, submit one continuation and check the After Resume logs.
Simple test: assign “prepared” before the wait and “resumed” after it. Verify that the second value appears only after continuation.
Dublin 6.0 resume tokens are single-use and have no automatic expiry. Plan reminders or escalation separately.
Where does your service currently lose visibility while waiting for a person?