PegaWorld 2025: Constellation Adoption Strategies for Radical Success

PegaWorld 2025: Constellation Adoption Strategies for Radical Success

Good afternoon everybody. My name is Paul Barnes and we are excited to have you join us in our session this afternoon on Constellation Adoption Strategies for Radical Success. I didn't use Iris to help us come up with that name, but I do hope that you get radical value out of the session. Um. My name is Paul Barnes.

I'm a senior director of business excellence and adoption strategy for our new tech at Pega. I've been with Pega for about 14 years, spent the first two thirds of it in consulting, delivering our solutions, and a few years back, I moved from the field into our go to market strategy team, and I now get to lead our lighthouse program, which is all about bringing new technology out to the field and understanding how we deliver it, and making sure that we're bringing delivery lessons and product lessons back into the Life cycle Constellation is one of those.

So this will be my third year presenting on Constellation very excited to be here. And with me. I've got my name is Tim Beachus and I'm a Senior Vice President and a DPA offerings leader in Virtusa. I've been in Virtusa for seven years now. Before that I was at Pegasystems for 21 years and I'm based in Boston, Massachusetts and one.

One personal note when I joined Pega 14 years ago, Verizon who you saw on stage today, they were actually my first account, and we were implementing Customer Decision Hub for the first time with them and Tim Beachus at the time came out to help me deliver that solution for Verizon. So we go way back.

It's good to be on stage with you here. You too. Yeah. Um, so what are we here to talk about? Constellation, right. So before we get into the adoption strategies, I just want to give everybody a quick primer reminder on what exactly we mean when we talk about Constellation. So it is a complete user experience system out of the box.

And there are six things that I want you to think about when you, um, when the word Constellation comes to mind. One is that we've built it so that we, uh, can can drive productivity increase with our end users. Right? So all of our workflow concepts, the experience that Constellation provides, it's intended to improve and accelerate the work that that users are running through the system.

Second, it's all based on Center-out. So when you're going into Blueprint and you're building your stages, your steps, your data, your personas, and you're dropping into App Studio or Dev Studio and you're continuing that build and Constellation Constellation really forces you into that model. If you're a developer that's been with Pega for a long time, you've built a lot of traditional applications.

You had a lot of choices to do, a lot of things that weren't necessarily Center-out. So Constellation helps move you down that path and gets you gets to the outcome that we're looking for. It puts accessibility first. So again, with traditional architecture, traditional UI, if you wanted to have an accessible application, you needed to go in and build those rules yourself.

We've done all of that for you with Constellation, so you can now roll this out and immediately ensure that you're you're hitting all those people that have special needs and interacting with the systems. Uh, if you were in Caroline and Brian Long session just across the hall a moment ago, talking about how I within Pega is driving an eight x acceleration of developer productivity, you would have heard that Constellation is a big part of that eight x acceleration. We've run, um, labs and side by sides, uh, internally and with clients, and we show that it's at least 50% faster to build with Pega out of the box, uh, on Constellation than to build the same solution with traditional UI UIKit. We know, though, that, uh, some, some clients, some requirements navigate us or push us away from leveraging out of the box capabilities.

So in those situations, it's an architecture that allows you to bring your own UI. So it's flexible in that in that nature. And then lastly, we want you to experience faster and easier upgrades. And again I was talking with a banking client from Europe just last week, and he told me how their CEO is actually creating two different paths to live for applications, one for Constellation applications, because they're able to make upgrades on that, on that system so much faster than they can on the UIKit version of applications.

So that is really coming to fruition here, and hopefully you'll be able to start seeing how quickly you can apply product upgrades Infinity 25 when it comes out. Get it on your system and you're off and running. And Constellation is three years old, so we, uh, we believe we know that we have surpassed traditional UI capabilities, and we're really focused on innovation in the product.

And these are six themes that are going to be coming out with Infinity 25 within our core UX. We focused on accessibility and performance state management of the cases with migration capabilities. One click to introduce a blended UI solution into your environment. Modernization tools that allow you to take traditional UI kit or theme cosmos applications and move them over into a Constellation architecture, as well as a GenAI based migration assistant to move you along with theming, we've got some new branding options, new authoring experience in the area of self- service.

You know, we've made a number of advancements with a simplified case view, new mobile SDK capabilities, and new web embed capabilities. One of the big benefits of Constellation is that it is a digital first architecture. So we expect many more clients to be implementing self-service and digital channels, as opposed to just serving as a back office desktop.

