RSA Governance & Lifecycle Workflow Nodes: Start
Last Modified: 2026-10-21

Refer to the following page for a summary of all Workflow Nodes: RSA Governance & Lifecycle Workflow Nodes Summary.

 

Product Area: Workflows

Workflow Node: Start

Applies to Workflow Types: All (Requests, Reviews, Rules)

Time to apply: <5 minutes

Impact: Critical — every workflow requires exactly one Start Node. It initiates workflow execution and defines when and how subsequent nodes are triggered.

 

Purpose:

Start Node is the start delimiter for a workflow. It defines the entry point; the exact place where the workflow begins execution once triggered by an event such as a Create Request, Approval, or Fulfillment action.

Summary: 

The Start Node is the first and most essential node in any workflow. It marks where the workflow begins its execution. It ensures consistent workflow initialization and passes control to the next logical node (for example, Approvals, Decision, Activity, or Subprocess Node) in the process. If the Start Node is not configured properly, the workflow may not execute at all or may fail to pass variables correctly to subsequent nodes.

Usage:

All workflows must contain one and only one Start Node and it will Link to the first processing node (like Approvals Phase, Approval or Activity Node) 

General Notes/Benefits:

  • Defines the entry conditions and initiate workflow execution.
  • Node is easy to configure, mandatory for workflow initiation, and defines when and how the workflow starts.

Configuration:

Start nodes can be found under the Template Toolbar, in the Standard section on the left side panel. To add a new node to your workflow, click the desired node icon in the left panel, then double-click anywhere in the main workspace to place it.

Start Node Properties - General

The General panel for a Start Node contains a few core fields that define how the node is labeled and identified within the workflow:

  1. Name
    • This is the display name of the Start node.
    • In the image, it is set to “Start”.
    • This name appears on the workflow canvas and helps identify the node in the model.
    • It is recommended to keep the name simple and generic, since a process typically begins with only one Start node and its function is already implied.
  2. Alias
    • The alias is an alternative label for the node, also shown as “Start” in the image.
    • It is used internally or by scripts/queries that reference nodes by alias.