PegaWorld 2026: Blueprint Live - Build & Deploy Agentic Workflow in 30 Min

Thanks for joining us today. Thanks for choosing to join us in our little session here. Uh, let's start with a quick show of hands just to get you guys involved. Who here has tried out Blueprint already? You guys kind of expected that too. So next question. How many of you, though, are still trying to figure out exactly how Blueprint fits into delivery? Yeah. That's good. You're in the right place because that's what we're going to focus on today. So I'm Jamie McCarthy director of go to market strategy at Pega. I'll introduce my coworkers here in just a moment. But if you were here yesterday and you joined Kareem's keynote address, you heard him deliver a pretty powerful message. And that is that we are moving into an energetic world. No, duh. Where AI isn't just assisting work, it's actually doing the work. But there's a gap that most organizations run into, and we think that is they can come up with great ideas.

Okay. They can generate designs even. But getting that from that to a real working application takes time, alignment, and effort. So that's the gap that we want to try to address in this session. Today we're going to show you how we go from a business idea to a high fidelity agentic workflow to a running application without the typical handoffs or delays. So as you're watching this, keep in mind, ask yourself, how quickly could your organization go from idea to execution if this was your starting point? So let's dive right in. I'm joined by two experts today. They're going to bring this whole thing to life for us. Maggie Oswald is going to walk us through Blueprint and show us how we go from business intent to high fidelity agentic workflow design, and then Brian Pageau is going to pick it up from there, and he's going to take us through that design and show us what it looks like when it becomes a working application.

So together they'll take you from a concept all the way through to runtime. Maggie, you're up. The stage is yours. Awesome. Nice to meet everyone. I am Maggie Oswald, I'm a product manager for Blueprint. I'm going to jump right in. I know we have a limited amount of time today, but Brian, I heard that your family might be joining you tomorrow. Is that so? Yep. Uh, wife and daughter are coming in, so extend it out a little bit. Okay. I heard you're maybe looking to book some travel excursions in Vegas. I mean, we have we have a little one with us. So, I mean, some entertainment would hopefully be, uh, be fun. So there's some looking for what's available. Okay. Well, I know U+ travel had this quite old website that I think you were looking at to book through, right? Yeah, I'm almost a half a century old, so, uh.

Yeah. Well, here we can see that he's been trying to book through U+ travel. Well, I'm going to be doing is going through and recreating that through Blueprint today. So if I just jump over into Blueprint a few tips and tricks, we always say, if you're able to upload any assets to create your blueprints, that's going to provide you the best output. So here I've uploaded a few different data definitions and some tours and experience booking requirements as I went through this blueprint. If you have not yet created a blueprint, definitely stop by the booths today. There's a bunch of kiosks in the Innovation hub, but what you'll see is the workflows that it does create for you. So you'll see that there's three different workflows booking reservations, cancellations, disputes, and you'll see the stages underneath that that's reflected right on this step two here.

And I'm going to jump over into workflow details. So if you're looking at this, you're seeing booking reservations. Brian. You guys want to be booking some excursions. That's the plan. I mean. So here you're able to see everything in just one view. So you can see that we have different steps and stages, but you're also going to see these different color indicators. So in order to make sure that we're handing this off to Brian and his team in the best state possible, that we want all of these colors on this side to be green. And why is that? Green means go. Green means go green means that you are ready to go into app or into dev and Infinity studio. And now that's all one thing into Infinity studio and you are ready to start your build. So here I'm going to take us through a few of these different steps and bring us from that lower fidelity step all the way up into a high fidelity Blueprint.

So here we can see initially, Brian, you're going to want to be searching your tours. What are some things you're going to want to be searching for? I mean, different experiences that are available, um, maybe different times than it is, you know, we have a young daughter. So, um, typical Vegas times might not be appropriate for us. So see. So we'll add number of adults children time slots experience. So we can see that now within this modal you'll see that we've taken it from in progress all the way up to detailed. So you're able to see that with your different stakeholders and collaborators across Blueprint. Definitely collaboration is key. We want you to be working and interacting across different stakeholders within your company. So I'm going to hit save here. We're actually going to jump over into reservation. So once you book your tour, you're going to search some options.

And actually we do need to check I guess a few of these options over here. It looks like most of them have a minimum age requirement. Brian are you worried about that at all? Uh, seven maybe going on 18, but still seven. So, um. Okay, so let's see what I'm trying. I don't use windows often, trying to figure out what's the screenshot. Windows shift windows. S I'm a Mac person through and through. So what I'm going to do is I'm actually just going to screenshot this, and I'm going to go over into Blueprint. And we see that we have this decision step that has not been filled out yet. We don't have a business rule and it's still in progress state. So what we're going to do is use our handy dandy AI assistant to help expedite that. So I'm going to go over here and we can attach different files to this.

