PegaWorld 2026: High-Performance Pega Transformation: The AI Blueprint in Action

Good afternoon everyone. Thank you for joining us today. My name is Rahul Ashok. I'm the vice president of cloud migration as well as modernization at Pega joined by Stu. Hi everyone. I'm Stu Smith, I'm the director of Modernization Success. So looking to our mission is to make sure that all of you have got existing Pega apps out there driving the maximum value for your investment in Pega. And that truly is a Pega transformation. And that's what we're going to get into. So I had a great keynote this morning, and I think some of the points that Nick Nadgauda and Sheila were talking about are directly related to what we're going to talk about. So before we get into that, I'm a bit of a student of history, and Stu and I were talking about this AI revolution that's going on. Stu, there was a revolution a couple of hundred years ago where you're from, right?

And can you can you share a little story about that. Yeah, absolutely. So you can probably tell from my accent originally from the UK, now I live in Canada and 300 years ago a fellow Brit by the name of James Watt. He had his at this moment in time, we're starting right at the start of the very beginning of the Industrial Revolution. And he at. He's had his fingertips at the time. The best technology could possibly think of happened to be a new patent for a steam engine that was about to go and change the whole of the Industrial Revolution. But you know what? Even though he had the best technology at the time, he couldn't make it work. He couldn't actually go out there and get people to, to, to sell it. And his clients at the time, they were well, typically mines, coal mines, tin mines up and down Britain.

And he just couldn't get that technology out there because he was talking about piston ratios and separate cylinders. I just wasn't really resonating with his clients. But you know, what was resonating with the clients, what really they cared about. The precious resource for them was horses and the horses that ran there. So he came up with the term horse power as something that meant something to them as an organization. And obviously, that's a term that we still live with today. The reason I want to tell this story is because for three points, one, that decision that was made nearly 300 years ago is something we all live with today. We all use that that phrase still horse power in the age of Teslas and everything else. The second point was it was never about the technology. It was about the outcomes that it brought to the business.

And the third, it's down to people. People are and people in this room today and the ones that can make the difference. Absolutely, Stu. So as we get into our session today, the link back there is we're hearing everything about AI. All of us are worried, what's AI going to mean? What's it going to do? And what I find is like, we're still struggling to find the value and the why of, of what AI can do. And the, the gap is just growing faster and faster. Right? Everyone's got this urgency. Board of directors are telling their CEOs, you must do 50% more efficiency with AI. That's rippling down everywhere. But I'm still not seeing real broad adoption of that in highly regulated markets in where you have to do predictability and audibility. The stuff that Alan talked about this morning. But this is real, very, very real.

And clients that are moving faster are able to really change the way their business works. And for us, we believe that, you know, anyone, everything that we think is going to be run by AI is a far, far future. And in order to really get us, you already have the foundation of everything to build with Pega today. We at Pega have been running workflows for over 40 years. What we're doing is infusing the power of AI with the power of predictability built on everything that we have with Pega. So I'm going to say yes, but if I can go back to the previous slide a second, please. So yes, but anything can be done with Pega with anything can be done with AI in days. Of course it can. But what about the difference between enterprise execution and a scientific sandbox? And just a few demos?

It's easy to set up, and I think the reality here that enterprises are stuck with a few things. Legacy complexity. Absolutely. Compliance and standards. How to align business and IT. But also to think about how we orchestrate across multiple systems people. That's the reality of what our clients are dealing with today. And I think that's a very different story we need to be talking about. Absolutely. And again, if we talk about the reality of we know before we talk about the future and where we can head, let's talk about some patterns that we know absolutely don't work. So first of all, it's really tempting just to take some AI and just bolt it onto your existing systems. That sounds great. That sounds easy, right? But it's not really solving the problem because all you're doing is funneling the problem back into AI. That's not predictable.

That's not going to give you consistent answers. And then ultimately, it's got to be people that come back and have to sort that out. So again, that's not going to work. Secondly is about assuming that modernization is something you just do as a one off. It's not. Modernization needs to be continuous. We all know how far and quickly the AI models and the AI world is transforming us. We've got to continue to be once modern, always modern, and to keep up. And I find it really interesting that even from Microsoft's own research, they came out, they did some studies with the very premier models that we're talking about, the clods of this world. And they put it they put some studies out there based upon taking some documentation and the intent from that, and found that 25% of the intent that came from that documentation just ended up being corrupted.

