Conversation
Pegasystems Inc.
SE
Last activity: 4 Sep 2025 9:24 EDT
Blueprint Game changing enhancement - Support for Multiple Processes in a Stage
The newly released "Support for multiple processes in a Stage" feature in Pega GenAI Blueprint enables us to create case designs that is modular and mirror business reality. As someone who has facilitated numerous Low Code Enterprise Development (LCED) workshops, I can confidently say this enhancement will help us think of modular reusable processes during the Discovery phase.
The Game-Changing Enhancement
The new multi-process stage capability transforms how we model business reality in Pega Blueprint. Now, when designing a case lifecycle, we can add multiple processes within a single stage using the intuitive "Add Process" option in the stage menu. This seemingly simple addition unlocks profound possibilities for creating more accurate, implementable designs.
Key Benefits for Enterprise Development:
- Enhanced Business Alignment - The ability to model multiple processes means our Blueprint designs can accurately reflect how businesses actually operate.
- Improved Reusability - With multiple processes per stage, we can create more granular, reusable features. Individual processes can be designed as modular elements that can be leveraged across different case types and applications. In addition, the “Add Process” feature helps us be explicit about the “What” are the key activities and flows required within the case lifecycle while leaving the “How” (the technical implementation) to be refined during the Build phase. This enables teams to capture all the business relevant placeholders, even when full details are not yet known, ensuring a more complete and business-readable design during the Discovery phase.
- Better Resource Optimization Feature driven approach enable better resource allocation planning. Development teams can identify which processes can be built simultaneously and which require sequential development, optimizing project timelines and resource utilization and ownership of features.
- Agile Delivery By modeling multiple processes at the design stage, user stories can be aligned more effectively with each process in product backlog. This allows Product Owners and Scrum teams to manage their backlog with greater clarity, ensuring that each sprint delivers business value tied directly to specific processes.
In the below example I showcase how a Blueprint case design can truly reflect the modular design of case lifecycle.
Note:
Please ensure you use the latest version of the import component https://pegasystems.github.io/pega-dev-components/ so that multiple process are created post import.
Known Limitations
-
Drag-and-drop functionality for processes in both primary and alternate stages is currently on the roadmap.
References
https://docs.pega.com/bundle/blueprint/page/platform/blueprint/blueprin…
https://academy.pega.com/module/modular-enterprise-reuse/v1
https://docs.pega.com/bundle/platform/page/platform/app-dev/journey-lce…
https://docs.pega.com/bundle/platform/page/platform/app-dev/journey-lce…
BNYMellon Technology
IN
@Vikram Bandodkar Multiple Process will be Parallel, correct? with multiple assignments. So if a Process is dependent on its previous process Approval its better to design them as a Stage.
Pegasystems Inc.
SE
@ArvindThe process will be serial within a stage. So they will run once the previous process is completed.
In my example, in Communication stage, first the create dossier will run, and once completed successfully the next process Update Dossier will run and so on.
Hope that's help you clarify the question.
BNYMellon Technology
IN
@Vikram BandodkarThanks Vikram. Thought it will be a parallel process reading the documentation. Will explore.
Pegasystems Inc.
SE
Please ensure you use the latest version of the import component https://pegasystems.github.io/pega-dev-components/ so that multiple process are created post import.