Let's see where these files go to. That would have also been good to check. Um. One moment here. So you can upload anything at this moment in time. You can put in images. You can put in, you know, maybe an Excel spreadsheet or other content as well to be able to actually get this to be able to generate the content that's there. Yes, you can generate anything. So within this we are able to actually go in and check everything. We're going to try downloads. Well we are going to actually then just ask um the AI assistant. I'm going to say I'm going to start recording and just say allow for this time. Hello. I want to be able to make a business rule that helps me look at a business rule that helps me look at different events. And if they are eligible across different events such as Circus Soleil, we want the user to be at least five years old.

If the user is going to a dune buggy, we want them to be at least 18 and if the user is I'm going to the strip club. We want them to be at least 18. Probably not going to happen. The long ones not going there. So we're going to go in and we're going to ask it to create a business rule. I was hoping I could upload a file here. Apologies for some of these technical difficulties. But we're going to see we're going to let the AI assistant do its thing. It's going to come back and it's going to say if there's events you know circus delay strip club, sand buggy. So we're going to see ideally we would have uploaded all of these. You can upload any assets here. And I'm going to say go ahead and proceed with creating these rules. So it's going to go in the background.

We have all these different agents with AI assistant that are going through and are going to be creating the business rules and the business logic, so we can just not worry about it. It's just going to do it for us. And as we add that in, we're going to see visually where it is going to be introduced into our Blueprint. So here we can see that it's been created. We get that update. We now have the business rule within here. And we can actually go back in and bring this from in progress all the way up to high fidelity. So here we have that age eligibility. So if they're eligible we're going to say they can continue that process. So you can continue your booking. Go all the way down here, continue that process. If they're not eligible, we're going to bring them all the way down to one of our alternate stages.

Here for alternate experience suggestions. Otherwise we're just going to proceed. So once we select this we're going to see it be brought all the way up to our highest level of fidelity. So here we go. Green means go. We're good to save this and move on to our next step. The last one is a notification step. So here we do want to make sure that Brian and his family, when they're going to Cirque du Soleil, that they are being able to receive any pre-trip information. So I'm going to select who's receiving that, the customer email, and we'll see the email that has been pre-created for you out of the box upon Blueprint generation. Excellent. I might want to make sure I put my wife's email in there as the planners. So I'm going to go ahead and save this. And now we are going to jump over into our data integrations page here.

We have green all over this page. Green means go. We're ready to move ahead into our data integrations. So as Kerim mentioned, you can see that we have this new data modeling capability in Blueprint. You can see that we have on the left side, we have our user identity management and inbound events. In the middle, we have the core data objects that we are using to create this Blueprint. And then on the right side, we have these integrations. So I'm going to go ahead and talk you guys through a bit of these integrations. So if you guys remember when I initially created this blueprint, I uploaded a few different files, so I actually uploaded in a data definition for Uber and Stripe. So here you can see those were brought in for me and I have those external systems. So I know Brian it seems like did you guys rent a car?

Uh, yes. We're going to be able to drive around. Car seats are a little kind of tough in Ubers. Yeah. So he won't need any ride transportation. But if he did, we would have that Uber integration preset for anyone else to be able to use. And then stripe, when you're going through and paying, you can reach out to any of those payment transactions all the way into that stripe integration. So what I'm going to do is hopefully this file, this file is easier to find. Uh, don't know where the screenshots live, but I do know where my data definitions live. So I'm going to go through here and say, actually to get the Circus Soleil integration, we need to upload a Ticketmaster data definition. Please add this integration. I'm going to go in here. It's going to be able to analyze this file in real time, and it is actually going to search the different resources that it has.

And resources. Here you can see for the Uber, we have that ride request schedule, ride product trip history. So it's going to be able to read all that information, verify it with you before it adds, because we do want that human in the loop process. And then it will be able to add that and we can link it back to our experience listings. One other thing as this is going and loading is the inbound events. So Brian, I think how do you typically book events? Do you like going to websites like the desktop and API? I mean, there's going to be two of us that are going to be doing this. Me being in Pega, I'm kind of in, in AI. So like, I really like the idea of the MCP service and being able to use an agent to be able to help me with that.

