App Deployment pipeline
Approval workflows and environment-specific controls govern how and when models reach each environment.
What it is
Flowable Design now includes a configurable deployment pipeline that governs the path your models take from authoring to production. Approval workflows decide when a change is allowed to move forward, revisions keeps every release identifiable, and environment-specific controls determine how and when models reach each target environment.
What’s included:
- A configurable deployment pipeline from authoring to production.
- Approval workflows that gate when a change can be promoted.
- Environment-specific deployment controls.
- Deployed app are identifiable by revision key and the Design workspace the app is coming from.
Why it matters
Controlled promotion directly in Flowable Design enables enterprises to tightly control all changes going into production without having to build their own pipeline. Approvals give the right people a checkpoint before a change reaches a live environment and the revision makes every release traceable.
How it works
You configure the deployment targets in Flowable Design that need governance to only deploy with an approved publish request. When a modeller wants to publish an app, a publish request is created, which first needs to be approved by a predefined user or group. Approver and modeller can discuss the changes in the request and once everything is ok and the approval is given, the app is automatically published to the selected environment.
Together with the new revision comparison, this feature gives the control enterprises need to govern the lifecycle of their business logic.
Example
A team finishes their changes on an order-handling application and want to promote their changes through the environments. They first publish to test, which they can do without an approval. After everything is tested, they create a publish request for production. The team lead sees the publish request in Design, visually inspects all the changes in the Revision Comparison View, writes a comment and approves the request. The app is published to production.