A project lifecycle describes how work moves from initial creation to a released, reusable solution. Each phase builds on the previous one, allowing projects to be developed iteratively, validated, and refined over time. Projects do not follow a rigid sequence. You can return to earlier phases whenever changes are needed.
At a high level, a project moves through these stages:
-
Create and organize project elements
The lifecycle begins when a project is created. During this phase, you can define the scope of the business solution, create initial project elements, and organize work into a clear structure.
-
Edit and save changes
As you work within a project, changes are made to individual project elements. Edits are not applied automatically and must be saved explicitly.
-
Validate configuration
Validation is used to check a project for issues before it is released or reused. When validating, the system checks for missing or incomplete configuration, invalid references, or structural inconsistencies.
Validation can be performed multiple times throughout the lifecycle and does not lock or finalize the project.
-
Release the project
Releasing a project creates a snapshot of its current state. A release represents a stable version of the project that can be used, shared, or restored later. It does not prevent further edits.
-
Deploy the project
Deployment makes a released project available for use in a runtime environment. When a project is deployed, the released version becomes active in the target environment, processes can be executed, and users can interact with forms and workflows
Deployment is done in Studio Admin.
-
Maintain the project
Most projects continue to evolve after deployment. Maintenance can include fixing issues identified during use, improving the existing process elements, adjusting the configuration for the new requirements, and creating and deploying new releases.This stage often loops back through validation, release, and deployment while preserving earlier versions for reference or rollback.
Each stage supports controlled, repeatable development without disrupting existing work.