PegaWorld 2025: How AI-powered Development with Pega Leads to 8x Faster Go-lives

PegaWorld 2025: How AI-Powered Development with Pega Leads to 8x Faster Go-Lives

Hello and welcome everybody. Today's session is about how AI powered development with Pega leads to eight times faster goal lives. My name is Caroline Power. I work on a team at Pega dedicated to understanding how clients, partners and staff adopt Pega's latest technologies. Today I'm joined by Brian Long, a friend, a colleague, and one of Pega's best demo principals.

He's going to show you the tools. But before we get started, I'd like to get a show of hands. Has AI changed your SDLC cycles this past year to go dramatically faster? I see a couple hands. That's awesome. I would love to hear after the session what you did and how you did it. But for everybody who didn't raise their hand, we want to change all that.

Next year, we want to introduce you to this idea of autonomous authoring. It's the IT counterpart to the autonomous organization where you're supervising work getting done. In it. We're supervising application assembly. Everything starts with a Blueprint. And the reason everything starts with a Blueprint is the same reason why when you go to it, they say, what do you want to build? It's the instruction manual for your application.

It's where you're going to put the instructions that Infinity can interpret, so that Infinity can do all the heavy lifting for you on import. It's going to generate a backlog on import all that stuff that doesn't get done for you with all the decisions that you still need to make. It has a developer assistant right in App Studio that you can use to extend classes to find where the out of the box is if you don't know, and then it proceeds through accelerating testing with quality support and an automated test suite.

And if you've used AI in the past year to create components or generate code, you've sped up one person. If you use these tools woven throughout the Pega SDLC, you're speeding up your whole team. And nobody builds anything interesting alone. So I want to show you these tools. But before I do, I just want to talk about when I was a product manager in Pega's IT department.

I used to write user stories all the time. As a user, I want certain functionality so that a business outcome could be achieved. And I used to bring my stories to my lsas and they would kind of pat me on the head and say, cool, Caroline, we'll break these down into about ten stories and we'll let you know when they're going to be done.

And I would scratch my head thinking to myself, how am I going to demonstrate that? How am I going to show my stakeholders what we built for them piece by piece? Will they will they understand it? With the latest architecture, you can build dramatically faster. What you're going to notice in the backlog is we are trying to help prevent any gaps in your workflow.

If you're entering information on a collect information step, you're going to need to edit that information downstream, probably maybe a CSR, edit it later on in the workflow, and then you're going to want to display that data right on screen and maybe in a BI layer. And all of those activities can be achieved way faster than they could in traditional UI.

And we want to see you get that speed. And we want to set those expectations, because if you're not a Pega architect, you don't know that that's reasonable today where it wasn't reasonable in traditional UI. And so without much more I want to show you the tools so that you can see how to do these activities, and take these back to your slcs. Let's check it out, Brian. All right. Yeah. Thanks, Caroline. So I appreciate the introduction. My name is Brian Long. I've been at Pega for 14 years now, and it really has been quite the journey just seeing how we've grown. And also as AI continues to really just influence how we build our product.

Um, so as Caroline said, I'm going to start us off in Blueprint because, uh, where else would I start off? That makes the most sense. Um, but I'm also going to be showing quite a lot of other capabilities and technologies that we have also in Pega Infinity. Um, so it is going to be a little bit of a whirlwind.

I'm going to go fairly fast at a fairly high level. Uh, if anyone has any questions or wants to go a little bit deeper into what I'm showing, um, by all means, after the session, flag me down the hallway. I can either answer it directly, or I can help you find one of the experts in the innovation hub that can go a little bit deeper into that capability.

All right. So this is a little bit of a fire hose demo. Um do that on purpose. We just want to kind of show a lot of the capabilities that we have. A lot of the capabilities that maybe you don't know is in Pega Infinity. Um, and so maybe we can kind of get you thinking about some of these ways where Pega can really help accelerate your delivery, uh, maybe in some ways that you haven't thought of yet.

Um, so without further ado, as, as Caroline said, we are going to start in Blueprint, but I'm not going to start in Blueprint. I'm actually going to start with a fairly mundane word document. Okay. Now you saw Karim's keynote. You saw Don's keynote. You saw how they're able to ingest all this documentation.

