Configuring Start Node in Inbound Workflows

A start node is the starting point of a workflow and no workflow can be created without a start node. An inbound workflow can have two types of start points - Alias and Workflow. All emails coming to an alias, specified as the starting point of an inbound workflow, are routed by that workflow. More than one alias can be added as the start point of a workflow, but one alias can be a start point of only one inbound workflow. After saving a workflow, if the workflow is added as an end node in another workflow, then the second workflow becomes the start point of the first workflow. This means, that the activities routed by the second workflow are processed by the first workflow. An inbound workflow can have both aliases and workflows as the start point.

A workflow can have only one start node.

To configure the start node in an inbound workflow:

  1. From the Partition and Departments dropdown menu, select a department.

  2. From the Navigation menu, browse to Business Rules > Workflow > Inbound.

  3. On the List page, select an inbound workflow or create a new one.

  4. On the Properties page, on the Diagram tab, add the Start node in the Workflow Editor.

  5. In the Add Start Node window, in the Start Points tab, select the email alias to be set as the start point for this workflow. All emails coming to the selected alias are routed by this inbound workflow. You can add more than one aliases as the start point of a workflow, but one alias can be a start point of only one inbound workflow.

The department’s secure message center also appears as a valid start point for the inbound workflow. This allows messages sent through secure messaging to be sent to queues and handled much like standard emails. For more information about secure message centers, see Secure Message Center.

The Workflows tab is enabled only after a workflow is saved. After saving the workflow, if you add the workflow as an end node in another workflow, then that workflow is listed in the Workflows tab. This means, that the activities routed by the other workflow are processed by this workflow. An inbound workflow can have both aliases and workflows as the start point.

inbound

  1. Click the Done button to close the window.

Related Topics