It wasn't usable. And that's using the very top models. If they used more generic models out there, they found that 50% of them ended up corrupted. So Microsoft came back and said, we just don't think it's quite ready for delegated workflows at this moment in time. Now, obviously, they got some pushback from that, saying, is Microsoft really saying that? So they came back and clarified and said, well, we're not really saying that AI is not ready. We're just saying it needs to have more of a structure, more of a control. Doesn't that sound familiar? Yeah, I think so. I think it sounds something like the foundation that you all already have. So if you're an existing Pega client, you already have the foundation for workflow. It's your business knowledge, your business rules, and what we want to what Sue and I are going to talk about is how do you take your existing application, accelerate it with all the AI features and drive that Agentic feature.

So that's the plan that we've built. We're going to share that. I think we were here last year talking about this, and I'm glad to say that we're going to share some stories about clients who've actually achieved that today as well. So what what happens? Right? If you are a Pega client, you've had your Pega application for a long time. When you first start your Pega build, you're really excited. There's a lot of stuff that you believe you can get done over time, priorities change. Something different happened. And that's where we we call it an execution gap between what you can do with Pega and what you're actually doing with Pega. And what we find is with all the innovation that Kerim showed today, you're wondering, how do I get to use all that in 26.1 when that becomes available? What's the best way to do it?

And that gap is just widening. So we have an approach to make sure that that gets done. But before we get to the technology, I think there's a piece of it that we'll we'll talk about an approach. The architecture is all here. But that top line over there, right? Why are we doing it? I think the business outcome, going back to the story, what will resonate to the business? What will why are why is this whole AI journey important? Are your customers getting to engage with you in the way they want? Are your reps and employees getting the efficiency they want? Are you automating the processes they want? All that is really critical in order to really get that outcome that I think is still missing out there for the for the majority of the of our clients. Um, and in order to do that one thing, so Stu and I have been part of our group for a couple of years.

Uh, I talked to a couple of clients today in order to get to an AI system, fundamentally, you need to be able to focus your efforts on the innovation. That's what it's about because it's a completely new way of doing things. What you don't want to worry about is are you running Pega appropriately? If you're on prem and you want to use 26, you've got to upgrade your system, get new instances, a whole lot of stuff. So our recommendation is step one, make sure you're using Pega as a service. Focus on the innovation. And we have a very prescriptive way of getting this done for anybody who's not done that. Hey Rahul, can I ask you a question though? Isn't it true though doesn't you don't have to be on Pega as a service to you. You can be on premise. It's still going to work, isn't it? 100%.

So if you're on prem and you have a really good CI CD pipeline. You're keeping up to date. You're on the latest version. Pega releases 26 and on prem you have a really robust way of getting to the latest version. No problem. And I'll just say it very few of our clients are actually able to do that. That's my experience and that's why we did the whole focus on the. Isn't a statistic three and a half times more likely to be on a current release on Pegasus service than those who are not? Yes, it absolutely is astounding. Yes. And 50% less production issues when you're on as a service versus you're on, on, on prem. All right. So with that, what's our approach to? Well, I think before we go on a journey, we have to work out where we are to begin with. And so when we look at it, this is not just through the technology lens.

You've got to be looking at it through the business. We purposely put that right at the top of the triangle here, operations and technology. I'll hasten to add here, when we're talking about operations, we're talking about tech ops. We're not talking about the business operations point of view. But in our experience to be successful, you have to have a good combination of all of those three elements. We've tried it in the past. Let's be candid about where we have made mistakes when we just focus it on it through a technology lens, we know we cannot get the impact and the changes we're looking for. So one of the first things we do is actually look at the client's maturity at a moment in time and see, is it balanced across the board or where is there gaps in this one? And this particular example, you can see it's more skewed towards the technology side.

So they're doing well on that, but far from where they need to be from a business point of view. And that's something that needs to be addressed. And then we can look at that in a bit more detail. And we look at this through this more maturity assessment. Now don't look at that slide and be too worried about the individual dimensions on there about, you know, you know, whether you need to have 18, 19 dimensions. What we're trying to do is give a view to a client, and we can do this incredibly quickly about how far they are down this road of being able to take advantage of all of this genetic business capability. And if we can just use an example, in the past, we probably may have looked at this client and said, hey, this is a pretty modern client here. You know, they were on Pega Customer Service.

They're on our latest GA release. They're doing pretty well from a security point of view. And you can see they've done a lot of investment into more of the operations and technology side, but there's a lot that's missing from the business side of here. So when we look at this, it gives us a very quick and easy path as to what's the bits we need to focus on first in order to start having the client take advantage of all this amazing capability that's going forward. Yeah. And you'd think you look at this and you're like, well, why are we doing this? So I've been at Pega for over 20 years. I've had a background as an LSA in the field. I've done lots of different roles, and I've done modernization of some of our existing clients as well. And what I find is that without a lens like this, people are wondering, hey, are we doing the right thing?

