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

Product Area: Workflows

Workflow Node: Run Report

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

Time to apply: <10 minutes

Impact: High positive impact for reporting, visibility, and audit requirements. Low risk to workflow execution, as the node only runs an existing report definition.

Purpose:

Run Report node is used to execute a predefined report as part of a workflow. The Run Report Node triggers an existing report definition and generates report output when the workflow reaches this node.

Summary:

The Run Report Node enables workflows to automatically execute predefined reports. Instead of manually running reports, this node ensures reports are generated at the correct stage of the workflow.

When executed, the node runs the selected report and generates the corresponding report output, which can be used for auditing, tracking, validation, or downstream processing.

Key use:

To automatically trigger predefined reports (for example, User Access, Account, Group, or Role reports) during workflow execution and ensure report results are generated at the appropriate stage of the process.

Usage:

• Trigger reports as part of governance or compliance workflows
• Automate report generation instead of manual execution
• Ensure consistent and timely reporting across workflows

General Notes/Benefits:

• Automates execution of existing reports
• Improves auditability and operational visibility
• Reduces manual reporting effort
• Ensures consistent report generation
• Supports compliance and governance tracking

Configuration:

The Run Report node can be found under the Template Toolbar, about halfway down under the Common section. To add a new node to your workflow, single-click the desired node icon in the left panel, then double-click anywhere in the main workspace to place it.

Run Report Node Properties

General Section

The General panel defines how the Run Report node is identified and documented within the workflow.

1. 1. Name
      • This is the display name of the Run Report node on the workflow canvas.
      • Keep the name generic (for example, Run Report).
      • Variables cannot be used in the node name.
      • Detailed or dynamic information should be configured using Status options.
   2. Description
      • Used to document which report is being executed.
      • Helpful for future reference, maintenance, and troubleshooting.
      • Recommended to include the report purpose or type (for example, Monthly User Access Report).
   3. Enabled
      • The node can be enabled or disabled as required. If the node is disabled, it visually turns light blue in the diagram; however, the node will still be executed.

Status Section

The Status section contains the following status messages:

• • Planned (Possible)
  • Planned (Definite)
  • Completed

1. 1. Planned (Possible)
      • Displays a message before the workflow reaches the node.
      • Can indicate a potential upcoming report execution.
   2. Planned (Definite)
      • Displays a message before the workflow reaches the node.
      • Indicates an expected upcoming report execution as part of the workflow path.
   3. Completed

1. 1. • Displays a message only after the report has successfully executed.
      • Confirms that report output has been generated.

Recommendation:

• • • Leave both Planned options (Possible and Definite) empty and populate only the Completed status message to ensure business users see only confirmed workflow actions and to avoid confusion.

• • • • The Planned (Possible) message is displayed even though the workflow has not yet transitioned through the node. This provides information about a potential upcoming next step in the process.

• • • • Completed populates the message only after the workflow has successfully transitioned through and past the node.

Definition Section

• • • Select an existing Report definition to be executed.
    • This selection determines which report runs when the workflow transitions through this node.

Self-Looping Panel Section

The Run Report node supports a self-looping transition, which allows the workflow to loop back to the same node and re-execute the report if required.

By default, the self-loop transition should be kept Unconditional. This ensures normal execution of the Run Report node without introducing unnecessary looping behavior.

If re-execution of the report is required, the self-loop transition must be explicitly configured using one of the following types:

• • • Conditional: The workflow loops back to the Run Report node only when the defined condition evaluates to TRUE (for example, when a report needs to be regenerated or validated).
    • Completion Code: The workflow loops back based on a specific completion code returned by the Run Report node execution.