Lifecycle Builder
Control & DirectionThe Lifecycle Builder is a visual editor for designing the stage sequence within a lifecycle template. It provides a drag-and-drop interface for adding phases, configuring their behavior, and defining the order in which projects progress. Each stage maps to a recognized phase type and can carry custom configuration for approval gates, auto-advance rules, and workflow integration.
The Lifecycle Builder integrates with Lifecycle Templates (parent template), Default Approvers (phase-level approval rules), and the Workflow Engine (phase workflow automation).
Accessing the builder
From the Lifecycle Templates list, click the Build action on any template to open the builder page at /projects/lifecycle-templates/[id]/builder. The builder displays the template’s current stage sequence as a visual workflow with each stage represented as a node in the pipeline.
Standard phase types
Each stage in a lifecycle is assigned a phase type code that determines its role in the project lifecycle. The platform provides five standard phase types that cover the typical security project workflow.
| Phase Type | Description |
|---|---|
| Requirements | The initial phase where project requirements, scope, and objectives are defined and documented |
| Requirements Approved | A gate phase confirming that all requirements have been reviewed and formally approved before execution begins |
| Execution | The active delivery phase where the project work is carried out |
| Testing | The validation phase where deliverables are tested, verified, and assessed against the approved requirements |
| Closed | The terminal phase indicating the project is complete, with all deliverables accepted and documentation finalized |
Adding stages
Add a new stage
Click Add Stage in the builder to insert a new stage into the lifecycle. The stage is appended to the end of the sequence by default.
Configure the stage
For each stage, provide the following:
| Field | Description | Required |
|---|---|---|
| Name | A display name for the stage (e.g., “Security Review”, “Final Approval”) | Yes |
| Phase Type Code | The phase type that this stage represents (Requirements, Requirements Approved, Execution, Testing, or Closed) | Yes |
| Stage Order | The numeric position of this stage in the sequence; determines the progression order | Yes |
| Config | A JSON configuration object for advanced settings such as approval requirements, auto-advance rules, and notification triggers | No |
Reorder as needed
Drag stages to reorder them in the visual builder. The stage order values update automatically to reflect the new sequence.
Stage configuration
Each stage carries an optional config JSON object that controls its behavior. Configuration options include:
- Approval gates — define whether the stage requires formal approval before the project can transition to the next phase. Approval rules reference the settings in Default Approvers.
- Auto-advance — when enabled, the project automatically transitions to the next stage once all gate conditions are satisfied, without requiring a manual transition action.
- Notification triggers — configure notifications that fire when a project enters or exits the stage.
Phase workflow integration
Stages can be linked to the Workflow Engine through a phase workflow association. When a project enters a stage that has an associated workflow, the workflow instance is created and executed automatically. This allows you to automate actions such as sending review requests, creating tasks, or triggering external integrations when a project reaches a specific phase.
Phase transitions
When a project moves from one stage to the next, a phase transition record is created. Each transition captures:
| Field | Description |
|---|---|
| From Phase | The stage the project is leaving |
| To Phase | The stage the project is entering |
| Transitioned At | The timestamp when the transition occurred |
| Transitioned By | The user who triggered the transition |
| Is Skipped | Whether the stage was skipped rather than completed normally |
| Comment | An optional note explaining the reason for the transition, particularly useful when skipping a stage |
Transitions provide a complete audit trail of how a project progressed through its lifecycle. Skipping a stage requires a comment explaining the justification, ensuring that deviations from the standard process are documented.
Permissions
Building and modifying lifecycle stages requires the lifecycle:manage permission. Users with this permission can add, edit, reorder, and remove stages in the builder. Users with read-only access can view the builder in a read-only mode to understand the lifecycle structure.