Okay. But I know my wife is really going to want to deal with emails. So I mean, maybe emails and MCP. If we could. Emails and MCP, we can do that. So we have our email received here. I'm going to go ahead and just hit save. So we have the email of the user. We have the different case types that they'll be able to interact with. And then we also have you have MCP. You might want to be chatting with one of those external systems here. So right now MCP service, we brought it all the way up to detailed, but I don't think that we want the MCP service to be able to cancel or have disputes. So we're going to go ahead and remove those and hit save. Then you can see here that these inbound events to book your travel have now been added.

So Brian, you and your family, you can interact with the DCS, API, the desktop, any emails or MCP server. Awesome. Now you can see that we have added the Ticketmaster API here. So you'll see these resources that were added. And I'm actually going to go in here because I see that this one is still in progress. So we have our experience listings, everything that's being shown here, all of these different excursions, you'll be able to you want to make sure that you're grabbing those from Ticketmaster. So I'm going to go over here, see that integration system that we just added, Ticketmaster, select the resource such as events, and then save it back in. And we have now brought this data object all the way up to the green state. So here you can see that now we have our data and integrations, and we are going to take a quick look at our personas who's involved within this.

One thing to note too is you can actually see who has access to this application. So you can see that we have case access and data access for these users. So our customer support agent, they might have the ability to create, read or edit across those different case and data objects. Finally we are going to jump into previewing the application here. So what we have is a few different channels that we're able to look at. So these are available for you to use immediately. As you saw we have the desktop mobile Salesforce and lots of others. I'm actually just going to jump over into this web self-service one so you can actually see it and how it looks on your own application on your own website. So here we can just jump through Cirque de Soleil. That's the one that Brian, you and your family were looking at.

Matinee is a good idea, probably. Then we'll be able to see the experience, date, number of children and adults. And actually, I think we might want to add the age because I think that's pretty important. So we're going to open up our data Data Explorer. We're going to go in and find that field. As you guys saw, Kerim said, sometimes things are easier to just drag and drop. You don't need to have a conversational experience for all of these. Just dragging and dropping these ones over here. We're going to jump over to the desktop and do that. There we go. And we were able to actually see that it was added in real time. So you can drag and drop any of these fields and build out that UI right in front of you so you can work with stakeholders and make sure that you're changing things and getting the feedback right right away and iterating throughout the process.

So now, Brian, I believe that we're in a pretty good state. We have our entire Blueprint in a green state. So what does that mean? Green means go. Green means go. So I'm going to hand it over to you. We're going to download this blueprint and you will take us through the import process. We'll take that journey now. Awesome. Thank you Maggie. So my name is Brian Pageau. I'm a product manager for, um, studios I guess. So all of your studio problems are my fault, I guess. Um, so, um, so what we're going to look at today is I'm going to download the blueprint And use the mouse prime. Um, what we're going to look at today is what are the different options when we want to be able to take these blueprints and actually turn them into running applications. So a lot of you guys have functionality that's been built on Pega for years.

Sorry. And there's assets that you want to be able to reuse, right? There's functionality that exist and you don't necessarily want to be able to build it again. So we do have capabilities with app signature and a lot of our modernization tools to be able to extract that information from your existing solutions and be able to put that into a blueprint and bring that in. And using some of the tools that Maggie outlined with being able to bring those assets into the system. So what we're going to look at here is I'm logging into a new system. I'm logging into my system. It's basically, let's build from a blueprint here. I'm going to grab that blueprint file, see if I'm any better at finding files. Um, so we're going to grab our blueprint. And what's what we're the first thing that's going to happen is this is going to Basically it's going to tear apart the Blueprint.

For us, it's basically outline everything that we're going to have available to us, and we can use the blueprint details to be able to examine, make sure the different information is coming in, um, that, that we want. Opposite scroll on the mouse. So what I want to be able to demonstrate here though is the built on functionality. So what I have is we have a couple built on layers that already have functionality that we want to be able to reuse. So we have this magic button here built now. So if you click this, what it's going to do is it's going to take all of what we think are the best practices and the right things to be able to do based on the information that you have. If classes match and things along those lines, we're going to try to be able to reuse and do that thing, do what we think is best.

If you don't want to trust to us and you want to be able to walk through it and have a little bit more control over that, that's what this customize build option is. And we're going to step through that and talk about what some of the different options are. So as part of this, you're going to see all of the different case types that we're going to be built. So if you want to check out the Life cycle and make sure that it's going to be correct, well, there it is. This is what came in from the Blueprint and this is what we have available to us. The icons aren't showing, which is great on the system. But again, you have the data model that you can look at as well, and you can explore to make sure that that's coming over these options. Though, when we talk about building these, these different objects, what are we able to do?

