This video builds on the previous extension scenario by introducing a second outcome (MLP 2) into the same existing application. The focus is on using Blueprint to drive incremental evolution—merging earlier imports, then importing the next set of case types and data objects without duplicating what already exists. You’ll learn how to selectively inherit from existing assets while choosing to keep the Blueprint‑defined lifecycle when it better reflects the agreed business design. The session also demonstrates the strategic use of “use existing” to swap Blueprint references for established enterprise assets. This scenario applies when iteratively evolving an application over multiple releases while preserving architectural consistency.

What you’ll learn

• How to incrementally extend an application across multiple releases using Blueprint
• How to avoid rebuilding assets already introduced in earlier imports
• When to preserve Blueprint‑defined workflows instead of inherited lifecycles
• How “use existing” swaps Blueprint references for enterprise gold‑standard assets
• How to safely evolve an application while maintaining architectural consistency