Increasing developer productivity again, all sorts of new tooling. Many of them tied to our generative AI capabilities called Autopilot at design time, that really connect in with Constellation and improve that authoring experience for you. And then over the course of the last year, we have leaned in with a lot of clients and heard a lot of feedback around how we can treat our data differently within Constellation.

So we've made a number of updates around our insights, forms, text, and labels. Localization improvements in 25 are a big thing. And then other embedded data capabilities around tables and lists and whatnot. So really excited for you all to see this. Uh, and, uh, you know, definitely want to hear from clients that are first on board, uh, trialing out Infinity 25.

I'm sure a person from my team or the product team will be close by. You looking to hear what you have to say. So if you are adopting Infinity 25 with Constellation when it comes out. Please let your know so that they can let us know so we can find out what your experience is like. So last year at this time we announced a partner contest.

We got a chance to get up in front of the partner summit, and we basically asked all of our partners to lean in and drive the adoption of Constellation, and we asked them to do that in three ways. One of them was we wanted them all to go out and take the Constellation adoption mission that had recently been published and available on Academy. There is a big shift in thinking and approach in moving from traditional builds to Constellation. And while our role based missions provide exercises that are focused on Constellation, this adoption mission was a great grounding to help you wrap your mind around what. What are the key differences between your traditional and your Constellation implementation approach.

The second was we wanted to hear about projects that our partners were driving. So registering them with us, making sure that they're going live to successful production, and then telling us about them so that we can write case studies and talk about the goodness. And then the third was submitting new Rd components.

So Rd components are a core part of Constellation. It is how you can extend the Pega desktop and allow for new controls to be brought in that are still within the guardrails of the Constellation architecture. We have a library of them available. Many of them you can take out of the GitHub library and apply right away.

Some of them are 90% there, and allow you to make some small changes to to suit them for your client's needs. So we asked our partners to help us build out that library by submitting those components that our engineering team could review them together. And we had some pretty fantastic response from our partner ecosystem.

Over the course of six months, we had close to 8000 partners that were badged on the Constellation adoption mission. And I think at this point, we're probably closer to about 11,000 that are out there. So if you're working with a partner and they're saying they don't have the expertise in-house, push them a little bit because they should be able to get resources that have the expertise or take this enablement and make sure that they can show up and give you the skill that you need.

We had 44 projects that were registered as Go lives in 2024, which is fantastic. And we recently ran a survey and found that 40% of Pega's clients globally today have either deployed Constellation application into production or are building in the late stages of building the application for production in the next quarter or so.

That's a huge number. And that tells me that Constellation is really, um, you know, it's it's taking root, right? It has taken root. And who was the winner of this contest? You can probably guess. Um, Mr. Beatrice is here because Virtusa knocked it out of the park, so congratulations. Thank you. Yeah.

Thank you. Paul. It's great to be recognized, especially around this new technology that's happening with the Pega platform. So I'm going to take you through sort of those two tenants, that or actually three of them that were part of the program on how we responded to this initiative, this challenge and won through.

So first off, we had an enablement approach and it had three key tenants. We wanted to align with our learning goals. We wanted to accelerate adoption through engagement, and we wanted to enable the organization wide readiness for this new technology coming along. So those were the three key pillars.

And what did we do in each of these pillars? Well, in the learning goals, the first thing we did was that we mandated that the Constellation adoption and the associated Pega Academy missions will have to be embedded into the performance objectives of the staff. This led to over 630 associates successfully completing both the adoption missions and upgrading to the latest Constellation enabled version of their highest certification.

In terms of engagement, we organize tech talks where an average of over 125 participants explored the Constellation. Sorry Constellation capabilities across three sessions involving demo and case studies. Now, this enhanced their expertise by making sure that they stay ahead of the innovation curve.

And then finally enabling an organization wide readiness. We did that through organized hackathons, where over 50 participants engaged in problem solving and practical implementations of Constellation. We had top two teams with their innovative approach who won out? And additionally, we enabled to your point about the DX components, we enabled the React and Angular development teams on the latest versions of Pega to customize and build those custom components.

So that was really our approach to the enablement. And I just want to give a quick shout out to Abhilash and Arun on our team who put this program together. It was a great job that they did. Now, talking about that engagement element, we organized those hackathons. The last one, as I was preparing this session at that time, the last one we ran was from February 3rd to 10th.

We had 11 teams and 58 technical wizards across Virtusa tackling a hospitality management use case. And we crafted some game changing solutions using Pega Constellation. And after a week of this intense innovation, the winning team of these guys here emerged with a cutting edge solution. So I read through the the sort of news story about this program from our service line.