Kerim ingested a video of a COBOL application. Right. Which is honestly pretty crazy. Um, but that's not what I'm going to do here, right? I'm just going to have this little word document that basically describes a retail loan origination application. So this is a loan origination app that we want to push out into a retail bank Okay.

So I have this document. It describes everything that we want to do. And of course I could upload multiple documents. So I'm going to go ahead and do that here. I'm going to create a new Blueprint. And we're going to basically bring in this documentation very much like what you saw Kerim and Don do in their keynotes.

All right. So at this point, what's going to happen is the first round of GenAI work within Blueprint. This is where we're interrogating that document, we're analyzing it and we're summarizing it, and we're figuring out with all of that material that you've uploaded, potentially even including a video, what this app needs to do once it's implemented.

Okay. So at this point, we're summarizing, we're analyzing, and in a moment we'll just see how we get this summary here. So already we can see we have a lot of metadata about this application. We can see the industry the sub industry the department. Obviously this is a lending application. We have a rich functional description that we summarize from that documentation.

We see our workflows. We see our data. So we already have the groundwork for a really solid application so we can keep progressing onwards. So once we move forward, we'll be able to go in and then start doing a little bit more definition work. So obviously this is a banking app. It's retail banking. It's lending. We are going to specify that this is our ubiquitous U+ bank organization. We've seen U+ quite a bit at this PegaWorld. And we'll go on and press next. And then we'll do our second round of GenAI processing. And so this is where we take that functional description that we summarized initially.

And now we start adding in more structure to it. We start creating our case types. We start creating additional assets that make this app come alive. So we have two case types. We see loan application and we see underwriting. All right. So so far this is very similar to what you've seen in the keynotes right.

But here there's some additional things that you can do. You can start going in. You can start editing things. You can start changing things if you want to add in more documentation into the Blueprint, you can. Right. So it's all completely iterative and collaborative as you go through this process.

So at this point we have two case types. We can go ahead and edit the description if we choose to. We can delete case types I only have two so I'm not going to worry about that for the time being. But also at this point we see here BPMN. So if you have an older application, maybe you have a case type that is defined using BPMN.

This is where we can import it. And if you saw Dawn's keynote where he got into soapbox and started talking about BPMN, well, this is where we can start to add translation from more legacy older kind of specifications. And it's something that we think is quite a bit more modern with Pega. Okay, so that's where we can start introducing things like BPMN for those case types.

So once we progress further, we can also add in additional cases if we choose. But I'm not going to do that. And now we're going to do our third round of GenAI processing. So at this point this is where we're going to start introducing a lot of the more details into our case types, we're going to be adding in stages and steps and data objects and all that kind of stuff.

And really translating your world into Pega, into the language of stages and steps that the business. And it can go back and forth and iterate on. That's right, that's right. And so quite a bit of processing here. And one way to also think of this is processing that happens here. Up front is a tremendous amount of time saved down the road.

Right. So that's why we really think that we really spend some good time collaborative effort iterating on Blueprint. You get a lot of payback down the road. All right. So here's our case sites. We have a loan application case. And at this point we can continue to iterate and do some more finer fidelity management of what this case type will look like.

Now right away I can see there is a bit of a minor issue with this. We don't actually have an underwriting stage included. That's probably a mistake from the documentation we submitted. So now we can start iterating and actually using human intervention to start correct some of those things that we got from GenAI.

So I'm going to add in an underwriting stage. I can also add in new steps within this stage to perhaps call that case type. So we have an underwriting case type. I'm going to go in create that case and just call it right. So you can start adding in structure into this into this case Life cycle. You know validate documents.

We have that automation step. Well, as we learned today we have a new Agentic documentation processing capability. So let's go ahead and replace that kind of older automation step with something that's newer. Maybe using some GenAI to handle all those documents. So basically the point here is that we can go in and we can start managing and massaging what this workflow will do for us.

Okay. So we can spend a lot of time here. We can go back and forth, we can iterate, we can arrive at a case life that we really like. But at this point we can go forward. And now what we're going to do is really look more closely at our data and integrations. So data is really critical because, oh, I'm sorry I got ahead of myself, I apologize.

Uh, we wanted to go in into the case type and actually get a lot more detail into our case. Life cycle itself as well. So I mentioned how we have our case hierarchy, right? We, we we added an underwriting step and we're calling that child case. Well this is how we kind of link that together right. So here we can actually establish this case hierarchy where we have a loan application parent case that can call this underwriting child case.

