Skip to main content
BRYTER Academy

Let End Users Collaborate With Handover Actions

Updated

The Handover action node enables authors to build approval processes without the need for database involvement. This node lets the author specify the point in a module where a handover process should take place.

The Handover action then transfers the subsequent steps to another user for further processing. If needed, additional Handover actions can be added, e.g., to redirect tasks back to the initial end user for completion.

This is a licensed feature which can be enabled by your BRYTER contact person. For further information, please reach out to them or support@bryter.io. Additional pricing may apply.

 

Step-by-step guide to building approval processes

  1. Select Handover in the Actions menu to insert a Handover action. Configure the node.
    The Handover action combines an input node and an action node. The top half (input) is presented to the current end user as their final screen, while the bottom half (action) notifies the end user taking over via email. When filling in the information, ensure that you address end users appropriately. The link for the handover process is automatically added to the handover email.
  2. Insert an input or Result node following a Handover action. This screen will be seen by the end user taking over.
  3. Repeat the process as needed to hand over tasks to different departments or even back to the initial end user.
  4. Remember to publish your module because the Handover action requires a published environment to function correctly.
If a module has changed since a handover was initiated, the end user might encounter errors when trying to resume the session. So, it is best not to publish a new module version while your end users are in the middle of handover processes.
We recommend that you provide a brief explanation of the process to the respective party in the CONTENT fields of the node. For example, if the initial end user is waiting for approval from the legal department, inform them that they will receive an email after the legal department responds. Similarly, let the legal department know to follow the link in the email to respond to the end user's request.

 

Occasionally asked questions

Why do I see the error This session could not be handed over when opening a handover link?

When you reopen a saved session or follow a handover link, the BRYTER engine loads the latest published version of the module and replays the previous inputs from the start node.

This replay continues until the engine reaches a node where it can no longer determine an answer. This may happen if:

  • A required input was not previously given,
  • A new node was added along the original path to the handover node,
  • A transition condition was changed and now depends on new variables that weren’t part of the original session.

For handover links, the engine must be able to reach and end in the handover node (or a following node, before any additional handover).

If the replay cannot reach that point, e. g., due to module changes or missing data, the session cannot resume, and you’ll see the error: This session could not be handed over. This is expected behavior when the module version has changed in a way that affects the original session path.

If you need support troubleshooting a handover session, feel free to contact us at support@bryter.io.

Was this article helpful?

0 out of 0 found this helpful
Return to top

Related articles