Which area should be focused on? Are we solving the right problem? This gives you a framework to think about like what's important. And I think that's the gap between us just going, doing a technology solution, but not focusing on the right problem. So this really helps you identify the problem area. And it takes about 30 minutes to do. Maybe it's a pretty fast process and we have stuff that we can share around that. Yeah. If we haven't done this with you as a client or a partner out there and you want us to do it, it's very, very quick and easy to do. But that's the as is. This is where the client is at this moment in time. What about the to-be? Where are we heading? So this is something I'm passionate about that we absolutely align. This is where you are, but this is where you are going from a business point of view and the capability that Pega can deliver to you and your business outcomes.

So this outcome aligned roadmap is almost, it's a ticket to the game for us moving forward. Again, taking it away from just being a scientific sandbox and making sure we're getting true enterprise execution on a genetic here. So this is purely obviously an example. The text that's on the slide is just that's not important. The important thing is you can note that it's about business and operational advantages. Where is that business going. It's also about the benefits that come. And almost the technology is just an afterthought. That's the bit that's underneath just in those purple little boxes here. One thing to note here is that people come and they expect that they maybe have an app that's five, ten, 15. In one case, we've had an app that's 30 years old. And that expectation is it's going to be a huge long path to be able to take advantage of all you saw at the keynotes today in the best of Pega, the message from us is that we have a roadmap.

Every roadmap we have includes a genetic in here, and we can do it incredibly fast and incredibly cost effectively to build on the foundations you've got there and give you that genetic future. Yeah. And S2 has a really great line in there. He talks about the existing platform carries substantial untapped potential. I truly believe that there's a lot of functionality within Pega. I think most clients maybe use 30, 40% of it even as is, and we're doing even more, right? So the roadmap, what it does is it gives you a framework to have the conversation of what to modernize or what, where the transformation is going to go. Without something like this. You don't get alignment up front and it just causes churn in us to lose time. That's that's been our experience. All right. So all that sounds really good, right? How do you do it?

So Blueprint is the way for us in the future. We have created a tool called Application Signature Tool. This is available in marketplace today. We released it in January. We're doing updates to it pretty much in sync with Blueprint. And what App signature allows you to do is you install it just like any other product in Pega. So if you're a developer, you can download it from marketplace, install it in your current environment and app signature. When you run it, it will give you all the parts of what you would need to know about the application. So one of the common questions that people have been asking is Blueprint is great. How do we use it with our current existing application? This is the answer. So you can download Pega app signature from marketplace as long as your current version is 7.1.6 and higher. You can run it and you can immediately import it into Blueprint.

Yeah, I think at that point I'm speaking to a client over lunch and we said, how much are you using Blueprint? And it went, not really that much because we haven't been doing any new workflows recently. They've assumed that Blueprint is only for their old, so new workflows coming in and not something they can use with their existing workflows. So that's really interesting. And this is really a game changer because a couple of scenarios, right? A lot of times you have an old Pega app, 12, 13 years old and it's working a certain way. That's the impression of what Pega can do, which is far from truth after this time. So you get app signature, you look at the application and now you can see your as is app in Blueprint, and even look at that preview button and it'll look different than yours. But that's how it would look in a modern paradigm.

So you have that visibility of current state. And what this does is it creates that Pega app signature file. you get to import it and it creates the high fidelity Blueprint. At this point, you have a couple of options. You can do what we call the Blueprint brainstorming. We call it a blueprint workshop. You know, the idea is fundamental and core to how Pega has been operating for many years, which is bring in your IT, bring in your business, come together, look at the blueprint and reimagine. How would you do it? The chances are you would not rebuild the workflow today the way you had it 15 years ago or ten years ago, and that's where the magic happens. So as you do that, you can then start reimagining it. And in Blueprint, when you import the blueprint and you go to Pega.com with blueprint, there's an option to do a reimagination.

So I have a video. I was hoping to have some more ability to adjust it and pause, but I don't have access to it. So it's about a three minute video. It's going to go very quickly. It's going to show you what you can do in three months, in three minutes. So it's going to like run by. I'll try and pause in and we can ask some questions. But in the Blueprint, what you're going to see is we have an old app. It doesn't look old. Like if you look at the UI, it's going to look pretty neat. But beneath that, what you have is the old non case management case work objects. For those of you who are technical older paradigm, you cannot use the case management. You don't have access to any of the new features. We're going to take that. We're going to import it using app signature.