This is where we can actually make that linkage in the settings menu here in Blueprint. Right. So instead of having a a flat kind of case, uh, case concept, now we can start adding in hierarchy and things like that. We can also specify what's required. We can go into our fields and actually say this needs to be required in order to effectively progress this case.

All right. Now I want to stress really strongly at this point. This is not just for bookkeeping. This is not just for creating a design documentation at the end of this process. What will happen at the end is this, as Caroline mentioned, it will create a Blueprint file with all of these instructions.

So all of these specifications, this fine tuning that I just created in here will get carried over when I import that Blueprint into Pega OK. And that is another example of really just the huge time savings that we can achieve with a really proper kind of blueprint process here at the beginning. So now at this point, we're going to go into our data, and now we can actually start working with the actual data objects that service those workflows that we just talked about.

Okay. So we have a number of data objects. These are all created by GenAI or summarized by the documentation and the original material that we submitted into it. And we can do as before additional work on getting this into a better place. So for example, for data objects we can specify a SQL file. So if we have databases or systems of record and we know how they we already have their Other definition we can just take in their SQL file.

Here we also have YAML where if you have an integration endpoint, maybe you know what that looks like. You can import that. And then as Caroline said, you can start translating that into your uh, your application. So I do, for example, have a SQL file here. I'm going to bring that in. And as you did in previous steps, GenAI is going to analyze that SQL file for us.

And this is going to reduce errors. Every time someone looks at an interface, writes it down in word, puts it into JIRA, you lose fidelity and you lose accuracy. What this does is this says these are the exact fields that we need. It's going to map tightly to your interface, and you're not going to have to spend those cycles fixing and correcting and understanding what those data types are.

Yep. Exactly. And we can also do is specify systems of record. So if I know this database comes from a different system that's not Pega, we can just specify it here and start to incorporate that into our application. Okay. So at this point we'll start working our data objects. And like I said before, at each step of the way, this is highly collaborative. We can iterate. We can get to a better place through this Blueprint process. Last but not least, we have personas. So these are the actual end users who will be acting on this end application once it's complete. And as with the other steps, we can go in and do some fine tuning with it. So in the case of personas, what we can do is actually determine what access privileges they have.

So either case access or data access. And even here we can use GenAI to make recommendations on what the access privileges these users can have. And like with the other things this material this this information will also get translated into the Pega app once it's imported and created for us. Okay, so I hope you can start to see how much fine tuning you can really do with the Blueprint.

So I think maybe most of the demos that you've seen with Blueprint so far have kind of been at a high level, but when you really click into it and really dive into it, you can really see the richness that you can achieve with a Blueprint process that you can work together and collaborate on. All right.

So now we're at the end and we can preview it. We've all seen preview. We saw Kerim keynote give a pretty fabulous presentation of what Blueprint preview is really capable of. But what we can do here is actually dive in and start running this case. I want to see what this looks like once I run it. Okay.

So we can go in and right away we can start looking at how this case functions through this landing page. Now one thing I will mention also is if you can kind of snapshot, you can mentally picture what this app looks like. When I do import this Blueprint into the Pega and I start it up for the first time, it will look quite similar to this.

Not completely, but it will look quite similar to this, which I think is pretty impressive. All right. But like I said, we want to be able to go in and actually start looking at some of these case types so I can run my loan application case here. And right away I see an issue. Right. Loan product type is just a simple, mundane text field, right? That doesn't really give us much.

Right. We want this to be something more prescriptive and iterative, right? We want this to be able to go in and say, this is what this loan product actually is. So this is easily fixed. We can actually go back into our Blueprint and make these changes. So one thing I'll highlight here is when we go back to this user step where we where we saw in the preview, we now have the ability to see all of the fields for each user step.

And this was recommended for us by GenAI or something that we manually did throughout this Blueprint process. So we can see that loan prototype is here. We can add edit. We can continue to to manage this information here. But at this point I want to be able to go in and change the definition of this field.

Right. Right now this is just a simple text field. So we need to be able to modify this to be something different. So I'm going to go leave this. And then what I need to do is actually go into the case data for this workflow. Open up loan product type. and we can see that the field type is text. So let's just go down.