And I picked out from this some of the quotes that the participants in this innovation challenge made, and I've highlighted some words because I think they're important in terms of what people go through when they do these hackathons and these learning experiences. So the first one you see is the word challenging and being able to enhance his skills.

Now, if you don't have a program that's challenging, then people kind of just forget what they learned. So having that challenge really builds that muscle memory during the learning cycle so that when they're in the field doing an implementation, they remember, oh, I remember how I did that, how I got through that.

So I think it's very important to pick something that is challenging and not just easy to get through because you want to win a competition. Again, sharpening my technical skills. Shivani was saying that, you know, this was a very important element for her. And again, using that word. Challenges. Despite facing challenges, she gained valuable insights and worked individually and as part of a team which is again very important.

A couple of other quotes. You see that word challenge again, right? And the word adaptability. So adaptability I think is a very important element of working with customers, especially around the UX. Right. It's what most customers actually want to change or look and feel and sort of go through that show and tell part.

And you need to be adaptable in being able to respond to that. So from from a delivery point of view, this is a very important element. again innovation, collaboration and ending up with a deeper understanding of the Constellation. These were really great quotes that I picked out from the teams that did this.

Before I go into this next session, I just want to circle back. Challenging doesn't necessarily mean Constellation itself was challenging, it was learning the new skill set, overcoming some of the traditional experiences that they had, I think was part of it. And the fact that you put together a program that challenged them to think differently about it and apply their skills successfully.

Yes, the hospitality use case and what we wanted the hackathon to be was really where the challenges were, rather than people being challenged at using Constellation. Thank you. I just got to get that in. Yeah. No, but that's fantastic. I love the, you know, the very thoughtful approach that you took to it.

Um, as, uh, you know, the Our Lighthouse team, as we work with new clients, new partners that are taking their first steps on Constellation, uh, the very first thing that we run into is, uh, where we have a blocker. It's where a team is coming to the table. They're excited about adopting the new technology, but they haven't been given the time, or they just haven't set aside the time, uh, to go through and complete the enablement.

And they're hoping to learn about Constellation as they go, not realizing that they need to hit the reset button before they start the project. So when you start your first Constellation implementation, uh, please show up with enablement completed, if you're a partner and you have resources going through the Academy missions, please spend time with them thinking through how their approach is going to be different for this new project that they're embarking on, it will be a much smoother onboarding and move into accelerated release cycles.

So we're going to talk about three adoption strategies today. The and we're going to go through each one of them. And then I'm going to hand off to Tim to talk about a couple experiences from projects clients that they've had within the last year. So the first one pretty straightforward new applications.

Our adoption strategy here is so easy. I hope everybody remembers it. Leaving the room. If it's a brand new application, particularly on Infinity 2324 and soon to be 25, there is no reason that you shouldn't be building that new workflow on Constellation. We saw that the capabilities have surpassed the UI kit theme, cosmos capabilities, our Generative AI solutions plugin in much more easily, readily with Constellation.

So you're going to really get, um, you know, an infusion of goodness by, uh, by following that model for all new applications. And I just want to run through some basic guidance that probably seems fairly evident as you think through it. Um, but for new applications. Right. When we say new applications, it's Platform customer service and sales automation and industry applications that are available on 24.2 plus.

So smart dispute smart investigate um, smart claims those are all versions that are now available. Uh, and if you are embarking on an engagement with any of the industry applications, please reach out to your Account Executive. And the account Executive will reach out to my team so that we can help facilitate a lighthouse engagement model to ensure that you're getting the right support as you're taking your first steps with that strategic app.

Um, within your organization, get aligned with your Pega COE. Get your architects to have run through the adoption mission. If you're running a Constellation or a customer service project, uh, the Constellation implementation mission on Infinity 23 or higher is all geared to Constellation. So you should go through that and then all role based training, uh, the BA, SA and LSA is all current on Constellation as of 24. And uh, the SSA course will be uh, up to date on Infinity 25. So every single role will have Constellation based training available. Uh, and there shouldn't be any excuse in getting your hands on what you need. Um, designers and business analysts, we want you to go to a site here. Once you have the deck, you can download it after this design.

Pega.com. To get started, there are some additional things that we want to point you at to get you to understand what the design system is about, how you should think about requirements, user experience approaches. So go there and it'll give you some some good guidance. Of course. Start every Pega project with a blueprint.

What was it? Don't don't Sprint without a print I love that might get it tattooed. And then lastly Rd components. We talked about those, you know, invited our partners to lend some to the library. When you're starting your first Constellation project, don't worry about Rd components. Go out of the box.

You can achieve your business objectives going out of the box. If you are a very rare scenario where you really do have a business requirement that is not Available in our out of the box experience. You can look at at building a DX component. We have tooling around it. It does require some front end development skills.