So build from blueprints is going to grab our data model. It's going to grab our life cycle and it's going to be able to create all of it. The next option though, really starts giving us some power to leverage the functionality that you already have in place. You've already built it. Let's continue to be able to reuse it so you can choose to be able to build on another, another, another case type that already exists. And here I have a reservation case type that already exists. So what this is going to do is it's basically going to set up inheritance. I'm going to create a new class. It's going to be able to inherit from this class. So basically I have a case type and I still got all my old case type stuff available to me in my data model and everything. If I don't want to use my Blueprint Life cycle, which I do.

Maggie did a great job putting that together. I wouldn't want to throw that away. I'm not going to check this box if I check it. I'm just going to use my old life cycle and bring it all forward and just bring in my new data model functionality. The other capabilities, just to talk about briefly, there's a do not build. And this is sometimes if you want to build in in layers, people want to be able to do this. You want to spread it out, maybe into different applications for ease. You can choose to build a portion of your Blueprint. You don't need to build the whole thing at once. You can build it in stages, build one, build another, and they'll slowly build onto each other and use your built on stack to be able to put that together. So those are possibilities. I'm going to build this here, um, because I want to have all the data references and everything and make sure that gets created.

So now we're going to move on to the Data Objects tab. And we're going to have the same functionality here. So we have booking. That's great. I don't really have anything of that. But what I do have available to me is this experience listing. So within our organization we've already built out a Ticketmaster integration. I don't need to do this again. You have integrations into systems. You don't want to build them again. You want to. You want to Blueprint them. You want to be able to put them in your case types. But it's built. It's in a layer that's already available to you. This is how you reuse it. I'm choosing to build on that layer, and I can choose all of those different assets here so I can build a new integration if I want. Or even better, I can just use existing. It's not going to do anything at this moment in time.

So what we're saying here is you already got it. Just use it. Bring it into my app. Don't touch it. Don't do anything to it. Just use it as it is and map it in the Blueprint. So the import process is what it's going to do here is it's going to point everything that was pointing to this experience listing before, and it's now just going to point it to a vent. So we're going to do all that mapping automatically for you. And you can actually check it out because I've learned that people don't trust me all the time when I say stuff works, but you know, I try. So the other thing that we have lastly is the personas where you can look at the different settings that are available here, and you can choose whether you want to build these or not. And again, if you're building in stages for your application.

This is something you may want to be able to look at is maybe choose not to create the access groups all the time, but that's up to you on how you're building and your Blueprint delivered projects. So lastly, what we'll take a look at here is what is getting created. So come on, scroll up. I want to show we are creating a new work pool. Um, so this is basically where all our work is going to go for our application and what our class hierarchies are going to be. So we try to outline all of this information for you. So you know what's getting built. If you don't like this at this moment in time, let's go back in the process, okay? And we can figure out what to change and what we need to be able to make happen. But here you can see I'm getting my my base is building on my reservation.

That's great. Now what's my data object doing? Scroll down a little bit more. There's a bunch of data objects. Too many data objects. Experience listing. There it is. So it's basically reused from built on. I'm not creating anything here at this moment in time. So I can submit this. And I'm going to start creating this application. I'm not sure if everyone stays current. We release Blueprint updates pretty regularly. We try to be able to keep up with Maggie and her team. Sometimes they're a little too fast, but I'm not going to complain much. Um, so what we're trying to be able to show here is what we're doing at different stages within the Blueprint and Blueprint build process. So we're going to show you the case types. We're going to show you the different data objects that are getting created. We're going to try to tell you where we are in the process about what's being able to happen.

This is really meant as a debugging tool. If something does happen, you kind of know where it fails and maybe some of the things that are going to give a problem. So if I need to be able to help you, you know, that is that is useful information for us. I'm not going to let this run. Well, I'm going to let it run, but I'm going to switch to another app alt tab And I have a built application. So I feel like Martha Stewart pulling that turkey out of the oven. It's very exciting. Um, so this is an application that I had already built. So we took the tours experience booking, we built it out. And this, this is where you land in your application. Looks pretty awesome to me. Um, we're bringing that Blueprint um, look and feel forward. As you can see, we have this basic explanation of our, of our application.

So all the Blueprint information that was available. So our organization, our industry and departments and all that sort of stuff. And why is that useful at all? Well, this is context for the AI when we're dealing with the AI, and we're doing things about creating new case types and continuing to build our applications, we now have this context available to us for everything that we want to be able to send in, to be able to say, oh, you're in a bookings and travel business, you know, let's try to focus on that. So when we're using our best practices, we know the right ones to be able to pull and it gives a little bit more focus and context. So that's helpful. So I'm going to move forward. We'll step into workflows so we can see the different workflows get created. The stages that are here, they're all looking, they're all looking great.

