The Blueprint That Shipped While You Were Reading Requirements

Blueprint and App Design
1

I want to share something that hit me while reviewing Blueprint’s release timeline.

In the time it takes most partner teams to complete a traditional discovery phase — let’s call it 8 to 12 weeks — Pega shipped the following Blueprint capabilities:

· Business Rules with Decision Step integration

· SLA configuration directly in Assignment Steps

· Embedded Data field support across Case Types AND Data Objects

· Automatic backup before regeneration with version snapshots

· User Reference routing for Assignments

· Stage-level routing from Decision outcomes

· AI-generated picklist values

· Browser-based voice conversations in the live preview

That’s not a yearly roadmap. That’s August to February.

Let that sink in for a moment. The platform is evolving faster than most discovery documents get signed off.

I’ve been working with partners on AI-first transformation strategies, and here’s the pattern I keep seeing: teams that learned Blueprint six months ago are already operating on an outdated mental model. Not because they weren’t paying attention — but because the capability surface area is expanding monthly.

Here’s the practical question for this community: How are your teams staying current with Blueprint capabilities between engagements?

I don’t mean “are they aware Blueprint exists.” I mean: does your team know that as of January 2026 you can route an Assignment to any user reference field defined within a Case? That you can use a Decision Step to move a Case to an entirely different Stage? That you can configure SLAs directly inside Assignment Steps without leaving the Blueprint authoring experience?

These aren’t cosmetic updates. They fundamentally change what you can model during a discovery workshop. A Blueprint created today using only what you knew in September 2025 is leaving significant design fidelity on the table.

I’m going to post a series here over the coming weeks exploring how the velocity of Blueprint’s evolution changes the way partners should approach pre-sales, discovery, and delivery. I’ll try to make each post practically useful — tied to specific capabilities you can use in your next engagement.

To kick off the conversation: What Blueprint capability shipped in the last 6 months that changed how you approach a client workshop? I’ll share mine in the comments.

2

Hi Pumolo, a lot of new features have been added to Blueprint which is great! Designing new workflows with Pega has been made so much easier.

To keep up-to-date on the latest and the greatest with Pega Blueprint features, I’d recommend building a Blueprint regularly, following Pega on LinkedIn and / or following Pega docs: Pegasystems Documentation

Looking forward hearing how Blueprint helped you!

Regards,

Sjors

3

Hi Sjors, I agree enthusiastically that building Blueprints is a great way to stay current. I also think it is important to spend some “academic time” reading the release notes and thinking through the potential that new features expose. I try to ask the most questions about the features I don’t immediately see value in. Pega is a very smart company and when I miss the objective, I prefer to ask and find out why it is useful. My favorite new feature is a preview of what is being released next week: vide coding. In a few weeks of pre-release I am hooked. It is a game changer. I love that blueprint can create a new vision for us when we don’t know much about a case type or application. However, when you have a strong opinion about what you need to build I sometimes fight the ai. With vibe coding, I now discuss and collaborate on the happy medium (my new pair coding).

1 Like
4

My strategy has been to import incrementally. Import one case type at a time, get it working then import the next. Blueprint changing at the rate it does provides the opportunity to take advantage of new features and reduce the effort post-import on subsequent imports.

As an example, we are just now starting to get the full capabilities we have been needing with embedded data. This is going to make it feasible to prepare views in blueprint that align to our target state data model reducing the level of post-import adjustments.

1 Like
5

Two Blueprint capabilities have drastically changed how I approach customer engagement workshops: document upload and vibe coding. With document upload, I can feed BRD’s, legacy code, or even a video directly into Blueprint and watch it generate an application design in real time — clients immediately see their world reflected back as a working prototype. This accelerates alignment like nothing else. Vibe coding takes it further: describing a workflow in plain language and having Blueprint instantly create Case Types, Data, and Personas means we spend workshop time refining a design together rather than building from zero. These two capabilities have shifted my sessions from “here’s what Pega can do” to "here’s your process, and how it looks in Pega”.

1 Like