Connection lines
All nodes in a workflow process can participate in a connection with another node. You can draw positive and negative connections between nodes.
- Positive connections
- A solid black line on the canvas represents a positive connection.
A positive connection indicates a positive outcome. For example, an
action was performed, a record was approved, or a record met the condition
specified by the node. Use the Positive Connection toolbar button
to draw a positive line between nodes.
- Negative connections
- A dashed red line on the canvas represents a negative connection.
A negative connection indicates a negative outcome. For example, a
record was canceled, a record was rejected, or a record did not meet
the condition specified by the node. Use the Negative Connection toolbar
button
to draw a negative line between nodes.
Positive and negative connection buttons are 'sticky', meaning that you can continue to connect nodes together, until you click a different toolbar button.
Connection lines can also have actions associated with
them, and the new Action application enhancements allow the
user to associate an icon (.jpg or .gif) with an action (see Working
with Actions topic). Another feature of the Workflow Designer (Advanced)
application is the addition of an icon on the connector that has an
action associated with it. If the action has an icon defined, the
icon will be displayed on the line. If no icon has been defined for
the action, a default icon will be
displayed on the line.
Flyover help showing properties information about the actions defined on the connector is also available. This information includes the Action name, type, description, and value.
Sticky mode works for connection lines only; it does not work for nodes. When you click a connector, you can continue to connect nodes without re-clicking the connector toolbar button. It remains 'sticky', or active, until you click any other button on the toolbar.
Types of nodes and guidelines for connection lines
The following table describes the types of nodes and lists the guidelines for the connection lines that you can draw between one node and another node:
Node | Description | Lines permitted entering a node | Lines permitted or required exiting a node |
---|---|---|---|
Start node ![]() |
Indicates the point when a record starts a workflow process. When you create a process, a single start node displays on the canvas. Each process can have only one start node. You cannot delete start nodes. | None. | One positive line is required. |
Condition node ![]() |
Indicates an evaluation of the record, based on data in the record. Use a condition node to enable a true evaluation or a false evaluation of the record, and then direct the record based on that evaluation. When a condition node is generated, it evaluates the record based on the Structured Query Language (SQL) statement defined in the properties for the node. The record is then routed to either the positive connection line or to the negative connection line exiting the node. | One or more positive lines; one or more negative lines. | One positive line and one negative line are required. |
Interaction node ![]() |
Provides an option for a user interaction with a record. Use interaction nodes to guide a user through a structured interaction with a record. A process can have one or more interaction nodes. You do not have to include interaction nodes in a process. A manual input node precedes an interaction node. If an interaction node leads to an application not related to the object on the process record, place a stop node after the interaction node. The original process shuts down as the new record displays. | One or more positive lines; one or more negative lines. | One positive line is permitted. |
Manual input node ![]() |
Indicates a need for user input because there are multiple directions that a record can take in a process. Use a manual input node to have the assignee decide what happens next. When a manual input node is generated, the manual input window displays a menu of options for routing the record. When the assignee selects an option, any actions or notifications associated with the option are triggered. | One or more positive lines; one or more negative lines. | More than one positive line is required. Negative connections exiting the node are not allowed. |
Subprocess node ![]() |
Indicates that a separate workflow process is contained within another workflow process. Use a subprocess node to break down a complicated business process into smaller, self-contained units. For example, you could have a subprocess that handles records in different sites, or that handles different classes of work orders. When the record encounters a stop node within a subprocess, the stop node is returned to the main process at the same point where it left the process and on the same type of routing line on which it finished. | One or more positive lines; one or more negative lines. | One positive line and one negative line are required. |
Task node ![]() |
Indicates when a user is to be given an Inbox assignment. The user has two choices. For example, the user can either approve a record or reject a record. Use task nodes when your business process requires that a user evaluate a record. Create a task assignment that routes the record to one or more individuals. The workflow comes to a stop at a task node until the assigned user has routed the record. | One or more positive lines; one or more negative lines. | One positive line is required; one negative line is allowed. |
Wait node ![]() |
Indicates that the progress of a record through a process pauses until a required condition is met. Use a wait node to create a reaction to a database event, such as a status change, or a record update. A process can have one or more wait nodes. You do not need to include wait nodes in a process. A wait node cannot precede a node that requires user interaction, such as an interaction node or a manual input node. | One or more positive lines; one or more negative lines. | One positive line is required. |
Stop node ![]() |
Marks the end of a workflow process. That is, the point where a record leaves control of the process. When you create a process, a single stop node is placed on the canvas. Use the stop node tool in the palette to place additional stop nodes on the canvas. Workflow processes can have multiple stop nodes. Simply delete or add stop nodes as needed. | One or more positive lines; one or more negative lines. | None. |
Stop Warning node ![]() |
Marks the end of a workflow process that ends with warnings. Workflow processes can have multiple stop nodes. Simply delete or add stop nodes as needed. | One or more positive lines; one or more negative lines. | None. |
Stop Error node ![]() |
Marks the end of a workflow process that ends with errors. Workflow processes can have multiple stop nodes. Simply delete or add stop nodes as needed. | One or more positive lines; one or more negative lines. | None. |