And the same thing with the data and integration screen. So as we step into data integrations, um, the different things got built up, but we have some different colors here. Why is that? This is being driven off of user stories. So tasks that are open that still need to be completed. So when we generate and there's you see a 75 at the end, I'm not sure if anyone saw that little red dot wondering what that is. Um, that's the tasks we generate basically a whole bunch of tasks for you, for all the different steps and things that we're configuring. Blueprint does a lot of it for you. Okay. And I'll show you a lot of things that it does, but some of the things it still needs information on. So and on some of these, it needs a little bit of detail for you to be able to finish it and make it production ready.

I'm not going to be able to do all of those today because there's 75 of them. And that, yeah, that would be fast. I'm not the flash. Sorry. So we can look at this, at our different integrations and how they're built and how they're tied together. We can look at our, um, the, the different, uh, inbound channels that are configured. We can see that the listeners get created for us. Same thing with the MCP servers. Those are going to be able to get created as well. So all of these things are going to get generated for us. And that's great on the data side. So on our personas, um, same basic thing. So all the personas get created. So these are access groups with the appropriate settings that were defined within the Blueprint process. So we're going to create the access roles that are needed for you.

So that way the users have access to what they need. And something I'm not sure everyone knows is that with Blueprint in this new build from Blueprint, apps are locked by default. And what does that mean? The work pool that gets created. Users don't have rights to change anything in that anymore. We lock that by default, so that means you need to proactively go in and make sure your users have access to run the cases. And that's a little bit of a shift where before it used to be wide open and you had to lock everything down. So you have everything that's available in like work dash and things along those lines. The base Pega infrastructure. But anything that's really in your implementation layer, we want you proactively making the choice to be able to expose that information. So we pull it from Blueprint and we configure it for you and it's done.

If you want to change it, you can, but it's done with the build. So let's take a look at this implementation plan. So you can see a lot of different tasks kind of get done for you. Um there's some debate whether stuff should be in review or not. I move some of the things in into in progress for me so I can take a, take a look and show you how some of those work in a second. And then there's our to do list. But um, all of this stuff that's done, that's done, like, what is that? Um, what are we, what are we dealing with? I'm going to take a look at the workflow and I'm going to go into our booking reservation workflow that we've been talking about. So what is done? So when we talk about done, we build the life cycle for you.

Okay. We build the data model for you. And one of the things with reservation though we talked about is we reused from a different layer. So I just want to point out booking date here, for example, it's coming from the base layer. This is a field that was defined in Blueprint. We knew it was already available in our built on layer. I didn't duplicate it. Okay. We're using what's available to you. We're trying to reduce the amount of noise that you're getting in your application layer. Instead of having all these overrides and trying to be able to figure out, why do I have 15 fields that are all capturing the same thing and which one's rendering? Um, we try to get rid of all of that. So we're using the reuse layer and we're building things that are necessary. And this is really powerful when we come from the app signature side, because they're pulling in even more information about your fields and they're putting some detail on that.

So if you'd like more detail about that, I recommend talking to the the app signature teams and the modernization teams and the innovation Hub. They have some really great experiences there. So we'll take a look at the workflow. Um, and there's a lot of information that gets configured here. This is a work queue. Okay. So routing all defined in Blueprint. And this is all the stuff that makes green. Okay. This is the routing. This is the SLAs. Okay. You can route to a work queue. Every single access group that gets created. I'm creating a work for them. So they're there. You can route that work to those users now. And people can actually pull the work from those systems. The SLAs will get configured as well. And I think one of the main things is the views get configured. So the views get built out.

And we're following Constellation best practices here. So we we follow, we look at what um, what Blueprint's giving us. And we're trying to follow Constellation best practices to be able to build those, those views out, um, in the same system. So just to get ahead, I don't know if anyone is still on UI kit. Well, we're trying, we're building Constellation first here, so we're trying to go the blended approach, so you can still keep your UI kit case types the same, but everything new that we're going to be able to look to generate, we're going to do in a Constellation manner. Um, all right. So one of the coolest ones I find sometimes it's a little ugly. So I'm going to see what it looks like right now. All right. Go away. I wanted that pencil icon and it doesn't want me to have it.