Change that to a data reference. Have it reference loan data and then off we go. Now we've just like that. We've changed the type of this field in our Blueprint. And so after all these changes now you can go back to preview. So skip ahead. We go back to our persona step. We open up Preview My app. And now we can run that workflow again. Now we can see what the impact of our changes has been. So sure enough we see loom prototype is now a drop down right. So now we're getting some data coming in from that data object. So let's run and see what it looks like. But that looks pretty bad right. That is just random numbers. So that is not the name of a product right.

That is a different data field. In fact it's the amount it's the amount of our sample data that we've already injected into the system that represents this loan data type. All right. So we have more work to do right. So let's go ahead and close this down. And once again we can iterate right. So we can go back to our data integrations.

Open this up. And now we're actually going to do a little bit of work on our data object. So let's open up loan data. And what we can do is then just edit the data model. And what a lot of folks may not know is that the ordering of the fields here actually matters. Right. So you see at the top you see amount is the highest position field.

And that's what we saw in the data reference. That's what you saw in the case ID in the preview when that ran. So in order to adjust that priority, that ordering, all we need to do now is just drag product up to the top. And now our product name will be the top reference field within our data object.

So to prove this we can go ahead and close this out, save it, and then go back into our preview mode and be able to look at this again. Okay. So as I go through this, this is admittedly a little bit of a trivial example, right? We're just doing a little bit of manipulation with the data objects. But I think you can see how through this process of testing it on a preview, looking at what it does, going back and refining your Blueprint, you can get a lot closer to what your finished product might want to look like, what your finished app could look like, right? And also in preview mode, of course, you can see other things like the customer data records, the loan application records.

You saw our great dashboards that we think we can start building into this Pega application. All right. So that's the Blueprint process. So at this point I want to switch over and now migrate this Blueprint into an actual Pega Infinity application. So now we're here in the summary page we have our entire app.

And what I can do now is actually download the Blueprint. And as Caroline said, this Blueprint file is just a set of instructions. It's a set of instructions that Pega Infinity knows and understands and can interpret in order to now create our Pega application. Um, so let me pause here for a second.

Quick, quick check of hands. How many folks here have actually imported a Blueprint into a Pega application? Patient one. 234. All right. These lights are really bright, so I really can't see very well. But I think just a few. Just a few people. Okay. We'll go with that. So so this is actually pretty exciting then because this is incredibly powerful stuff that we think we can show here.

So we import this Blueprint. And now we're going to go through an Infinity process to basically interpret that Blueprint and understand how to build this application. Now the first thing you can see here is what is the built on application. So it defaults to Pega Platform right which is our core system.

But what I want to do instead is build on an enterprise reuse layer or some other layer that has more global artifacts that we might want to leverage in this application. Things like data objects, reusable Constellation components, things like that that we may want to reuse. So we press ahead. We see that our case types.

Sure enough, now we have a choice. We can either build or not build, right? Even still, here we have the choice of what to do with this Blueprint. same thing with data objects, but because we built in that reuse layer, and that reuse layer has a customer data object in it, we have a decision to make.

We can either replace that customer data object in this app with what was from the Blueprint, or we can reuse what was already there for us in that reuse layer. And that's exactly what I'm doing here. I'm choosing to take advantage of, reuse and use what was already there in that built on application that we have.

Here's our personas moving along. And then of course, our application setup. This is where we can have a little bit more fine tuning of our class structure, our data structures, things like that, so that we have all the information that we need in order to properly create this application. So at this point I'm going to click submit and off we go.

Now at this point there's a lot of magic happening. You see that it's kind of small but you see total rules created. I sped up this video. But this number is incrementing pretty fast right? All those are all Pega rules in Pega Infinity that are being created for this application and the system knows how to create those rules and what kind of rules to create based on the instructions that it receives from that Blueprint file.

So when this is done, you're not going to have an empty app. You're not going to have just a skeleton application to start from. You're going to have an already pretty richly defined application that you get directly from your blueprint that you created. And you don't need any user stories for what's required and what's not.

And you've already done some amount of troubleshooting, right? In Blueprint. That's pretty powerful stuff. I think it is. All right. So here's our app. Okay. So freshly imported retail loan origination. Now what I can do is if you remember what we saw in the preview mode. Now let's go look at what it looks like in preview mode here.

For real right. So I clicked on preview. And now this is what our end user experience looks like. You know pretty close right. It's not too bad. And now I can run loan application. Here's our case. You see the required fields that are there. We specify that in the Blueprint we have our data reference working with product loan that showed up.