Then we'll show you exactly what Kerim showed you on stage today in terms of the way it looks in Blueprint with the data, the integrations, we're going to reimagine it, import it back, and then have an agentic conversation for the same workflow. So it's all that in about three minutes. So it's super compressed. We do have a booth at the innovation center. We can give you more details if anyone's interested in how that works. So let's see that and then I'll come back to that one. Is it working? Is it running? Uh, yeah. Not yet. Try again. There it is. All right, so here we go. It's, uh, running the application. It's a loan submission process. The UI looks fairly clean. Doesn't look too bad. They're just doing an employment status. Annual income. Entering the information. Here's the case. Life cycle that it looks like.

But if you look behind the scenes, if anyone's done Pega, that's kind of the non case type that's working behind it. I don't think I can pause it so I'll let it continue. Um, you go when you run the app signature, it shows you I wish I could can I pause it. I'm going to try. Oh it did work. All right. So over there, when you run the app signature, two things we recommend running app signature in production. And the reason we ask you to run it in production is because over time, the design time build of Pega and the runtime build are very different, because people have come in and built tons of rules in the system. Maybe 40% are actually being used. So by running it in production, what the app signature tool does is says, okay, what cases are actually being used?

What are the rules that were executed on the execution path for those rules? And then you can select the case types that you want to reimagine, because you don't want to do a two year full blown modernization that just will not get any ROI immediately. Everyone wants to see ROI immediately. What can you show me in three months? Not three years. Right. So our recommendation is pick 1 or 2 case types, import them into Blueprint and use that. So that's what they're doing here. Let's see if this plays and I don't have to play it from beginning. All right. There. And then in Blueprint I'm going to pause it again. You have the ability just like you would for any non Pega application Under the code analysis document. You drag and drop and you put it in. Put your Blueprint the app signature output right there.

If you have additional documents like you've built training documents for your users, you've built any additional documentation outside the system. You can upload it all because it's just going to enrich the blueprint that you that you develop. Let's see. All right. So we download it. And that went over really fast too, but it articulated all the case types. So here I'm going to pause again. So it detected that there's a loan submission use case, a customer verification loan disbursement loan loan closure. And as you come in here there's your application as built today in Blueprint. It's got the case data model. So all the data objects that are being used are pulled in. It's got the air model. So you can see what the data entity relationship looks like. It will also get into the. Let's see next, looking at different use cases, it'll also get the specific integrations that are being used coming up soon.

There it is. And you see this is the same same view that Kerim showed this morning. Right? So this is all live in Blueprint today. Everything I'm talking about, you guys can do right now. Like if you go and install it from marketplace, you can do all of this today. Um, and once you do that, all the key components of a case type, personas, data integration, all of that is in here and within, within the persona setting, you can also do all the stuff that we talked about today in terms of data access, channels, personas, editing it, and I think, and the preview functionality, which I personally love because it looks, this is for those of you who, you know, there's always question, how will my app move to Constellation? Well, you do this and you import the app back in. It's a Constellation app.

It's not as simple. There will be things to do, but this is a much faster track track to getting your applications modernized in a faster way. So allows you to preview. You can use all the same vibe coding Agentic AI features in Blueprint with your existing app. And now this is a neat feature. So it went over really quickly. But as you import it, you'll see on the top right that in Blueprint, it'll identify that the this Blueprint, maybe it's not in this one, but in Blueprint, it'll identify that it's an app signature Blueprint. And that allows you and gives you an option to reimagine. So in Blueprint, you can click that and you can reimagine what did I. I restarted the app. Oh man. That sucks. That's why I didn't want. To have to say it all again. Now I've got to sit in on it.

Two minutes. No, I don't know if I can do that. All right. So it will you can. I'll just talk so you can reimagine your workflow at that stage. And once you reimagine the the workflow, it will actually show you and you can vibe code it and you can say, hey, here's my existing workflow. What are the different agentic steps that I perhaps could do as part of the process? And it will identify the areas in your workflow that could use the Agentic. AI. So this is a loan and a processing loan loan application with a lot of document management. So there's a lot of intake of documents. Great use case for Agentic. AI. So it will identify that where's the spots for you to go do that. It'll identify doc AI which is our technology already. Blueprint knows about all that. And then you can, you can, uh, you can get that.