All right. So this is our process modeler. So and what we're doing is we're building out this this process flow. And it's a little ugly. I'm sorry. This is something we probably need to get to. But what is it that we're doing? Is Maggie defined eligibility. She built a decision table that had different requirements as to what's going to go where. We are configuring that decision table for you, and we are routing the work correctly for you. So when you click on the different decision status, it's going to say, okay, this is an advanced shape because it's using a decision table. So the decision table is configured here and it's basically going to route to the different places. But all of this is built for you. Again define it in the Blueprint. We'll build it appropriately for you in the system. And then you can evolve it as you need to in the future.

But we're going to make that Blueprint definition real. All right. Um, the last thing I just want to be able to show is we'll preview the application here. We'll take a look at the work portal. And this is the app running. This is. This is a functioning application. So we can run our case types. We can choose. No we're not doing a casino crawl either. So um so she might like the fountains. So let's take a look at that. She's seven and we're going to do this tomorrow. Okay. And then we can actually move through our case flows, be able to to find the different processes. So these are all running. This is functioning. Basically everything that you saw in the Blueprint preview is going to be functioning here, but actually implemented in real rules. So lastly, we'll take a look at a little bit more on the implementation plan and how we can use this.

So some of the steps that really need to be able to be built out are things that don't necessarily have a complete configuration in Blueprint today, as Maggie puts more and more stuff in a blueprint and more and more configurations there, we're going to add more and more to the import we can. I encourage you to just keep up to date with the import component. Whenever you're starting a project, you want to bring in a blueprint. Try to make sure you have the right version, the latest version that's available on your system. So we create these tasks, but one of the things that we're pulling in is we're pulling in these notes. So if there are notes in information that you're putting into the blueprint, we're going to use those. So every step that's in your life cycle is going to get is going to get a task that's going to be associated to it, to configure it.

It's going to get the notes from there. We're going to be able to put it in there. Why is that important at all? We have our friend the AI assistant, right. And he they are going to be able to help us move this application to, to completion. And we can do that by clicking these little buttons and gives our, our information in here. And then we can actually get the AI system off to be able to start building out different, different options. So this, for example, is a connect GenAI step and say, can you, uh, can you and I'm the world's worst typist. So. Create a, an AI. Uh oh two. Yep. Maybe I should actually use the microphone as well. Uh, to. Summarize, um, the So, and then we'll give this off and it's actually going to run for a little while and be able to figure out what it's going to be able to do.

It can actually read my typing, which is good. Most of the better than most people. Um. So our implementation plan is here. Our application is built. Um, this environment unfortunately isn't on a cloud environment. But if you are creating on cloud K, if you're on cloud three, we're going to actually set up the deployment pipelines for you automatically as well. So you'll be able to move your application from environment to environment. And you'll get a, you'll get a merge pipeline that's available to you. And you actually get a deployment pipeline. So it'll do the merging and the testing and be able to move that, move that forward as long as well. So when we're doing these different analysis, we can actually create our unit tests and things along those lines as well with these different tasks. So, um, that's about it. That's Blueprint to, uh, to live about how we would build that, how we're doing.

Thanks, Brian. You're welcome. Thanks, Maggie. Really good stuff. So a couple of things I want to think about here before we go to Q and A, and if you want, these microphones here are going to go live in just a second. If you have any questions for Brian or Maggie, you can start kind of moving up to them too. But I think the key thing to think about here today is that, you know, with Blueprint and the AI agents that are going to help you push your application from idea to deployed, you want to start with intent, not requirements, right? So Blueprint is going to allow you to capture those business intents in a way that's immediately usable and quickly changeable. So nothing gets lost in translation as you're trying to to build an application. Second, think about using Blueprint as a design agent. Sort of goes back to my first point because it doesn't just document workflows.

It helps you define, refine, and evolve them in real time. And it's sort of the conjunction of where business and it can come and meet and work together. Third build for change. We're all familiar enough with Pega. That's our core principle, really. Build for Change today it doesn't. It's not a fixed design, really. I mean, what you see with Blueprint is really AI's best bet and suggestion. So, you know, we're expecting the human in the loop to come in and make changes and revisions to that too. And you can do that, as Maggie showed us live and see the changes take place right in your app right away. Um, lastly, the agentic workflows are going to be the thing that you want to sprinkle in at the end. Um, you are not just automating tasks through these workflows, right? You're orchestrating agents that can make decisions, can take action and drive outcomes across systems.

So these are real applications. They're not prototypes. This is, um, a working foundation with workflows. What Brian showed us everything from workflows, data and logic already in place, ready to be extended, governed and deployed at scale. Um, so if you have more questions after the Q&A period, I would strongly invite you to go down to the Innovation Hub and track down Maggie, who will be circulating amongst the Blueprint kiosks that are out there where you can get hands on with our blueprints for yourselves. And Brian will also be down in the Innovation hub too, so you can grab him for some more 1 to 1 conversations. Um, do we have any questions? There's got to be one question. Oh, awesome. We have a taker. Thanks. Oh two. Go ahead. Hey. Good morning. Thank you so much for the presentation. My name is Brian Kelly from Navy Federal Credit Union.

