Lifecycle Workflow
Control how business records progress through states, actions, permissions, and automation.
Define workflows for each business type, govern what users can do at every stage, and connect transitions to commands, notifications, and program logic without custom screen development.
Explore the CapabilityLifecycle Workflow
Type-Specific Lifecycle Modeling
- Configure separate lifecycles for projects, tasks, tickets, assets, audits, inspections, and service records.
- Define starting, terminal, and exception states that reflect your process, including On Hold, Under Review, Approved, or customer-specific states.
- Allow parent and child records to follow independent lifecycles while automation synchronizes progress, status, and relationships.
In practice
Operational task execution
A task moves from Planned to In Progress to Completed, with comments and role permissions at each transition. Execution remains controlled and traceable.
Lifecycle Workflow
Promote Actions and Transition Paths
- Define valid source-to-target actions such as Initiate, Submit, Approve, Reject, Hold, Resume, Complete, Skip, or Discard.
- Control whether actions are visible, restricted by role, or hidden for custom-program-only execution.
- Require comments, confirmation, or input dialogs when transitions need business justification or supporting evidence.
In practice
Hold with a recorded reason
An authorized user places a record On Hold and enters a mandatory reason. The record can later be resumed, while the history preserves the explanation for the delay.
Lifecycle Workflow
State-Wise Permissions
- Configure permissions for editing basics and attributes, linking and unlinking records, and performing promote actions in each state.
- Give operators, reviewers, and managers different rights as work progresses.
- Protect records from unauthorized changes during review, approval, completion, or locked states.
In practice
Governed approval
A process record moves from Active to Under Review to Approved. Only an authorized approval role can perform the controlled transition.
Lifecycle Workflow
Commands and Process Automation
- Attach commands that update attributes, copy user input, unlink resources, send notifications, or execute program logic.
- Use C# program hooks for dependency checks, completion roll-ups, cross-entity updates, and integration calls.
- Configure hidden Skip or Discard actions for background automation, and log command failures with selected escalation notifications.
In practice
Completion roll-up and resource release
When child work completes, a program recalculates parent progress. A configured unlink command releases related operators or resources for future planning.
Lifecycle Workflow
Auditability and Operational Traceability
- Capture who performed a transition, when it happened, which comments were entered, and which commands executed.
- Use lifecycle history for customer communication, audit reviews, compliance evidence, and troubleshooting.
- Connect lifecycle state to dashboards, reports, search, activity history, and notifications.
In practice
Review the process history
Reviewers can examine transition comments and execution history to understand how a record progressed and investigate process exceptions.
How Lifecycle Workflow Works
Define the entity type and its required lifecycle.
Create the states, including a default starting state and terminal or exception states.
Configure valid promote actions between source and target states.
Set action visibility, role access, mandatory comments, and automation-only behavior.
Configure state-wise permissions for editing, linking, unlinking, and promotion.
Attach promote commands, then validate access, comments, notifications, parent-child updates, and failure handling with sample records.
Connected and Governed
- Trigger notifications on approvals, holds, rejections, completions, and selected failures.
- Use Dynamic Forms to capture structured information before submission or approval.
- Run scheduled checks for overdue states, pending approvals, and stale work.
- Execute program logic for calculations, validations, cross-entity updates, and enterprise integrations.
Business Value
- Model complex processes through configuration instead of custom screens.
- Combine workflow, permissions, comments, commands, and notifications in one governed layer.
- Ensure valid users perform valid actions at the appropriate process stage.
- Preserve traceability for audits, customer communication, and management reporting.
Give Every Process a Governed Path
Configure states, transitions, permissions, and automated outcomes around the way your business records need to progress.