You can run the workflow that way. Import it back and then run the application. So I don't have the ability to forward it. So you're getting to see this another time. I will not touch this now so that it works clearly. Um. One thing you were saying that it's not migrating Constellation getting Constellation effectively for free as part of the reimagination process. I think that's amazing. That's a, that's a big change in direction. Yeah. And for me personally, having done this stuff a lot, I almost wish we don't talk about the technology, but talk about the business outcome. Right. Like what are you going to get? You're going to get straight through processing. You're going to get the ability to do a document management. You're going to get the, the time to process this loan application goes down for, for two days to like ten minutes.

That's, that's, that's the outcome that we want. And then the technology is just a side benefit of you reimagining what you're doing. That's really the approach that we're, we're going for. All right. We're back where we were. We're reimagining it. So it asks you, what do you want to reimagine? You got your reimagined workflow. We're getting into the why AI assistant. There's a prompt already in there, but you can really chat with it. I've done this. It's a really neat experience. If you haven't tried it and it's going to call out those Agentic AI features directly right there within Blueprint. Okay, so these are the four agentic steps that identified we run. This comes back. You download that Blueprint and when you import it back, you make it what's called a built on application. So this is the neat part from a technology perspective. You are reusing everything that you have built today.

So your business rules that may be great. You get to reuse them. You built it on top of your existing. Now you run it. And now the same application. This is in runtime your agent experience for the loan submission agent. Now we're just showing this because we have to demo it. This could be completely automated. There'd be no human intervention if you didn't want it to. So you're uploading the document. It's asking a bunch of questions that will then create the case automatically once it's done. So all the details are read. And if you look at it, it's going to be the exact same case and experience that the client had. So can I just check? You're not telling me that if I built an app in 8.1, I could just do all of this too, could I? Yeah, absolutely. You can absolutely do this.

So the the amazing part is, as I said, the UI there looked like a 23 dot in more newer UI. Some of the clients I've spoken to, in fact, Stu's going to talk about one of our clients who has used this approach is in production right now, and they had built their app about four years ago, but they realized that the app that they built, the way they had built it was probably not optimal, but they had built a lot of integrations. They built a lot of the data model, which was all correct. It was more on the process side. They had to reimagine. They were able to use the same approach, reuse all the integration, use the built on application, and they went to production in a pretty fast manner, which we'll talk about in just a minute. And before I get there. Right.

So the idea is you don't modernize all of this in one big bang. You do it incrementally. So pick the case types that matter, drive the value. Think of what your heritage application becoming another layer in the Layer Cake you have your new layer, and over time you're just getting rid of the stuff that you've now reimagined all the while preserving your previous investment. You're automating all the discovery and you're automating the delivery. So I personally think this is really neat, and we're starting to see some really great story and success in the field as well. Um. Yeah. So again, when we stood on this stage last year, this was still a fairly conceptual, we hadn't actually got this actually live. We hadn't launched it properly. Obviously, this is now absolutely live. And as we're all saying, you know, this is out there, any one of you in the room could be doing this.

So one of the largest companies in the world, a big, fast moving consumer goods organization, I guarantee you've got their products in your bathroom and in your in your kitchen. Today. They had an app that was five years old. It's pretty clunky. It was functional, it did the job, but it certainly wasn't modern in any way, shape or form. And they were able to take this, run this through this process, reimagine that app, and deploy it in as little as 63 days. So five years of technical debt and reimagine that from a workflow in 63 days. But this wasn't a rebuild. They hadn't built everything from scratch. In fact, all of the effectively the rules that were sitting there before, including 40 rules in terms of integrations, security, IDP, etc. all of those were able to be reused. Such an important concept is your apps, as we said, have got so much untapped value in them.

They've also got so much IP in them. So much of your existing business and the insight is sitting there today. That's not just chuck it out with Chuck the baby out with the bathwater, but let's build upon that and build a gigantic into those. And you saw from the from the video, which we went through twice, just so you can see it, how how quickly and easily that can be done. Yeah. Thanks, Stu. And you know, you'll think about Stu and I are here. We showed you all the technology, but we keep talking about the business because we're both really passionate about that. I've done so many applications. In fact, I delivered some applications where at the end of it, we were like, well, the client didn't get much value. And that hurt me as a developer too, right? And I think if we don't do all the business stuff up front and get alignment, these things don't get as much momentum as we think we will.

So that's, that's, that's why we're both very passionate about that. All right. So that was the bulk of the content. I really wanted to open it up for Q&A. Before we do that, a couple of items. So we have we're in the innovation center for two things. One on the on the modernization piece. We're also there for Pega as a service for anyone curious about how that approach works. We have four modernizations partners globally that are following this approach. We're partnering with um, Aaseya AI for process cap and lab. Lab, in fact, has a meetup later this afternoon. Stu and I will be both, both there. So if you guys would like to have further conversations, we'll be we'll be there as well. And then I'll leave the innovation booth set up so you guys can come meet us there. But if there's any questions, please feel free to step up to the to the mic and we'll answer those questions.