Good name. Um, yes, Brian is a great name. I and the why doesn't matter either way. It's good. Um, yeah. So I just had a quick question about kind of the scope here for our developers on our team that work in Pega. Um, and it must be very difficult to kind of pin this down, but just general range wise, you have kind of an idea of how many hours you know, this saves someone who's doing the traditional, uh, you know, like Pega development versus like using Blueprint and maybe getting into the genetic elements might be a little bit harder to pin down, but do you kind of have a range of like from a typical project, like how many hours that might save? Um, I don't know if I would measure it in hours. I mean, would we measure it in weeks and months? Uh, maybe.

Um, really the Blueprint is a game changer there. And I think we can see that with our Blueprint delivered projects where you're delivering, you're delivering completed projects in 40 days. Um, so there's those would typically have taken, you know, six months longer a year. Um, so we're seeing a much, uh, very large change as part of that. And just one of the things I, I focused on building a new application. So, but Blueprint can be used to be able to extend existing applications as well. So as part of the import process and all that sort of functionality, we have the ability to extend the applications in the same way that we. We built a new application so you can get your business teams and your development teams working together in Blueprint. Ideating coming up with new case types, new flows that they're going to add to existing apps and use that import, leverage the functionality that's already there to be able to accelerate that delivery really, really rapidly.

But I mean, there's hundreds of rules that you're not having to have a user even touch anymore, no fields that you're needing to be able to create data references and mapping all the view layouts. It's done for you automatically. Great. Thanks, Brian. Thank you. Brian. It's always great. It's always good to talk to another Brian. So we've been using Blueprint for the last probably 8 or 9 months. Um, my question is around. We are currently using current version of Blueprint, and we were able to import to import into 24 version 24.1 dot 5 or 4. Yep. So similarly with the new version that you are releasing, right? Are we able to use in the, you know, older platform import into. I know, yeah, this is one I'm actually kind of proud of old here. Sorry. Um yes you can. So one of the things that we've tried to do is we're moving to, um, we've implemented something we call a component module sort of approach to the platform.

So there's certain functionality that it's changing rapidly. Um, how many of you want to get a new version of Pega every two weeks. No, no, nobody does. Right. So we kind of understood that, but we still need to give you that functionality. Blueprint is going to evolve. I can't have you take a patch update to be able to get that functionality. So we're we're planning on shipping that out. Our plan is anything that's in support, a supported version we're going to support back to those things. So right now we're still supporting 23. One five is the first version that gets that. And the import component can be installed on those versions. Now what that said, there's certain functionality that you can define in Blueprint that doesn't exist in 2315. I'm not backporting that functionality, but whatever is there for that version, we are going to be able to support.

So Constellation is going to behave differently in 2031 as it's going to do in 2041 and 2042, 25 and 26. So as those features evolve, like AI, I'm not necessarily going to backport all the AI functionality there. Thank you. So small question. While you are building the Blueprint, I saw with some special characters or numbers being added to the class structure. Right? Is there any reason for having classes or data models having underscore 1 or 1 like that? Conflicts, conflicts, conflict, conflicts. So we try to be able to address conflicts. And when Maggie was building from, she brought the Yaml in to be able to build that out. There's a whole bunch of embedded objects that get created as part of that. So there are data structures and things along those lines. You can kind of sort those out within Blueprint if you want to, but we'll sort them out intelligently for you.

So I think one of them was like address. There was like three different address fields for like some of the different integrations. So if you wanted to be able to sort of bring those together, you can do that in Blueprint to be able to get the embedded objects all point to the same thing. But as we were creating three classes with the same name and the same structure, that would have been a conflict. So we just, we get rid of it with with numerics. If no other questions. Keep them coming. I like questions, that's my job. So. Um, I think that, you know, you can import variety of objects or documents, PDFs, etc.. Um, I believe we ran into some issues, especially importing, say I have, you know, screenshots defining the functionality. You know, I just wanted to import it as a PNG or Jpeg files, you know, just a screenshot.