So all that stuff, all that, all that work that we put into the Blueprint is realized here. We don't have to re-implement this now within Pega Infinity. Now, obviously these views may not be exactly what you want. Totally fine. Right? This is where now the design process went. Infinity can take over, but we see that we have such a huge head start with a functional application.

Thanks to Blueprint and thanks to that Blueprint import process. We also have data. This is sample data that was injected into the system by Blueprint just to help us with testing, you know, and making sure that the app runs correctly. So we can go through here. We see all these records landing pages.

We know we have a pretty rich app that was already created for us. But, you know, no one's under any illusion that you can now just press the Magic Deploy button and we'll push it out to production. Right? Maybe that day will come, but that day is probably not here right now. Right? Um, so that's where the GenAI capabilities that are built into App Studio now come into play. Okay, so within App Studio, pretty much all the capabilities that we have are wrapped into an umbrella term that we call Autopilot. And Autopilot is this capability that really is kind of just spread everywhere. You know, sometimes a little bit subtly throughout the application design experience. One example of that is User Stories.

Caroline mentioned how she had a previous life in it and how she was building user stories. Well, what you may not know is that Pega fully supports that embedded into the application. And here we see a whole series of user stories in the to do column of GenAI created stories that we recommend that we take.

A lot of these are going to be review steps like check this user assignment to make sure that the view is correct. You need to build in business rules for this automation. You need to add in this check this, things like that. So we can go through here and just start looking through these user stories.

And this is how we can kind of manage what we recommend that you do in order to progress the development of this application. So I open up one of these, for example. And on the right you see here's the description of the user story. We can also see the acceptance criteria right. This is all created for us automatically by the system.

And it's kind of our recommendations of what you need to take in order to finish the app. So at this point, let's say I want to be able to take one of those user stories, just drag them over, drag and drop into doing. And we see that the bar kind of updated to be 2% now being worked on. So we're making progress here.

Now I open up Autopilot. So on the right column this is now the conversational interface with Autopilot. So remember how I described that Autopilot is kind of like our universal umbrella term for the design time. GenAI capabilities. Well this is now the conversational interface of that right here. So let's say I want to just understand well how do I add business logic for an approval step.

Right. Maybe that's one of those user stories that was recommended to me. I can go in and type that question and then Autopilot absorbs all this information from Pega community and other sources to give you a pretty reasonable best practice answer. Okay, so this is kind of very useful if you're kind of stuck and you're not sure where to go.

You know, just call an Autopilot and ask it a question and see what it comes back with and it'll probably help you. All right. So now we're going through our design. We're building out our application. Um, but you know, maybe we just forgot something in our blueprint. It happens right now. You could go back and build another blueprint, import it into this.

That'd be totally fine. But let's say we need to create another case type, right? Maybe a simple one around document management. Fine. So at this point we can still obviously create cases directly in App Studio itself. Right. That hasn't changed. But we've now appended additional app Autopilot capabilities into this.

So just like Blueprint uses GenAI to create the stages and steps, so does Autopilot. Here in App Studio, you can still create a full GenAI created stages and steps for this case type along with the case type. You also have the data. So again like before this is all fully editable. We can go in and iterate on that. But it gives you a great starting point in which to build your case type. Now, one nuance with case types that are created in this method versus case types that are created from Blueprint is that you don't get the view. The view is created for you. So here we need to go in. Let's go into one of the assignment steps that was created for us through Autopilot.

And again you see on the on the right we see add fields with Autopilot. So again, kind of subtle Autopilot is kind of embedded everywhere in the App Studio experience. But we can call upon Autopilot to recommend what fields should be populated into this view for us to use in order to build out this assignment step.

And sure enough, for this assignment step, verify document completeness. We have a pretty reasonable set of fields that we can add here. And of course, obviously we can edit and iterate as we need. All right. So we're kind of working on this app. Things are looking pretty good. We're taking advantage of Autopilot to help speed development.

Um, now at this point what we can do is go in and start taking a look at some other things that we that we're able to do. So, for example, uh, as we continue to work, um, maybe we need to go in and start looking at testing. All right. So we get to a point where our app is complete. We have a new capability Infinity 25 where we can actually generate tests.