Hello Dr. Patel from NJ courts. I, um, I noticed you mentioned, you know, maybe you want to take the approach of doing this in small chunks, like do one case type. But would that affect the testing when there's child cases involved and everything like our offline mobile product involved? So, um, I'm a in 25.1. One of the things we've done is I think Kerim mentioned it briefly, but anything that you build with the latest technology, we are building the test automation scripts by default, and that only comes with Constellation. So the beauty of this approach is, as you do that, all the test automation cases will be provided to you with Pega. I think I don't know if the coverage is not going to be 100%. It never is, but it's way better than what it is today. So for those case types that will get impacted, my hope is that the experience will be actually much better than it was.

Um, my ask and I know it's a public recorded session. Our hope is that upgrades on Pega Pega as a service will be much more seamless going forward. And in order to do that, you've got to be in the best. You know, our best practice methodology. And by doing this and by having Blueprint doing the import, you're automatically following best practices. That used to be a big debate. Are you doing things the right way or the wrong way? Well, there's only one way now, right? If you do it, you're using App Studio or Infinity studio. You're automatically compatible to all our best practices. Thank you so much. You're welcome. Any more questions? Hi, this is Kumar. I am from connections reimagining a legacy application using this signature tool. Um, how much? Like if you're moving on Constellation, how much of work will be still manual that we have to do to upgrade or it will be like 100%.

Moving on to the Constellation. So I think there will. So during the modernization itself, there's definitely going to be work, right? But the if you think about any kind of modernization like this, there are three main steps to any modernization. Number one, you got to figure out what does your current state look like? Two, you got to figure out what is the reimagined new state look like. And three, you got to actually go build it from a discovery perspective, we expect about 80% reduction in discovery time using the app signature approach. That's that's what we're seeing. We say conservatively 50, but we've seen up to 80% on the on the delivery side, we're using the Blueprint delivered methodology, which is leverage Blueprint as a way to deliver that. Our expectation is 50 to 60% reduction in development effort around using Blueprint for that upgrades. Right now, I don't know about 26 yet because it isn't out, so I can't tell you what that would be.

But currently, for our clients that are on Pega 2425, we have seen over 50 to 60% reduction in upgrade times for clients that moved from on prem to cloud. That's just the first time around. And then as they start building things like test automation, that goes down even further. My goal, what I would love to see is I'd like upgrades to be less than a week, right? Going forward, is that going to happen tomorrow? I don't know, but that's what I would like to see in the future. And I'll just point out one question you're saying because there's customizations, we know there's customizations everywhere because we're rebuilding that imagination layer on top of the existing. We're not chucking any of that away. So we don't have to clean up everything and get all of that dealt with in day one. We can still use those rules that are sitting in the below layer and over time, remediate and over time, obviously tidy up and move those rules into the modern layer.

But it's not something that has to happen day one. And that way we can get quick business advantages, but we haven't chucked away any of that. We know customization is there for a reason, and that's something that can be dealt with over time. So you're saying the preferred approach is to upgrade in chunks. Not all the case we imagine. Obviously the upgrade happens at a platform level, but the. Absolutely. To reimagine case by case flow moving forward iteratively, it's absolutely the right way. So you don't end up with a two year project, but you get value much, much quicker moving forward. Okay. Gotcha. Thank you, thank you. Thank you. Hello. Good afternoon. Thank you for the presentation so far. I took a video of, I think both times that I ran. A second. Time. And yeah, zoom in and look at that later. Um, you were mentioning reducing the discovery time when you are.

This was literally a topic with my director earlier today was how do we add features into a new app into an existing application? Take something that is already live. Keep it smooth without incidents, and also continue to build on to it better. And you touched on a point which I really want to learn more about, which is, um, using app signature, reimagining it, using with using Constellation for apps that are not using Constellation yet, or are not using the more newer case management approach. So where in this process is it like, is there a natural place in this process to surface some of the insights on what are the areas that are going to require building and modernizing moving forward? Right. I know, I understand it's still there in the application stack. It's still available for use, but it may not be compatible with the reimagined version.

