Overview of Workflows

WFM Interactions consist of two items: a form and a flow component. Interactive forms are built using the Form Builder. A flow is a map of the form (interaction) path, determining where the form moves within the workplace. A workflow consists of actions and objects. Actions are generic processes that perform specified functions and determine the next actions that occur. Actions correspond to nodes, and objects correspond to the physical part of the interaction – for example, a particular Vacation Request form that is submitted by a user.

The WFM workflow process begins when an employee submits a form. Once the form has been submitted, the workflow manages the interaction request by routing the request from one workflow action to the next until the workflow process is complete, as defined when the workflow is created in the Workflow Editor. If the next node in the workflow is a process node, the node is submitted to a database table to be queued for processing. Depending on the node’s configuration, DBMS Jobs process the nodes according to the BO Run Job procedure that an administrator sets up.

Nodes can be configured to have delegates, alternates, timeouts, and can send different types of messages. Certain node features are customizable. See for detailed descriptions of the workflow nodes.