Now this is a new thing. Infinity 25. We have a booth dedicated to this in the innovation Hub. But based on this case type for loan application we can go in here, click generate these tests. And it generates these cucumber test scripts that we can now import and use in any kind of automated testing system for us.

All right. So this is kind of like a really fast kind of whirlwind tour of a lot of the capabilities that we have. But you can see how we've used AI throughout the entire SDLC from Blueprint to Blueprint import to design time, experience to testing. Okay, so like I said, a lot of covered here, a lot of capabilities, very powerful stuff.

If you have any questions like talk to me outside in the hallway, um, or we can help you find the expert that you need to to get a better understanding of this. Awesome. Well, thank you, Brian. And if you have any questions, please feel free to come up to the mics. You're absolutely welcome to ask them right now.

If we don't have any questions, we'll start to wrap up. What I want to share with this group is we want to see every Pega client go this fast or faster. Eight times is a particular number that came from one study with a partner. You can find that study on pega.com and it will tell you what the details are.

But we want everybody to experience the effect of everything that we're putting into Infinity. This particular quote came from, you know, a business analyst at a large European Telecom. And the things that I highlighted are those things that I think are incredibly important to have the attitude that rapid prototyping will surface, where you don't have a shared experience, where you're talking right past your business stakeholders, or you're talking right past it.

It's going to be working right in front of you, like Brian showed us, to the point where you can almost start to troubleshoot right in Blueprint that attitude of rapidly prototyping so that you're always talking about working software instead of documents and Excel spreadsheets is really part of the magic. But the other thing that's highlighted on this slide is working together. One of the things that is, you know, in striking focus is that you can generate code with AI very easily, but how do you translate that to actual speed? And the way you translate that to actual speed is working together. It's still that human element.

I know we're talking about AI, but there's the human element that lets people work together, not do the work that's just drudgery, not do the work. That's just mapping things. Use AI to take that out of the equation, so that your teams are working effectively together, and you can focus on the communication so that you're not talking past anybody.

That's really essential to the magic of all of this, because all we can give you is technology and tools. And if you still don't believe us because we know PegaWorld, we all get excited. We all hear a lot of exciting things. We promise that people are actually doing this today. We're seeing, you know, rollouts to 15,000 plus users in a matter of weeks.

And we want this for you. So we're just going to, you know, bore you with one more one more example, this person you heard from yesterday and the things that I highlighted in this quote are that structure is what translates to speed, structure and guidance is what gets you that velocity down the line.

Throwing things over the wall doesn't work, and we know that. Does anyone ever seen a project go well where you got requirements thrown over at you? Yeah, it doesn't work, but Blueprint lets people who may not be quite as technical participate in what is really building your application. You're getting started in a massively productive way, because there's nothing in your blueprint that's wasted, even if you don't build it right away.

If it's not part of your MLP, you saw how Brian can have fine grained control over what he imports and when he imports it, and how he layers it onto existing application stacks. But it's that structure in the blueprint that makes it so that no conversation is wasted, that everything you talk about with your business stakeholders immediately goes into a model.

And that model driven development is really, you know, peg is bread and butter that you've all been familiar with. And now we've laid down these tools that help you go that much faster. So we have some time for questions if anybody has any. Yeah. Go ahead. Fantastic presentation. Really loud. Um. Two questions.

One is, uh, obviously this stuff is evolving rapidly, right? Very, very quickly with Blueprint Blueprint import. Where do we go to get the most up to date view into the capabilities? Um, you know, get part of the conversation around leveraging it. Is there like, where where would I go? Well, absolutely.

You can get onto Pega.com. Blueprint Blueprint is evolving and it is sometimes nuanced, as Brian showed us. And so understanding all of that can be difficult. So if you're midway on a Blueprint, you might have a little surprise. But if you want to learn more about it, what I would say is you should absolutely join one of the expert circles.

You should get onto community. You got to get involved. Because if you have feedback for us, we have our product team sitting here. He wants to hear from you. We want people to be engaged. So if you build a Blueprint and you have questions, contact your account team. If you import it and you don't get the results that you expect, contact Pega. We want to hear where it's not working for you because this isn't just hype to us. We are starting to see workflows go in rapidly, and the idea being that you don't need to have systems that that are forever, systems that you just kind of tweak because they're so brittle. We want you to be able to stand up a workflow.