Doesn't require that person to be on your project the entire time. Pega has a Sprint Constellation springboard offering where you can bring in consulting and help through some of those upfront experience conversations. Many of our partners have successfully built these DX components as well. Just don't don't go overboard on it.

We understand that you may need a DX component, but it's essentially equivalent to creating a custom screen, which over time, if your application is built with a whole bunch of custom functionality, Upgradability might become not as smooth as we would like it to. So out of the box is really where we want to focus.

Um, Tim, do you want to give us a couple, uh, a couple examples of your experiences? Yeah, sure. So, um, what I did is I reached out to all of these implementation teams that I'm going to talk to you about today. Um, and I asked them to sort of give me some insights into what they did in the project.

So I asked them what were the objectives of using Constellation and why did they want to do that? What benefits did they think they would get by going with Constellation? What were the results and what were some of the challenges that they had? So this first example is a new implementation. It's actually an implementation to automate and enhance prior auth at the physician clinical review process.

Their objectives was to modernize the user experience. They wanted to have an enhanced UI performance. They needed better accessibility and mobile responsiveness, and they wanted to future proof the application for better extensibility. Why? Well, that future proofing was very important. They perceived a faster time to market.

They wanted the performance and scale of the UX. And they actually thought that the benefits they would get was a better UX and lower maintenance and cost and a faster time to build. And the actual results they got was a faster build. They loved the drag and drop. They had an elimination of custom sections, UI rules and scripts. You know, the old UI kit stuff, reduction in UX load times. And here are a couple of quotes from the customers team that as they went through this process. So one said I have found the app to be user friendly and streamlines the process. Okay, another person said, this stuff looks really simple and we anticipate no issues with getting people trained.

And that's very important for a new implementation, right? You want to have your user base, your business, adopt the application as quickly as possible. And for anybody who's being onboarded into your company, you want to make sure that they're training on that application is as smooth and as quick as possible.

So these were realizable things that they they responded to. Some of the challenges was the learning curve. Obviously at that time there was some style restrictions, limited CSS and some capabilities were still evolving. So that's what you see. As you know, Blueprint and Constellation, these two very newish capabilities in the platform.

They're constantly The upgrading and updating them. So what were the key learnings here? Faster to build reduced customizations and using out of the box capabilities. There was zero customization in this implementation right. And that's quite significant. So those were the key learnings from that. I'll talk about another example that was an early adopter implementation kind of a new thing.

And it was with a US national insurer. And they wanted to build the next generation long term claims claim system. Their objectives was to streamline the long term claims review process, set up triage and decision. So that's sort of onboarding a claim right. And making sure that that was improved in the overall process.

They wanted to improve that user experience. And they captured structured data and automating the workflow. Why? Well, it was a new implementation and they wanted to use the latest technology and the version available. And they had a perceived ease of implementation by using Constellation rather than having to stitch everything together in the ways that one did with UIKit in the past.

So they had also a faster time to build. They had a richer user experience than previously, and the ease of implementation by leveraging out of the box features with reduced need again for that customization element really helped them. The results they got was an improved user experience. They reduced the manual steps through much better integration of external documents in that onboarding and triage process.

Some of the challenges that they had was, you know, it was early Constellation, so some features were not available that they needed. Some of the attachment, processing and visualization of looking at the attached documents was kind of a little flaky, and the composite view wasn't refreshing on demand.

So a little bit of a bug here and there, but ultimately through these things and implemented a great solution for the customer. So what were the key learnings here? An improved user experience and keeping current. Because, you know, as I said, Constellation is also you saw what Paul was talking about is coming in version 25.

So if you're trying to build user experience or UI on versions before you're missing out on all of that new great stuff that's there. So you need to keep current. I know that's a challenge, but at Virtusa we've also addressed that challenge with a product offering. It's a managed service. We call it Infinity evergreen, and we'll take that problem and that challenge off your hands.

And if you want to know a little bit more about it between now and the end of the day, we're at booth 16. So please come along and find out more. We'll be sure to get you out of here by 4:00 so you can go bombard his booth. All right, so the next adoption strategy is, uh, a lot more nuanced. And this is where I think most of our clients are going to find themselves, at least most of you, in the room here.

So you've got an existing Pega landscape. You've made a lot of investment in your data and your integrations and your business processes and your rules. Um, you want to start getting the benefit of Constellation and all the things that we talked about in the out of the box experience and the benefits that Tim described.