I want Blueprint to be able to generate that. Right. But we ran into some issues. Um, is there any specification to say, you know, those file types needs to be this, um, supported files etc.. Yeah. So within the Blueprint file upload, you'll see the different files that we do support. We do try and provide helpful user messages. We've recently, as you guys know, we add new functionality into Blueprint almost every week. We've been rapidly updating those. But with that, we are constrained to different AI models with the document analysis as well. So we've been updating that, and especially with the new fleet models that we've been able to get our hands on in the past few weeks, we've been updating those. So if you run into issues, just let me know. You can also email [email protected]. Um, for anything, but hopefully with the most recent models that all the file analysis will be improved.

Yeah. And also with the new version, because of the AI, you can with vibe code, you can ask and generate probably we don't run into that issue, but just we had that issue in the older, you know, Blueprint version. Thank you. Thank you. Thank you for sharing. I have $1 million question and a compliance question. So from a blueprint perspective, I know you have a sandboxing. What do we upload? It's it's quarantine. Some level of visibility. It's not goes to public cloud is the right statement or go to public, say for example, when I try to create a highly regulated or compliant applications, I upload some of the artifacts for Blueprint. Is it quarantined somewhere within the environment or the cloud or how it is confined to Pega? Yeah. So if you are a PegaCloud client, then we will store your files within your own S3 bucket.

And we actually did release a new Blueprint administrative capability on Friday. So if you are interested in understanding who within your organization is creating blueprints, you'll now be able to see a report of who has created those blueprints, if there's documents attached there. And you'll also be able to see configure any security settings or branding logos, anything along those lines. So if you are a PegaCloud client, they will be stored within your own S3 bucket. So that's yours. Your organization's if you're not a Pega Cloud client, they'll be stored within a Pega managed S3 bucket. But you are all. I guess every organization is within their own folder, so everything's isolated and separated. We have some level of traceability towards it. Yes. Thank you. Token costs. I know it's brought up in yesterday and today. No prompt, no token cost. Is there anything that if I bring this to my on prem cloud and manage like for example, 261, you can use the Pega SaaS cloud or you can have your on prem.

If it is on prem, it's going to use our AI gateway to communicate for all the AI agent work. So if I, if I understood correctly, if it isn't SaaS cloud, no cost. If it is an on prem cloud, is there a cost involved? Yes. And you're talking about for in Infinity. Correct. Right. Yes. I believe if you're bringing your own AI to this and you're not going to be able to. You're not choosing. Yes, you're going to have to deal with the token. Okay. So for example, 261 release some point in the future instead of opting in for the SaaS Cloud, I'm doing it in my on prem deployment. If I need to run through because Blueprint is inbuilt in 26 dot X is the right statement. And we're actually going to reach out to Blueprint at that moment in time. So you're not going to necessarily need to worry about that.

So if you do create a case type and some of the different interactions that we have in Infinity, we're just making an actual request to the Blueprint service. And that's that's all handled. So it's basically like a simple it's through an MCP, but you can think of it as a rest connect. We handle all of those costs. Got it. Thank you. I'll do a quick time check. We've got time for one last question I think right now. So let's let's do that I appreciate it. Jeremy Kramer with Unum in operations. And we have a lot of complex processes, workflows where multiple people are involved, a lot of handoffs, kind of taking your scenario where you had reservations as if you were here. But if you were back home and you had to get flight, rental car, dog booking or boarding. Uh, would you suggest kind of starting at like one step of it or can it encompass everything?

Because it can be so different and complex and you had multiple tasks to do within that one step. Yeah. I mean, that's case design, I think is probably one of the main things. Um, you don't want your case types to get too long. So if you have like 15 different stages as part of that, we want to break that down into smaller tasks if we can. So using sub cases, another example of that. So you may have an overall booking that's going to spin off travel, you know, flights, rental car, hotel and all that sort of stuff. And those could all be separate, different flows that are all spun off. We haven't really talked too much about agents, but it could be spun off identically, right? Depending on what you want to be able to do, you can have an agent that's helping you be able to organize and spinning off the appropriate processes to, to drive those different tasks.

That way you can have also different teams working on those different areas that are focusing on that. So. And that just sorry, things pop into my head randomly. So everything that we do create, though, we do bring into it as a branch as well. So all the stuff that Blueprint is going to do, we're going to put it in a branch. So if you don't like it, you can get rid of it. So our rollback ways that we have to just drop that information. So you don't have to deal with all this what we call space junk sitting around in your system so teams can experiment. We want to encourage that. Bringing in things, working with Blueprint, doing that collaboration building. And you know, if it's not what you want, we have an easy path to be able to get back to where you were before.

Thank you. Hopefully I answered that. Okay. That's time folks. So thanks again for choosing to join us this morning. I would encourage you again down in the Innovation Hub to look for Brian and Maggie. Thank you guys. That was excellent. Very informative. Appreciate your help. Thank you. All.