Process application development lifecycle

You can use Web Modeler to quickly develop and progress low-risk process application releases through the stages of a typical development lifecycle.

caution

For business-critical and higher-risk processes that require strict governance and/or quality requirements, you can integrate Web Modeler into your CI/CD pipelines.

Model

During the modeling stage, you will typically:

• Create a process application and select a default development cluster to deploy to.
• Invite other users to collaborate on the process application.
• Define and set up the clusters and deployment stages you will use in your development pipeline.
• Model your diagrams and associated resources, and fix errors shown in the modeler.
• Use token simulation to correct and optimize your process flow.

Deployment pipeline stages

You can use the provided Web Modeler deployment pipeline to manage your application process deployment. The deployment pipeline has four stages named Development, Testing, Staging, and Production.

Stage	Description
Development	Use to create and test new software features and changes.
Testing	Use for quality checks, ensuring software meets defined standards before release.
Staging	Use for controlled testing where changes are validated before deployment to production.
Production	The live system with the latest software. Only administrators and organization owners can deploy to this stage.

To define your deployment pipeline stages:

1. Open the main process.
2. Select Deploy to open the Deploy process application modal.
3. Select Define stages to open the Define stages modal.

   

4. Select and assign a cluster to each deployment stage that you want to use in your deployment pipeline.
5. Select Save to save your changes and close the modal.

note

• An administrator must define the cluster to deploy to for each stage.
• During deployment, the next stage is not automatically selected. You must select the stage you want to promote to.
• You must select a cluster for at least one stage to be able to deploy. An Undefined stages warning is shown if no cluster is selected for at least one stage.

Validate

When your process application is ready for validation you can deploy it to your development cluster.

• Use Play mode to quickly validate the process behavior and play different scenarios.
• Validate that all files and resources are correctly deployed.

note

Play is being rebuilt and progressively rolled out to more users. See Play limitations and availability for Play limitations and why you might not see the Play tab.

Review

After validation is complete, you can release a version of your process application for review and approval.

• Use process application versioning to track and review changes across the files and assets in the process application. You can compare milestones to visually review changes between two versions of a BPMN file, or view code changes for other files.
• Use comments to make review collaboration easier.
• Approvers can add a comment to the main process diagram to indicate that a review is complete and that the process application is ready to be promoted to the next stage.

Promote

After the review is complete, you can promote the versioned process application to the next stage(s) of the deployment pipeline. For example, promote to your testing cluster/stage, then to staging, and finally to production.

info

If you want to use your own deployment pipeline after the review is complete, you can use Git Sync at this point to deploy and promote the process application through your own pipeline.

Process governance

The Web Modeler development lifecycle provides the following process governance:

Governance	Description
Change control	Users can announce a review is complete by adding a comment to the main process diagram. Governance is not enforceable, and comments can be deleted.
Deployment control	Deployments can only be made to the pre-defined set of approved clusters. Only users with correct privileges can deploy, and only organization administrators can deploy to prod tagged clusters. Each deployment action is logged with information on the user and stage it was deployed to.