So what are you going to do? Guidance is start building new cases on Constellation and over time, incrementally transition existing functionality that are tied to the new case types over to Constellation so that you can either have that reusable functionality, serve both the Constellation applications and traditional applications, or over time, the traditional case types through, you know, through just aging of the of what they're serving, you can reimagine those as a Constellation case type.

The idea here is not to go in and say, we want to adopt Constellation. We've got to come up with a plan to move all of our existing stuff over into Constellation. We don't want you to do that. You've got fantastic applications that are giving you good business value today. Keep those in place. Do not introduce risk.

Uh, and, uh, and and you'll be smooth sailing. We have dozens of clients that have implemented this particular approach. And I'm going to go through a couple, uh, um, a couple things on the next slide that describe, uh, how that how that blended architecture really works. Uh, the other thing, uh, that we want to focus on here is, as you're building the new case types, focus on also expanding or potentially expanding existing case types into new channels.

Uh, so we'll we'll talk about that. So, um, where does this apply? So it's everything Platform and Customer Service for our industry apps like Smart Dispute, Smart investigate, KYC, CRM. I would not recommend that you try to implement a coexistence or a hybrid architecture with those applications just yet.

Uh, if you have an existing application in one of those buckets and it's on traditional architecture. And you're also looking at the new Agentic smart dispute smart investigate solutions. Let your ACO know so that they can contact us in the product team, and we can have conversations with you about a the right approach to do that and what that roadmap would look like for you.

There's really, um, you know, three things that I want to call out on here. One is that as you're identifying opportunities for new case types, uh, look where you can add value for for those new case types through self-service channels. The reason being Constellation is now a digital first architecture.

It's modern architecture. So being able to take what was typically a back office application and do some type of iframe mashup into a digital estate with traditional is no longer the approach. We know with web embed and other capabilities that we have. It's a much more seamless, modern, secure experience. Also focus on the self-service. The second is bring all of your data goodness with you. True, the data architecture for traditional is different than the data architecture for Constellation. At its core, it's a stateful data model in our traditional land and in Constellation it's stateless. So it's different data types.

You're going to need to have a strategy in place to make the integrations and the data that you've built up available to both applications that serve both architectures. Um, and then third, where you are looking to package up reusable features, we have a recommended approach. It's called modular enterprise reuse.

It's essentially bundling functionality rule sets into built on applications and putting them into your stack where you need to access them. Um, so it's a common pattern. Many of our European clients who are also early adopters in Advertising,Retail,Technology Services,Transportation,Utilities and Constellation drove the thought leadership in this area, and as more North American and rest of world clients are coming on board, they're also leveraging that same pattern to get the reuse between their traditional applications and their Constellation applications.

On the right hand side, you'll see Platform blended UI, CS coexistence, and Pega Process Fabric hub. So one of the things we recognize clients are going to need to do is bring case types from either architecture into common portals. So if you have a traditional portal and you have traditional cases within that portal, and you want to start adding Constellation case types into the mix, you can achieve that in Platform using the blended UI design pattern.

You can also go the other way if you have a new Constellation app, and you're creating Constellation case types within that app, and you have existing UI kit applications in your Platform app, you can bring those over through blended UI and the one click. Uh, I don't have it on here, but the one click, um, migration tool that you can see in our user experience booths over in the hub, uh, they will show you how to do that and set it up quite easily.

Um, with customer service, it's the same concept. It's just a different design pattern. We call it coexistence. That's because there are a number of other out of the box capabilities that you just get snap in when you build a service intent. Uh, and the, um, the I, the I cases, uh, for customer service.

So just slightly implementation pattern but also very well documented, very easy to implement. And then the last one we have here is Pega Process Fabric. So if you have a large number of applications, some of them on uh, customer service, some of them on platform, maybe different versions, and you're wanting to bring them into one unified experience you can leverage Pega Process Fabric hub for that exact reason.

If you're looking to modernize your customer service on traditional application over on the Constellation over a period of a year or two years, the Process Fabric hub product, which is separately licensable, is something that we can provide to you for that bridge, period. Just work with your AE and their business officer, and they can make sure that you have that.

And it's not a blocker for you being able to follow that migration strategy. We also have some other tools here. The modernization assistant I talked about. Again go check that out. It's in its second iteration. And it'll go through and look at your existing applications. In traditional. Identify all the rule sets that transition over easily.

And then those that require some care and feeding in order to get over it will, uh, it will provide a prescriptive plan for addressing those that you can build into a plan and take it. Implement it as over whatever period you need. Um, and then we have a data integration designer, which helps to map data entities into the new common data model for customer service.