There are process flows that are more complicated. There could be data views that are not usable or compliant. Constellation is does this provide any improvements on finding those places so that we can begin reimagining the right way to do them? That's a that's a great question. So, um, the tool itself is getting is iterating quite a lot. So the first iteration of the tool we released in January was fairly basic, like it identified the flow rules. It identified the, the personas, the case, the data. In May, we had another release and that started getting into. We realized a lot of our customers had built rules in the UI rules, which is not best practice, but they had built business rules in the UI layer. So we added the ability for the tool to go in and extract even the rules in the UI layer. I was talking to somebody earlier today and they were like, well, we have unfortunately built stuff in utility and activities and like rule forms that.

And we have a table determining. So we probably, there's so many combinations that I don't think everything is going to be covered. But two things. One, if there are common use cases, we will. We are working very actively with our product team that's building this this feature. So come talk to us. We'll we'll figure out where that is in the roadmap. If not, we can get it on the roadmap. But two, when you import the Blueprint back in, We went over that very quickly, but when you import it back in, it will show you which rules that rules that you can start, like overriding or which layer. What is it going to impact? That's something I want to see. So that's override layers. Yeah. That gets into those level of details. It will still require somebody saying, okay, where in my layer cake should this list?

Is this the right reuse layer? So that's still there. Um, I personally haven't seen 26.1. I haven't gotten my hands on it yet, but I'm expecting that the YB AI capability that's coming on the developer side, that's going to supercharge that even more, because now you can start talking to it and saying, hey, here's what I've done, here's what I want to do. So I don't. So it's not a non-answer, but I think there's some exciting things coming in that space. Directional answer no, directionally. Directionally, I think this is the right way to approach it. Okay. All right. Thank you. You're welcome. Hello. Hi. Patrick Capron from TD Bank. Um, I've been told that the app signature tool doesn't support Frameworks like Customer Service and others. Is that true? It does not support some of our older. Like Pega warranty. Some of the. So right now the two things.

So Platform. It supports completely. It supports customer service for discovery as well as Re-imagination. It does not support smart investigate smart dispute. So the smart apps. It doesn't support in the sense that you can use it to understand your current state because everything's Platform everything Pega built is Platform, but smart apps are industry specific accelerators, if you will. There's a new way of building. If you're using Smart Dispute Agentic Edition or Smart Investigative Genetic Edition for those. We have a slightly different approach. And candidly, we're building that approach like we're taking it. Where's the biggest problem? Platform CS next, we'll hit some of the smart apps. So with smart apps, our recommendation is go with out of the box because smart just smart claims the product team has already built a more prescriptive approach of almost like a standalone. That's the new app that you want to build, and customer service app signature does work, so you can run it on your customer service instance.

You can determine which cases you want to do the the way to do the, you know, there's two things. There's coexistence, we call it in terms of having the old and the new work. And for customer service, our approach is to use. Process Fabric. So the Process Fabric that Kerim spoke about earlier this morning, the idea is going to be, how do you use your new and the old and the things that you're going to run into, and we can get into the nuances of it is, what is the CSR experience in CS? Because you, if you have certain case types looking like constellations and others not, what does that mean from a training perspective, from a call handle perspective? So our recommendation again on CS specifically has been, why don't you look at where the value is going to come from, goes back to the business value.

Often we find some of the CS applications are deployed in the customer in the CSR channel, but not in a digital channel. So can we start picking certain use cases and using this approach to build a digital front end for certain customer journeys, and that could accelerate it. But I'd love to learn more about your particular use case and see how we can help you. Yeah, I was going to say on the specific question about frameworks, it's completely nuanced. So it's not a black and white. It doesn't work for frameworks. That's not the case. It's the case that there may be things it just doesn't pick up on. We just recommend, you know, paired with the roadmap in terms of the outcomes of what you're looking for. Give it a go. Absolutely. Run it again. Run it in production if possible, in staging as near to production as we possibly can and see what it comes up with.

And if it's missing anything, again, it's not lost when you re-import it. But yeah, we'd love to have that conversation and obviously work with you guys on that. Sounds good. Thank you. Okay. Hey. Good afternoon. I'm Payton Cochran, I work with Aflac. And I had a question about, um, With using app signature to be able to document or basically be able to create that app signature file, put it in a Blueprint, and kind of be able to see how a modernized version of a case types would look. Um, is there I guess enough power under the hood with the reimagining for, let's say, for business purposes, we're not only wanting to modernize our application and update our case types, but also potentially for business reasons, revamp our case types a little bit. Could we say take our existing case type A and be able to say, I've got this similar one that I'm wanting to build called case type B, and here's what would carry over.