If you have an emergency that you need to serve your business for, and tear it down as quickly as you stood it up because you might not need it anymore, people might not know. But one of the things that Pega does every year is if there are national emergencies and governments across the world, they often come to Pega to stand up a very fast application so that they can service their citizens and get payments out to them and services out to them.

That's one of the things that the latest architecture is really good at, and we want you to get the benefits of it too. So hopefully that answered your question, but if you ever need contact with Pega, you can always reach out to your account team. Get on to community and we want to hear from you. Thank you.

Other questions. Yeah. Yeah. So definitely great presentation Brian and Carolyn. It's exciting to see what you've presented. What question I have is like from a SDLC perspective as we have inception analysis, design, build, test, deploy with the Blueprint what you just presented, how do you break it down among the business analysts and the developers and the testers? I love that question.

Thank you for asking it. Um, I've always, you know, been somebody who loves to use software. I was like four when I started playing around with computers, and I was immediately sucked in. Not everyone has that comfort level, and some people are a little bit afraid of it. Or they, you know, you have business stakeholders who feel like someone will judge them if they're not a technical person.

What I would say is that's what to work on, because the AI is going to take out the documentation for you. So have lunch. Go meet with your NBA at Pega. We're having all our lbas get into App Studio. We're going to be developing live with clients, and then we're going to be handing off the acceptance criteria over to SSAs essays.

Lsas that can't be accomplished live when we import and you get to that class screen. I personally believe that you should have your LBA sitting right next to your LSA or PSA, making sure those class structures are right, because the speed that you get will be diminished if you have to refactor. So the point in the kind of the theme to your point that runs through all of this is do it right once, get it right the first time.

You can always go back and change it. You can always go back and add more. But I do think that in that particular case, Lsas Lbas, the Lsas can move on to very rapidly standing up user management. If you're doing like a. Net new Pega app, we always need some single sign on. We always need email accounts.

Let your LSA get all of that figured out. Have your SSA stand up your merge pipeline. I believe that the deployment pipeline is critically important to going fast. Everyone should be adopting the merge pipeline if they can. And when you do those things together, your Lbas can be working with your clients and you have three parallel tracks of activity going on to rapidly assemble your build.

And that's what we have seen. That really expedites things is when you have parallel work tracks and you don't have SSAs or Lsas waiting for requirements, waiting for that permission to build. Everyone has permission right at the jump with Blueprint. Get in there. Understand what's going on. Brian also showed us some security features. Has anyone ever created roles to objects in Infinity Platform few hands. All right. Yeah. It's not that fun, right? It's not that fun. You can get through a whole workflow. You think you're in good shape, you're ready to demo, but oh, shoot, you forgot to secure your workflow. What? Blueprint is trying to do is, like I said, get everything stubbed out, get it all foundationally planned, and then you can iterate on it.

Does that answer your question? That does. I was going to ask, Will this also help to eliminate Pega Azure App Studio. Well, you can absolutely use Agile Workbench by itself. I personally like to use Agile Studio, and the reason I like to use Agile Studio is sometimes the development environment is a little bit much for some people, and they might get a little bit lost or they might have to expand things.

So I personally love Agile Studio because you can keep them in sync. You can be using your user stories, you know, doing any check ins and syncing it back to Agile Studio. But Agile Studio is a traditional kind of project management tool that people feel very comfortable and it's very straightforward.

So I personally love it. You can integrate with JIRA if you'd like. You can export to Excel. So if you download that backlog and you think I need to get that over to JIRA, just drop it into Excel and import. Yeah. Other questions? Yeah. So how do we use Blueprint for Pega legacy application to convert into Pega? Infinity version.

Can you use. Blueprint to convert legacy applications into new applications? Um, that's a great question. And that's one that we're we're absolutely working on. You can use it as a tool. And we would suggest it. We would say, hey, you could possibly export your existing Pega application if you if you're in case designer, you can export it to a Blueprint.

And you can just like any file, import a Blueprint into a Blueprint. Um, it's not fit for purpose. Designed for that just yet. Um, but I think as we think about it, what we call that at Pega is heritage, um, modernization. So you have a heritage Pega app that you're modernizing. What I would say is use use the ideas that Blueprint gives you, but don't get hung up on it, because if you're building something that you have, you need to add value to it for it to be worth it unless you have something like a strict CSP requirement coming at you, which is a requirement that.