Um, there is some new tooling that was just announced yesterday in another session. Rahul Ashok and Stu Smith. I don't know if you went to their sessions. They were running the as a service upgrade and and GenAI, uh, one of the items that Rahul spoke about was a signature tool, which is in alpha mode for us right now.

So it's very, very early stages of um, of looking at this capability, but it would allow you to look at a traditional Pega application and, uh, use some AI tooling to, um, take it out and then reimagine it as a Constellation application for you. So it would cover a lot of the modernization steps for you.

But it is not a magic button. Um, it is meant to drive, uh, you know, collect the the technical information, the requirements around it and drive it through the new standardized Blueprint to live process that we have. Tim. Yeah. So this is the last implementation example I'm going to speak to. Um, this is with a large Australian bank.

It's a hybrid implementation. We've worked with this bank for many, many years. And what they wanted to do was replatform their multiple BPM apps onto a modern platform, 24.1 and above. So historically, the way they approached this was that if their application was strategic, it would sort of have its own home.

But if you wanted to do some processes or, or, you know, a single process, then what they decided to do was have a single instance of a Pega system, and they would build the process. And over time these sort of operational apps just evolved. And then they thought, well, what do we do with these? We need to modernize them, right? So we work with them.

And their objectives was to obviously uplift this Pega digital, as they called it, to leverage Blueprint and Constellation, and also to reuse the modern Pega platform for any new workflow use cases across the enterprise. So they didn't want to go back and create the problem that they did from, you know, several years back.

Why? Well, modernization, embracing new user experience technology to support a modern process and the modern case types. And then they actually went through an assessment with us to look at UIKit, cosmos, and Constellation And and ultimately Constellation came out as the winner as it brings together the UI, the case and the data model.

And again, that's very important in terms of speed to build versus the old way of using UIKit to stitch things together. As I mentioned earlier. The benefits they thought they would get was a much easier implementation be faster and more maintainable. And that's a very important thing for them with all of these apps in this, this digital platform.

The result they got was actually a user experience. Feedback from the very first modernization use case is very good and they love the new look and feel. And I'm talking about something that happened several months back now right. So they're on to the next one. A significant reduction in customizations.

Again that's a very important element to just try to use out of the box where you can. Some of the challenges with, you know, this was a sort of dual partner thing that we did with them, and they needed to get their developers to. So they had some adoption challenges around using this new templated approach to build the UI.

Finally, upskilling to Constellation in a demanding development cycle. So those were some of the challenges that they had. And with us, we we work very hard on getting the first one established and now we have multiple ones to go through. So what were some of the lessons learned? So one I used this term The Bionic Man.

But I realized last night that it sort of aged me because I forgot that The Bionic Man or $6 Million Man, right? That was from the 1970s. And if you're not familiar with it, it's basically this guy that was an agent and, uh, he had a crash and they thought, well, what should we do? And they rebuilt him.

So he was half Bart and half human. And it was the bionic man. So in the same sort of vein, the idea of, well, if you take a business process, right, you can stick it on the table and you can start doing surgery on it. Right. So you can say, well, I've got to convert all of my old objects to case types now and use the case model.

And I've also got a unstitch, all the UI kit stuff that I did and put it into Constellation. But there's a better way of doing it, which is we can rebuild it, right? So we took all of those applications and using both Constellation architecture as well as Blueprint, started that innovation around rebuilding those applications that were very operationally intense.

We used Blueprint, and finally, going with that approach is much faster and more flexible to achieve the end result. Paul. So this last one we'll go through pretty quickly. Um, you're going to apply this strategy when you have no choice but to move to Constellation. So that's going to happen when you have an application that's not accessible at all today.

And you have a regulation, some governing body that's telling you you got to have accessibility, you got to do it fast. Uh, you should not try to make your traditional UIKit application accessible. You're going to spend as much time and energy pouring into that dated solution in architecture than if you were just to pivot and move to Constellation and get the accessibility out of the box.

So that's the first reason. Governing body says you've got to got to start being accessible. The second is around security CSP requirements. We've had clients come to us say, you know it. Traditional UI doesn't meet our security requirements anymore. The answer is move to Constellation. We're not putting new security things into traditional architecture.

Constellation was the answer for that front end performance. We've made some improvements there. Some clients come to us around table loading with traditional UI. So we've we've fixed that with Constellation. Um, and then authentication requirements when you're doing some type of, you know, mashup or web embed scenario.

Again, very specific situations. Um, I'm not going to go into a whole lot of information on this one because frankly, we haven't had many clients who have gone down this route. But the ones that have gone down this route, they did everything we talked about in the prior, um, prior version or the prior guidance.