Is that a realistic scenario we could achieve, or is that something that might rely on a little more nuance or a little more exterior or external work? So realistic scenario. Absolutely. What you don't want to do is take a whole load of files and just put it in, try and put it into one Blueprint because that won't confuse the heck out of it. So, so don't try and do that, but absolutely take it apart as effectively. Individual blueprints, just take them and import them as one. But then obviously work on that and say ultimately, if there's one master blueprint or one master case flow that you want to take forward and actually almost start importing the best of them. Obviously, once it's in blueprint, you've got all of that power available at your fingertips to make it happen. So that's a very common sort of question and use case that's coming up at this moment in time.

Okay, perfect. Thank you. Yeah. I would just add also that we are doing this with you all. So if you want to reach out to your account team and say, hey, you want to experiment with this, our team leans in and helps out. So we'll, we'll work with your solution consultant for your account and really make sure that you get what you need. So that's another offer as well. All right. Thank you. You're welcome. Liz. Hey. Hi. Um great session Liz from lab. Just a quick, uh, change of venue for the modernization drinks. It's at the whiskey down at 530, so please come there and we can continue the conversation. Um, thanks. All right. Whiskey down it is. Thanks, Liz. All right. There's no other questions, I think. Sorry. Hi. Um, is the infinite flow architecture is compatible with cosmos flow or Constellation flow, or need a full migration be required?

I'm sorry, I didn't. I didn't quite catch that. Sorry. Um, if it's compatible with the oldest version, um, cosmos flow. So definitely UI kit or cosmos, any of those. It will find the flows in an existing apps at this moment in time. What your to-be state will always be Constellation. That's the to-be state we want to go. But yes, it is compatible with those older flows. Yes. Are you talking about app signature or the approach like with the import which which. Infinity. Infinity. Virtusa. Infinity version will work with everything. So if you are. If you upgrade to Infinity 26 and you have a cosmos or a traditional UI app, that'll still work. We're not changing any of that. This is more around if you're interested in reimagining. That's where we think the value is going to come from. This is the approach for helping you really transform your Pega app into a more modern Agentic experience.

Thank you. You're welcome. Question from me. This is Anusha from Glidewell Dental. Even I met Smith during one one of our discussion related to Constellation. What we learned from the discussion is we cannot upgrade our Customer Service application to Constellation as easily as like migration looks like, right? So right now we've learned that we can use app signature and Process Fabric as a path forward to Constellation upgrade. Is it matured enough for us to Keep it in a roadmap, or do we have to wait for some more time? So so yes, it is mature. It's different. So we'd say it's a different approach from Platform as it is for customer service. But absolutely it is mature enough. And as you say, you're discovering the apps. But the important thing is you can run your UI flows and your Constellation flows in parallel. You just uses a slightly different method to provide that coexistence to make sure it's not a big, a big bang approach.

But yes, it is mature enough to have those conversations. Absolutely. Okay. Um, one more follow up question is, um, if we resisted the UI kit application and Process Fabric, does the UI look like a constellation UI or does it carry forward the UI kit one? So typically your CSRs will log in to the Constellation sort of front end Constellation framework that will look different, but the actual flows themselves will be the same as they were before. It's the actual UI flows that's being effectively surfaced within the Constellation window. So they look exactly the same. And that's the whole point. There's no massive change as far as your CSR are picking up. Okay. Thank you. Thank you. Thank you. Hi from Jpmc. So ours is a smart investigate app built about 18 years back. Is there a way to extract functional specification of the application during this process or reimagine from Blueprint or signature file?

So Smart Investigator and Smart Dispute are two really interesting use cases. I would say let's have an offline conversation and talk about it. We are actively exploring a few different options on leveraging some additional AI tools in, in, in parallel with app signature. Because what app signature does like behind the scenes? Just so you know, if there are technical folks interested, it will look at the case and the work structure in smart investigate. It's not just that you've got your messaging component, you've got your your rules, you've got the Swift stuff that you have to take care of. So it's slightly different in nuance, in the sense that a lot of customers for smart investigate, they've had that platform, as you said, 18, 20 years. They've done a lot more than just an investigation platform. They've built a lot more other things. So it's not as straightforward.

And that's why I think these are more nuanced conversations when it comes for smart investigate and smart dispute, because they're very purpose built applications for a single business purpose as opposed to a more platform application. So I'd love to discuss that more. If you have some time after the session and we can talk about what approaches we've taken there. Thank you. Sure. So I know we're over time, but just a thank you to everyone for coming and our message that no matter how old your apps are, there is a genetic capability just around the corner for you guys. So yeah, thank you for your time. Thank you. And we're here to help you guys as well. So thank you.