The User Action activity node

You can use the User Action node to send work to a user's Inbasket. This is one of the most commonly used nodes.

For example, you need to verify whether staff members want to change their benefits packages for the coming year. Rather than send an email to all staff reminding that a deadline for changing their benefits is coming up, you want to force them to respond. You can create a process that would send an action item to users' Inbaskets. In this action item, users are required to respond Yes or No to the benefits change.

In this simple example, a Yes or No response is all that is needed. For more complex cases, the User Action node allows for great flexibility in how users respond to items in their Inbaskets. You can design a customized action with a customized view or send users to a Lawson form or to an internal or external URL.

Note: 

  • If the Trigger node encounters the User Action node in the triggered workunit, the Trigger node will continue with the flow even if the node triggers the workunit synchronously.

  • The User Action node cannot be used inside the loop of an iterative node such as the SQL Query node and the Data Iterator node.

  • Only variables that are defined on the Start node will persist after the User Action node is executed.

    See "Persistent and non-persistent variables" in What is a variable?.

The Properties tab of the User Action activity node has several tabs and some these tabs have multiple sections.