When you're building new case types, uh, you want to package up as much as you can from your existing estate. Data and integrations are key reusable processes. Business logic package those as reusable modules, just lightweight, built on applications that you can deploy in your stack. Uh, use the tooling that we have available. Check out the innovation hub. There's a booth. Uh, Richard Marceau, I think you can go. He's there. Uh, ask him to to walk you through the version 2.0 of that modernization tool, um, and get going. Uh, so there's going to be more coming out on this, uh, as time rolls on. Uh, and as I said, there's even the modernization Pega modernization, uh, tool that is being worked on in a very select set of client scenarios.

So I expect that that's going to continue to to flourish and hopefully it'll be up on the stage talking about it next year. Um, so stay tuned on that. And then, you know, wrapping up some advice as you move forward on your adoption journey. One get enabled. It's the first thing. It definitely is a shift in thinking it is a new set of skills.

Let your resources get enabled so that they can feel good about the job they're doing, and you can feel good about the quality of the application that they're giving to you. Um, second, get in and understand the Constellation user experience system. We built it for Pega workflow. We built it because we are the leaders in workflow, and we believe that we know how workflows should get done.

So design Pega.com is a great way to go. Learn about it, learn about the patterns. Learn about the thinking behind it. Join the conversation on Pega community. You saw Steph Lewis get up on stage uh, today, uh, yesterday. And talk about expert circles. Join an expert circle. I invite, uh, if partners in the room.

Identify two people from your team that you're going to say. You should be going on expert circles and getting engaged in those conversations on a daily, weekly basis. That is where all of our, uh, internal thought leadership from our product team, from our specialist SDKs and Constellation experts within consulting, are going to be sharing, uh, and and collaborating.

Um, put aside your misconceptions. We put together a little white paper on some common things that people who are used to building in traditional UI. Think about Constellation. It's a quick read. Uh, but go take a look at it and begin to separate the mental barriers that might keep you from driving forward.

And then lastly, pick one of my three fantastic adoption strategies and just go and get it going. And we want to hear about your successes, uh, as you've got projects going, uh, please let your lady know. Um, one of the functions of my team is to monitor adoption, uh, as we're lighting up across the globe.

Uh, so between Constellation and Blueprint and Agentic capabilities, we have our hands full and getting all these signals coming in from clients and partners and teams that are doing work with it. But we want to be inundated with news and updates from you on projects that you're embarking on. So reach out to anyone from your account team, uh, and have them funnel that information, uh, to lighthouse at Pega.com.

And that's it. We didn't really leave a lot of time for Q&A. Uh, but I think this is the last session. No one's really going to be kicking us out, so we will take about five minutes for questions. If if there are any, I just ask that you step up to the mics. I thought he was going to be our first, but no.

Well, we must have covered it in enough detail that. So, so the third approach, which you suggested just now. Right. So we also have a legacy application traditionally EY. Right. So I mean, I was just on a booth with Pega, one of the Pega expert over there. Right. And he suggested that we can use that tool, I think, which you also pointed.

Right. It can do a wrapper like a wrapper. Right. Yeah. Is it not 100%. I mean, is it not going to take care of all the UI for that case type, or is still going to be challenges over there, or can we live with that for the time being? Um, I'm repeat the very last sentence of the question. Can you let's say I'm going to take some time to build up that, uh, completely new case type, which you suggested in the new application or the second one.

Right. But if I want to time being just for certain use case, certain case type, Stipe. I want to keep that mass rapper for my current Stipe. Can I live with that for a short time? Does it need a lot of effort? Actually, no. So if you're for that third scenario, you can absolutely build new case types and have them coexist with your existing case types for whatever period of time you need before you sunset the existing case types.

Does that answer your question? No. I think what you suggested to me that you can take your existing case type in the legacy application, and I think I have to still explore that option in that 23 one. We have that option where you can add that case type over there and it can create a mashup layer wrapper basically for the Constellation.

So behind the scenes, it's use your legacy UI only and create a wrapper out of it. Can that work out for my entire case type on the legacy or. Are it is an option? But it's also So I mean, you're basically like abstracting it so that you can keep the other thing around and you are going to have like there's different maintenance cycles and work that you need to do for the Constellation wrapper versus the traditional case type.

So I would question in that scenario, like when does the cost benefit flip where I don't want to continue doing that? I can certainly see it as a bridge strategy. Yeah. Just just for time being, I mean until we are not ready with that other side, obviously. Yeah. I mean, I've actually seen clients, um, that had a back office case type and they, they shifted to more of a self-service strategy.