You know, it's a security requirement that only modern UI can can achieve. And you would need to transition for that. But just like anything else, like when a new iPhone comes out, we don't throw away our iPhones and go all buy the new iPhone. We're not asking people to transition applications that are in good shape, that are doing what they need to be doing, and that are serving your businesses, so you may or may not want to actually do that, but you can.

Yeah. To expand on that just a little bit, there was a session yesterday, Rahul Ashok and Stu Smith from our as a service team presented on that topic. So when the sessions come out, I recommend going and finding the as a service upgrade session. They talked about an alpha tool. Um, it's very alpha.

It's called signature. And essentially it will extract the key aspects of an existing Pega application so that you can reimagine that through Blueprint. Um, we're we're trialing it with some internal things and in one client right now. But since Rahul announced it, I figured I could announce it to this group as well. But go and look at that session and then contact Rahul if you have questions. Not. Not Caroline. Thank you. Other questions? Yeah. Go for it. So we have an existing application, and, uh, we have 100 stories in backlog in DevOps. So can we use any way for this, um, this tool for the the future development? I'm going to say that back to you.

And you correct me if I get it wrong. You have you have an application. It has a backlog of about 100 items. And you want to know how you could possibly leverage Blueprint and the tools that we're sharing. Okay. Is it traditional UI? Traditional UI? Who's mostly on traditional UI in this room? Are we Constellation are we? Traditional EY are a lot of traditional EY OK.

All right, so this is a deep question. We're going to have follow up and if you need help, please contact Pega and we will get you help. Um it's actually pretty easy. What you're going to do is you're going to use Blueprint, get those 100 requirements into a Blueprint and see what it tells you, or break them up in logical groupings and get them into Blueprint and start to lay out your workflows.

While you're doing that, what you're going to want to do is stand up blended UI. So for Pega Platform we call it blended UI. It is a built on application. So you layer a modern Pega app right on top of your traditional app using the built on application feature. And then what you're going to be able to do is you're going to be able to expose all of your existing traditional workflows in your new Constellation portal.

Coming in Infinity 25, we have a one click migration wizard that's going to help you do this. So you'll see that coming out soon, but then you're going to Blueprint your new workflow, and you're going to leave your traditional workflow alone unless there's a good reason to change it. What I've seen people do is they kind of carve out specific use cases and they get comfortable in Constellation first, their teams need a time to adjust.

There is an adjustment period. Has anybody tried Constellation and felt the adjustment period that happened to me? Yeah, I see a couple hands. I'll be I'll be transparent and vulnerable with you. When I first got my hands on Constellation in 2020, it was a rude awakening for me. It was totally different than traditional is the way it felt.

That is what I felt. I had been developing in Pega for about ten years, day in, day out. I was really comfortable in traditional UI and when I got my hands on Constellation, I thought, oh geez, they broke the platform. So I called up the guys on the third floor and they they walked me through the ideas and about two weeks later I thought, oh my goodness.

They fixed all the mistakes I used to make on a regular basis with Constellation. This is fantastic. And so I ask everybody before and after their their transition period. Would you ever go back? And I have not had a single SSA, SSA NBA say that they would go back. So in that case I would recommend blended UI.

If you're a Customer Service Pega client, you use customer service. You're going to be using what we call coexistence, which is a different architecture style for achieving the same thing, which is we want to reuse all the stuff that we have. We want to surface all the legacy workflow that we have in modern portals, so that our users are starting to transition and get used to the new stuff, and then anything new, we want it to have the longest runway into the future.

We have Pega apps built in our back office, and our CIO is actually in the room today that are 20 years old. That is massive value. We don't want to see you lose that value. Your application lifetime value is incredibly important. If you need to do new stuff to give it the longest runway into the future is critical.

You adopt the latest architecture because it's going to meet modern expectations. And that's really important because five years from now, we don't know what the world will be like. AI is going to change it very dramatically. But what we do know is we are going to start to see systems from 2000 2010.

They are going to stop being able to meet modern expectations, whether it's a user's expectation of the system or another lens on the system. And so by starting with the latest, you give yourself that future as much as you possibly can. Does that make sense? Yeah. Thank you. We are at time. If you have any questions, please find us in the Innovation Hub.

Reach out to us. Reach out through your account teams. We'd love to hear from you. We really do want to hear. If you go faster, you can always get in touch. And we would love to do a case study with you. Have a great day!.