Suspend

Prepare to resume your flow

Suspend: Save state and prepare to resume

resumeStartOver

This building block will save the current state of your flow. You can then resume the flow later on. So this building block only makes sense if you have resume blocks in your flow.

The suspend block will save all variables and will create a links for each resume block. You can then use these links in your templates to continue the execution at the matching resume block once the user clicks on the link.

Use cases

  • Approval flows with dedicated approve and deny link
  • Send email with an attached document for signing

Configuration

No configuration required

 Reload

Click on the reload button if you have added or removed resume blocks to your flow. The suspend block will then update the resume links for each of the resume block that have been found.

Useful combinations

Purchase Order Approval (simplified)

This example shows a simplified version of the Purchase Order App. This App demonstrates how to create an approval flow. Depending on the user actions different parts of the flow are executed and distinct outputs created.

The email that will be sent to the manager contains two action buttons to approve or deny the request. He will also find a link to create a PDF document containing all approved orders.

Initially a new order request is received. A form is used to collect the input and to store it in a purchase order sheet.

Once the inquiry for a new item is received the flow is suspended and an approval request is sent to the respective manager. Up until the manager responds the flow is stopped.

As the flow contains two different Resume building block the Suspend building block creates a dedicated link for each of these entry points.

These links can then be used in the outgoing email to create links or buttons resume the flow at the related position.

Load PO Request

FORM
requesterName
requesterEmail
managerName
managerEmail
item

Suspend and prepare resume

resumeApprove
resumeOrder

Send approval request to ${managerEmail}

managerName
APPROVAL EMAIL
requesterName
item
resumeApprove
resumeOrder

Stop execution

In case the manager clicks on either the approve or denied button the flow is resumed at the "Resume approval" building block.

Resume: Approve

button
button

Skip 3 blocks if 'next' == 'Approve'

button

The value of the button variable will either be Approve or Deny . In case the request has been denied the subsequent blocks will be executed (sending a denial email to the requester).

The flow stops once the email is sent and a denial confirmation document is displayed to the manager.

Update PO

approved
PO item update

Send denied email to ${requesterEmail}

requesterName
DENIED EMAIL
item

Stop and display denied doc

DENIED TEMPLATE

End of skipped blocks

Resuming at the "Resume approval" building block with an approved request the skipping condition is true, the referring building blocks are skipped and no denial but a confirmation email is sent. Once the confirmation is sent the manager is redirected to a web-page (e.g. a worklist overview).

Update PO

approved
PO item update

Send approved email

requesterName
ACCEPTED EMAIL
item

Stop and redirect to worklist

www.yourworklist.com

Resume: Order

resumeUrlOrder

Load PO sheet

PO worksheet
fileId

Generate Order PDF by order template

fileId
orderPdf

Upload Order PDF

orderPdf

Once a number of orders are approved, the manage may decide to create a PDF containing all the approved orders. In order to start the order creation the second link within the approval email is selected. The flow is then resumed and the "Resume Order creation" building block and the order creation steps of the flow are executed.

Copy App

Learn more

The suspend block does not stop the execution. This will allow you to use the generated links in subsequent template building blocks or in your emails. Use the stop block after sending out the links if you want to stop the execution.

Questions and Feedback

If you have any comments on this page, feel free to add suggestions right to the Google document that we are using to create this site.

If you are not yet member of the Ultradox community on Google+, please join now to get updates from our end or to provide feedback, bug reports or discuss with other users.

Last Updated: 30.11.18