They didn't want to eliminate their back office traditional cases, but they also couldn't rewrite them to serve the self-service channel. So in that model they like prepended, uh, the like they kind of wrapped the traditional case type with the right self-service case, um, you know, stages and steps so that it could serve the new channel and plug into the existing traditional case type.

That's a case study we have. Actually, I think it's, uh, publicly available. It's Dxb is the client that we worked with. Um, and they they followed that, that pattern. I have a question. So we have a business case currently we are in this team cosmos, and we wanted to adapt to a Constellation. But the end users are really a high profile users, like the surgeons.

So, uh, we could not put in till now. Almost three years. They were using that team cosmos. Suddenly we could not show the Constellation. The UI will be different. So do you face any challenges similar to this one on the adoption and to the end users from the cosmos to Constellation. So just to reiterate, uh, so the theme cosmos design system and the Constellation design system, uh, If you're moving from one to the other is how different is the experience between the two? No, we know there's a certain experience, but did you face any challenge like, uh, experience, like, uh, how to adapt to this Constellation how we can convince the end users? Yeah.

Um, I don't have a silver bullet answer for you on that. Uh, I would say, uh, I would say let's talk in the hallway, uh, if you don't mind. So, I mean, at a high level, I think what I'm hearing is, uh, one, you see business value in moving to Constellation. So I'd want you to be able to articulate, like, what is that unique business value in moving to Constellation? Uh, because that's the same conversation that I would be having with, you know, the users who are already very happy with their theme, cosmos version.

So what is it that's driving them? Is it a governing body? Um, is there some other need? And then the second would be just incremental approach to moving over. Um, you know, there's, uh. Yeah. I don't know the full answer. I would also want to understand a little bit more about the specific pieces of functionality that you've built with the cosmos, and how that might translate over to, you know, to what it would look like in Constellation going forward.

Um, but yeah, we have not seen a super compelling business case from any client to date. Uh, on, uh, you know, just wholesale moving away from their UI kit or theme cosmos successful implementation. Unless it's for one of those reasons that I stated. Okay. Thank you. Okay. Hello. I'm going to use again another free consultancy moment.

Could you speak a little bit louder? I will use another moment for free consultancy with you guys. Um, our main challenge is similar to the gentleman over there. So we are running on Infinity 23.1 UIKit, and our CSS application is composed by roughly 15 service cases, heavily customized with a lot of rules that are basically implemented, like business rules that normally maybe should be on the backend, put on Pega.

So we are trying to understand how we can easily move into Constellation, but we are trying to understand what are the first steps that will enable us to make that move, despite what is going to be the approach of radical or. Gradual. And my question is what are the indeed these first steps that we need to achieve from a business perspective, so that let's say we can enable the transition, namely should we first optimize what we have there, like simplify, try to migrate more to out of the box, or we should just scrap everything and restart from scratch.

Don't scratch everything for sure. I would say um, so depending on how things were customized, it sounds like it was a lot of like like back end when rule customizations around like process processing of data, I'm assuming behind the scenes. Um, so in that situation, uh, one, you can still bundle that up as reusable modules.

Uh, in the built on modular reuse design pattern that we have. And those same subprocesses can still be leveraged inside new, uh, Constellation service intents. Um, so I would maybe want to take a look at or have the team take a look at what is the new experience that will be achieved with the new Constellation case type, and how do the existing back office or not back office, but underlying processes that you've built up? How do those plug in? Because some of them, you're probably going to be able to plug in easily, and some of them might need to be re-architected, it sounds like, but it should be an incremental approach to it, for sure.

It sounds like the sort of mash up approach that you can take there, which is supported. The mash up. By you mean like the coexist. The old and the bit of the new. Yeah, yeah, yeah. Coexistence works very well on that scenario. Um, we ran a lab with, uh, a healthcare provider in the US. Who was. They were on a very old version of customer service.

Uh, and they were also wanting to migrate to Pega Cloud. And so we looked at their, you know, we looked at 4 or 5 different service intents in a number of integrations that they had on their highly customized Pega Customer Service app, and showed them how they could create a coexistence architecture, with part of it still living on prem and part of it in the cloud. Um, bringing that Constellation case types down to on prem and the traditional case types up to the Constellation on cloud implementation and having it be a seamless experience. But I would also say that you should scrap the high maintenance stuff. Yeah. Thank you. Um, I think I'm probably getting nasty looks from the back of the room to wrap things up.

So if you have any further questions, we'll be up here. Uh, feel free to come up and say hi. Um, and ask them. So. But thank you, everybody, for staying a little bit longer. Thank you. Get to the Innovation Hub and finish things up. Thanks..