PegaWorld iNspire 2024: Charting the Constellation: Insights from The First Deployment of Pega’s New UI Architecture

Welcome to the session today on Charting the Constellation insights from the first deployment of Pega's new UI architecture. I'm Suzanne Clayton, the Senior Global EY Partner Director at Pega, and I'm thrilled to introduce our esteemed speakers today. Firstly, we have Sowmya Chowdhury, EY manager and Technology consulting and Pega lead system architect. Sowmya brings nearly a decade of experience at EY, preceded by a tenure at Accenture. Next we have Philipp Isbouts, also an EY manager in technology consulting who leads UI, UX design and implementation in the Pega practice. Phillips 12 plus years of expertise extends beyond EY, where he led transformative engagements for major healthcare, pharmaceutical and financial institutions. In December of last year, our talented EY team achieved a significant milestone with the first delivery of Pega Customer Service on Constellation. Today, our presenters will delve into valuable insights and lessons gleaned from utilizing the Constellation design system. And at the end of their presentation, we are going to have Q&A.

So please use the microphones for the question askers. And if anybody is going to be assisting helping them, please use the microphone so everybody can hear you. Thank you. Hi everyone. Welcome to our session on Constellation. I will start with the case study that we did for our client last year. Um, our client that was Insurance client was in a journey of transformation to a future proof enterprise. Pega solution to scale across multiple line of business to maximize the outcome via responsiveness, dynamic and adaptive design. Uh, the key challenges they faced, mainly because they were working with so many legacy systems and they have like 500 plus different workflows that they are trying to modernize, right.

So main thing that they struggle with was the operational bottlenecks. Then the customer service was lengthy because they have to work with 5 to 7 different applications to gather the data and solve the customer inability to scale up to the market demands. Lack of automation, the manual labor, low adoption, adoption and ease of use, and no brand identity. So EY as a team came with Pega Constellation that helped the client address these challenges with a sustainable, customer centric solution that will be up to the market standards. So the main thing that we did was orchestrating the existing workflows that is already there in different applications. We come up with extensive 360 view for the customer, so that CSR can get all their different information on the client on the same screen, rather than switching between five different applications when we are talking to the customer. Scalable enterprise foundation layer. That was the key challenge that they were struggling with. As I said, 500 different workflows that they wanted to modernize and then enhancing the automation across the workflow.

That was one of the most important thing that we have realized. Secondly, a guided experience. Guided experience was key to the CSR success. Successful interaction with their customer then re-use of client UX assets. So they had already been huge on modernization journey. So they had some UX assets that was built. So we came up with a approach to integrate that with Pega. The solution that we come up with guided our client through client Constellation advanced system, which configure to rectify their inefficiency within their operational framework. We streamlined the complex process and workflows that is there in their existing application.

More effective process automation. So we take out all the manual labor that people has to do. Robust data insight so that you don't have to go to different system. Everything is in one place for you with 360 view of the client. Operational efficiency and adaptability to market because Constellation being the latest and greatest in the market. I will just walk you through a very simple scenario that we started with with our MVP. So we and if you can see this is one integrated process into out to serve a client. When you receive a call to getting them updated in the whole system in the back end. So there and the customer say calls the client to change the owner of a policy.

And the call landed on the CSR portal interaction portal and they will initiate a interaction case. So as the client requested, CSR will initiate a owner change case to change the owner for the particular policy and they will capture all the information using the Guided Experience and Reflexive questionnaire. So they will capture everything and they will send out a confirmation notification to the client based on their communication preference. Like if I have chose email versus mail. So once they complete the call, the email will be sent out to them or the mail will be sent out to them via the fulfillment team. So once the customer signs in and sends the documents back to them, it will go through. If it is a physical mail, it will go through the OCR process and that will trigger the Pega workflow. If it is an email, it will go through the email bot and that will trigger the Pega workflow. So it will go back to the back office user with the same information that the CSR has provided.

They can review everything in the same case. And based on uh, if say it is an email, right. They just signed in and everything looks good, there's no restriction. It will do some validation on the case and everything looks good. It will just go and close the case and updating all these five different systems that needs to be updated. No human required. So everything is automatic in this. That's that's what SDP stands for. Straight through processing.

Say if they signed in something and send it out and there is some the signature is not proper. The OCR didn't capture the information correct at that time. It will go for a manual process and only in exceptional scenario it will go to a manual process so it decreases the workload to 50% if you think about it. So then the the back office user will review the information came through and they will either reject the case or accept the case. So that information gets updated to all the different systems rather than the user manually going entering all the information in. So we are eliminating that human error. So using different CSI functionality that is already existing out of the box, we didn't customize most of the things as is because it has been so advanced. Right. Like the omnichannel Channel experience like be it an email bot or be it a listener.

The user experience was same. Customer 360. As I talked about, we had a very good customer 360 that is not only available to the CSR but to the back office user too. So when they receive the form back, they can take the action appropriately. Then the knowledge management. So whenever the CSR talking to the customer, uh, it is very key for them to answer them effectively rather than putting them on hold. We already heard it in the keynotes, right? So whenever you're calling someone, if they can just the customer is asking you a question and you have that knowledge management on your right hand side, you just type it in and it will give you all the article or any information you are looking for right on your screen, so you can have an effective communication with your customer to resolve that issue or answer any questions. Similarly, for back office user, we use Case Management, routing SLA and for email, we use the email bot and the listener for any kind of processing.

Okay, so we've talked a little bit about the client. Let's dive in a little bit on what Constellation is and how we used it for this client. So Constellation is Pega's next gen UI, as we've all heard, and it's focused on delivering efficiency for end users and developers alike. Compatibility with various UI technologies, consistency across solution applications, and maintainability for future upgrades and enhancements. So how does it do this? First and foremost is the design environment found within App Studio, which presents a prescribed pre-built front end that can be used right out of the box. Built using React.js components, react is a UI technology open source JavaScript library maintained, built by meta, that's used by a large number of organizations because it's faster, more efficient, and more flexible than traditional HTML. So the way that Pega uses this to their advantage, it's somewhat of a paradigm shift from what we're used to in traditional UI with traditional UI. We're used to developers going to a section rule, which is just essentially a blank canvas, and drag and dropping various layouts, embedded sections, different fields, and referencing properties manually to connect the front end experience to the back end design.

So it's high manual effort on the developer's part. But with the Constellation design, the data model is more in the driver's seat here because based on the data model, the App Studio then considers the attributes of the data of fields and field groups. What is the correct component that should be used and places it on the UI. So it's more of a modification of the front end as opposed to building from scratch. So we end up with is of course easier builds, easier maintenance, easier revisions, as opposed to customization where you need to break apart and reformat everything. In terms of theming been modified a bit as well. We're used to, of course, those monolithic skin rules with the inheritance and attached style sheets and mixins and components that have to be managed and targeted across various aspects of the application. For any sort of branding or revision that's been simplified to these targeted theme elements that you toggle, and various swatches that then cascade across the application in line with accessibility standards. So in terms of branding, again, greater consistency and easier maintenance.

So that's the design environment. And then what's powering all of this on the front end are these APIs. So you may have heard of the APIs in the past. Version one, version two, and now the Constellation APIs, which are far more robust. And what they are, they are targeted APIs for just specific aspects of the front end that are called on demand for creating, modifying or viewing data. And they decouple the front end experience from the back end so that as opposed to traditional UI, where those are closely coupled and you get large pushes to the server and large pushes back, they're focused on just what needs to be updated and when, so that the chattiness between the two is greatly reduced. So you get what you see here faster interactions, smaller payloads, faster server response, etc.. So these APIs power the out of the box experience that I talked about, but also can be used for any non native UI. So again since we've decoupled it with these APIs, if there's any custom front end that needs to be used if the client has a like our client had a their own react component library.

If you wanted to build anything wholly custom, that could be done just as well. We're still building an App Studio. And then that can just point to any other front end, uh, using these APIs and can be accelerated with these software development kits or SDKs. We'll talk a little bit about that, uh, that help accelerate that process by providing kind of like a dummy application and front end that then can point to your application and your front end, but the translation engine is right there, ready to go in leverage. So how does this relate to our client? Like I said, they had their own react component library. So they were very curious to see okay, how can we leverage this. So there's a myriad of ways to implement, you know, the user experience and Constellation. And we'll talk about a few of those other ones.

But these are the three that we honed in on for this client because of their own library. They wanted to know how can we possibly leverage this? So we'll go left to right from least effort to most using App Studio right out of the box. Just like that prescribed environment that I was talking about. That, of course, was the fastest time to market. Everything is already available and you can just manipulate it in any way you need. Um, it's right in App Studio, which provides that live accessibility auditing that I was mentioning. If you, you know, try to change a color somewhere that doesn't quite meet accessibility standards, you get an error. So that happens live.

If you're building an App Studio, you can get that it supports a blended approach. We'll talk about that a little bit later. Um, and it's a familiar development experience. We've all had some exposure to App Studio developers are familiar with it. So it's overall it's just, you know, easier and faster to build compared to these other options. But again, this was a year ago. Constellation was very new. There were still some feature gaps. So the client was a little nervous, especially because they're familiar with their components.

They say, okay, what if we run into some issue and there's just a feature that isn't supported? Well, there comes option two, which is to extend this, uh, extend the component library with these custom components. The way that this essentially works is if we don't see a component available, which is basically a feature that is available right out of the box with App Studio. There's a lot of literature on this that you can look up on Pega website as well, but essentially using just some command line interface and npm from GitHub, you can download kind of like a framework of a Constellation component that has all the requisite information that Pega is expecting for the components, and then within it, just manipulate it to meet the needs of whatever the client is looking for. So that was something that we had talked to them about. And then when you upload it back in, the thing about it is it goes right into that same component library. So it's available for reuse in the application and for any future application that our client may want. And it's available just like any other component. So it's right there.

The system readily recognizes it because we followed all those procedures that are listed all online. And then the final option that we had was the most customized. Use your entire react library. Build something completely separate from us. We'll build a process and all the application logic, and you build out the front end. And this since they have react library, they could use the SDK that's available. So that of course doesn't have a lot of the same benefits in terms of time because you're building here and here, right. You're building the front end and the back end separately. But benefit of course, is that you can customize it however you want using your component library.

And as you see here, we recommended this really only for self-service because building out the entirety of a customer service back end with a entirely from scratch is just not really feasible. So where did we land on this? So the client really settled on option one. They were comfortable with going with this approach. The of course time to market was very appealing. But also the fact that if we did identify any gap we could use option two as a backstop was definitely something that helped sell it for them. But now that we've actually gone live with this, the client is actually currently building out a custom front end experience using that SDK. So really, all these options that we had presented as part of our proposal were really selling points for them. Okay, so I've talked a little bit about this already.

So now we have a visual that we can really put it all together. So we have the single application that we built in App Studio. This is just one process that we built out. And then we have the APIs that are feeding the Constellation orchestration engine that goes to the work portals. These are the out of the box prescribed experiences that I was talking about. This is what we initially built out for our client. So as you can see here, there's this what I mentioned, this decoupling here because we have this orchestration engine in the middle. So what the client is doing now is they're just pointing this instead of from the work portal over to that Constellation SDK at the bottom for their custom experience. The important thing to note here, right, is that we have.

Since these are decoupled, the Pega application doesn't really care about front end anymore. It's not focused on that. It's just focused on the process, the business rules, the logic, and it's really the orchestration engine that's making these decisions. So for an example, if I have like a customer address, Pega is just pushing, you know, street address one, two three city state zip. And then it's really the orchestration engine that's saying, okay, I need to send this to a front office work portal or back office work portal. Sorry. And it's going to be styled this way. While if I'm pointing to the SDK, I'm going to style it completely differently. Pega doesn't care.

It's all part of what we had defined right here, which is what the SDKs help us do. So at the end of the day, what that also means is maintenance becomes easier because we just have to modify one time and then it just points to the right direction. So if I want to add another field to the address I just add it here as to how that is displayed is already defined right here. And there's no additional work that has to be done on the front end. Contrast that with traditional UI, where we would have two separate portals, that we built out two different experiences and have to modify it manually. So that's a benefit there. So what we got here of course, is by following this path, we got that expedited go to market with customer service. And then now going forward they're able to drive these same workflows with their custom UI using the SDKs. So as you can see by doing this using Constellation to our in the implementation Mentation client actually see the difference in operational efficiency and reduction in the manual error, because we have eliminated those processes from their manual updating system, and they have seen the enhanced automation capability afforded client to be more agile in response to the current market demands and customer needs.

So you can be as agile as possible and reiterate your process to get to market faster using all this process. So they have realized that because we have developed this whole thing, say in six months, the Constellation was very new. We had collaborated with Pega very closely and with our customer as well, like client as well to deliver this product. Right. The cost, cost savings were also realized. All this existing application are very costly to maintain in the mainframe application and all this old application. so getting it to the Constellation helped them realize that cost and customer satisfaction is the key aspect that they realized, because the CSR will have more effective conversations using guided experience, knowledge management, all the tools that is on their fingertips, rather than chatting with their colleague or finding it in different websites. Everything is one place that was streamlined. That whole process was streamlined using the application altogether, and the result of all this is reflected on the customer service, the customer satisfaction survey that they got right, and the client realized the impact of Constellation, uh, how they integrated that into their own technological ecosystem.

They realize it through all these different areas. So when When we develop all these things, right? Constellation being new client, working in Pega being new, we went through a lot of challenges. It was not easy for sure. So the key challenges I'll just like to highlight in three different sections, right. The first one is overall for the project. So the first one is because they are starting new. Every customer is very excited to do a lot of things right. When you go approach them.

So the key challenges was to limiting the scope. You have to come up with simplified MVP scope so that you can have, uh, deliver, go to market faster, and you realize the, uh, realize the value that you're going to get in by implementing that in Pega Constellation. Right. So limiting the scope was one of the thing, educating the users and all the client, uh, members to what comes out of the box with Pega and how to utilize all those capabilities in their own workflows just to educating them, right? To come out of their own comfort zone and see what Pega will bring the value to their ecosystem, and how we can not update it way too much. Rather, use as is what comes out of the box like the user portal as Philip has described, right? What the end user will, what the in-house user will use. All those were not changed at all. We use it as is and just modified the relevant field that they would like to see.

And lastly, this is being a service customer service application. As we realize there are so many data that we load on the case, it gets integrated with so many different applications. So when we were going through the process, we realized that some of the services were not ready or it's not up to the point that we can use it. And some of them were totally not existing, so they have to build it from scratch. So those were eliminated by collaborating with different teams and identifying the services quickly, and developing and integrating with that to some Constellation lessons learned only for our team. Because being the first in the market, there was no documentation at that time. But we had a very good collaboration with the Pegasystems team, having calls with them every weekly. The whole product team will show up and we discuss about all these challenges we are having, and they have eliminated that in the process very quickly and faster. Right.

And um, the learning curve to use from the normal section rule and how we are used to use Pega and going to the App Studio and as a developer, being a sort of a LSA, even I struggled. Right. I'm very comfortable using the dev studio or go and do everything there, but it's a challenge to switch gears and go to App Studio instead of using even to create a property or configuring anything to adapt the App Studio perspective of it. That was little bit of lesson learned for us, like, uh. And the third one is the upgrade challenges. So when our client started the implementation, right, the CS in Constellation was not ready. The Infinity was not there at that time. So we started with our limited edition of Constellation at that time last year, and we went through upgrade process around September October time frame. So when we developed so many things and tried to upgrade to that major version, as you all know, we come up with a lot of problems, but Pega really, really helped us out.

So we with that collaboration and all the calls we identified, all those all those problems very early in the stage and resolved them quickly. And we get that upgrade done. I don't think that is going to be something anyone will face, because now they have done a lot of improvement and there is a lot of patch releases that come through to resolve all those initial issue that was there in the application. And the last one is Constellation UI. So Constellation is all about UI and data model now. So just to think differently how you implement when you are engaging with your client, you need to educate them how the UI will look in the new version of Constellation versus the old. Right. You cannot do like a onchange event, or you cannot put a custom button somewhere. Oh, I can do it before.

You want a button? Yeah. I will put ten buttons on the screen. No, you cannot put any button on screen. It has to be intuitive a workflow for them to work on. Pega now. And last thing is the custom layout and the skin changes we used to do to make it super fancy for the customer that they have limited so that it is more simplified. But if you really want that pretty screens and everything, you can use your own component to to build that out, but that has something they have removed. Okay, so what does this mean for all of you?

So when it comes to Constellation adoption going forward, some of the lessons we learned, uh, we've put up here. So it's really depends on what project we're talking about and what the history of that project is. So we put together this very rudimentary diagram here, and we'll start at the top. If we're talking about a new application, chances are Constellation is a great fit because we're dealing completely greenfield here. There's no dependencies we need to worry about. And like I said, Constellation uses react. This is a modern UI technology. More and more companies are moving away from the traditional HTML CSS approach to this more component based design. So this is an inevitable change that will come, not no Constellation.

I mean, sorry, Pega is not getting rid of traditional UI anytime soon, but this is something that everyone's going to get exposed to eventually, so we would recommend starting on it now. The only thing that would maybe give us pause would be if you're building on a Pega application that uses UIKit. So you can see some examples here at the bottom. Then because of that, if we're dealing with a case type that's directly related to that, then no, of course we really can't decouple that right now. But if there's any sort of extension, maybe there's a case that extends beyond that or you have some self-service element of it. We can still consider using Constellation via a blended model. And we'll talk about that on the next slide. Likewise, if we're not dealing with a new application, same kind of thing applies if this is a new case type or if you are extending it in some way to a new experience. We could look at using Constellation there.

There is some migration guidance, but it's not so simple as, say, going from UIKit to theme cosmos. The the shift from traditional UI to Constellation. It has quite some uplift and there's not direct, you know, hey, change this to this. There is manual effort to modify some of your rules. So there is some literature on there, but it's not something that we would push you to right now like, hey, you've got to migrate to Constellation. Um, in terms of feature support, you know, like we mentioned, um, you know, a year ago there were a few more gaps, but Pega has continuously been rolling out more and more components as they adopt them to these react components. Uh, so there is, you know, basically, you know, pretty much equal with traditional UI in terms of feature support, but in terms of specialized features, if anything exists that's found that isn't available right out of the box, you know, when you work with a skilled implementer like EY, of course, we have a myriad of ways of meeting that need either with what is available out of the box and some creative, you know, thinking or using those components that I talked about earlier. And like Sonia said, Pega has been very focused on the adoption of Constellation. So they have been really great partners.

They've been very engaged, and they have told us directly that if you need any help, if there's any gap you have, you know they are ready and willing to help us out with it. Okay. So I talked about this blended model a bit, so I'll talk about it in more detail here. The blended model is basically a way to have what you have built already, and any new Constellation case types in sort of a coexisting portal. So here in this example, we have a single user portal, and from the user's experience, they're not aware of any sort of difference in technology under the covers here. All they see is what they're used to seeing, which is their work list or their work queue right here. But depending on what they may open up, that may load a traditional case type, or it may load a Constellation case type. And the way that the reason that this has been brought to the fore is because this allows you to get some incremental exposure to Constellation on somewhat of a sliding scale, so that the end users can start to realize some of the benefits in the, you know, in the reaction time of the user interface and some of the, you know, the standard formatting, very clean lines of Constellation, but not have to retrofit anything that you've already built. The means of doing this is actually really simple.

If you look at some of the we have some links here at the bottom, we'll share this deck so that you can actually click on them. But it's actually just a number of toggles that need to be selected on the dev studio to support this. So it's fairly easy to do. And again, why we recommend this is just not only for the end users perspective, but also for your, you know, your internal development teams or citizen developers to get them familiar with this new approach to design so that they're more familiar with it as you keep rolling and get more and more exposure to Constellation. All right. I think we're just pretty much just about out of time. I'll just. I'll close out with this slide real quick. This is a slide that I share with our internal team when I'm trying to push the importance of design thinking on all of our projects.

And so these are like the key stakeholders that I lay out. There's Pega and its partners like EY. There's the client and then there's the user. And for the user, of course, what's most important is ease of adoption and usability so that they can continue to stay efficient. There's not any abrasion in terms of adopting to some new experience. Clients also want that usability. They want to see ROI as quickly as possible, but they also want a seamless delivery. They want delivery on time and on budget, and for Pega and for EY, of course, and for all other partners. It's important that again, we have an on time delivery and we have high user adoption that makes our clients happy and that helps us with our relationships.

So I won't go through all of these lines here on the slide, but you can read it yourself and hopefully see, based on what we've talked about, how Constellation helps meet that. I don't usually have this in the center, but I added it here in terms of this slide to just show how Constellation helps deliver all of these. And you can see here at the top this little factoid about the importance of user adoption. User experience is such a key decision maker in our projects. It often is an afterthought. But in terms of the decision making, in terms of technology to use who to partner with, what the design approach should be, that should always be at the forefront, because if we don't get high adoption and high user success, then what's it all for? All right. So I think we're running low on time. So I will stop here and we'll open up the floor for any questions.

But if you do have a question, please come up to the microphone so that we can get it on the recording. Oh yeah. So. You talked about are you initially started up with a version that was just getting built on Constellation? Uh, which version were you using when you started the initial build? So it was not Infinity 23. It was a limited version. It was only rolled out for the client to use for customer service. Uh, was it eight or 6 or 7?

Uh, no, it's not rolled out version. So it's kind of a beta version that we started. Yeah. Okay. And, uh, you said you had to do an upgrade, uh, in the middle of your development. Uh, how, uh, how long did you had to develop and then go for the upgrade? So we started around April. Four months, five months, four and a half, five months. We were into the process, and then we did the upgrade.

Once it is, it was available. April OK. And did you face any issues in the product when you did an upgrade? And the reason I'm asking is we are on age seven, and if we go to Constellation for, say, 24.1 just want to know what all issues you had. Anything specific that you would like to highlight? Yeah. So when we went on the upgrade, we uh, so ours was a little different because we were already in Constellation. It's not like we were on 8.7 or any of the prior version. Our built on architecture was already on Constellation side.

So main thing we we faced was on the UI side, right? Like when the interaction was loading, it was not proper and we had to go back and change some of the back end, uh, rule to just update that. And some of the data pages were not loading properly, so we had to just flush it out and just like save it in the latest version and some of those key things that was related to data pages and UI, mainly OK. And whether, like Hotfixes that you had to install new or was it just some manual changes in the code. Only manual changes were enough. We didn't had to go through any patch or hotfixes along with the new release. No. Okay. And, uh, do you happen to know if there is any kind of a tool Pega provides to convert a code which is built in UI toolkit to Constellation, or is it all has to be manual?

So there is something in process, but I'm not sure it's there yet. So they're working on something for the ease of customer to get there faster, rather than changing everything from one way to different. Right. That's why we are, uh, that's why it's very important. Whenever you're starting fresh. Starting new, they are asking you to go on Constellation so that we don't have to go for pain, but for existing, Sting. You have to. They are working on some upgrade or some kind of tool, but I don't think it's available yet. There's some instructions online that you could find, um, where you can create like basically a copy of the application and do some what of a comparison and it'll call out some of those differences.

I think if you look online, there should be something, um, that can help with that. Uh, in terms of migration. But again, it's all very case by case basis. It's not it's not going to call out everything very specific for you. Um, there is, like I said, some manual effort that will have to be employed to identify some of the gaps. But if it is able to transform at least, say, 50% of the code base into the new format and then, uh, help us in getting that kickstarted, that will be something really helpful, because we can't expect to rebuild the application that has been there for a decade. I'm not sure if Sean's going to let me put a percentage on it. But but there is there is similarities there that will translate fairly cleanly. Um, but again, that's, that's laid out in more detail on the website.

Okay. Thank you. Thank you. So in my early years as a UI developer, one of the things I ran into was limitations on components. React angular angular materials was early on when you were working with your client and they were doing their hybrid approach with like their custom. Did you see that as limited functionality or design? Like they wanted to control the design. So they did that hybrid approach or was it more of they couldn't find the right date picker or that kind of thing? I think initially, yes, a lot of what they wanted to do was definitely more from a design point of view.

Um, but again, we wanted to focus them on really just using it for where there is an actual feature requirement gap. I think everyone's going to be very gung ho about seeing these components and saying, great, I can put whatever I want in here. Um, but at the end of the day, as familiar as it may be to Pega, it's still not an out-of-the-box component. Um, so I think as best as possible, we try to guide them towards like, what is the real benefit you're getting out of this because you're adding time and what value are you really getting? So that was definitely something that I think they were initially really trying to push for. Um, but the more that they realized some of the trade offs, they were comfortable just keeping with what was provided out of the box. Perfect. Thank you. Um.

I think this may be a similar question, but I was told yesterday that. If even if you're not using the SDK, Constellation has widget areas where you can use your own components, but there's only a few of those. So you said earlier, you can't just put ten buttons, but you could put a button in a widget area. Could you explain more about what's possible? Well, I know in the Rd components, when you when you're trying to make a custom component, there's really three options. You could do a field template or layout. I don't remember the exact term, but and then the last is widget. So you can extend widgets. Um, but I think again, whatever the use case is would be a little bit.

But you know, it's just defined again in like react code as to how JavaScript, how you define that. But um, but I would recommend, you know, playing around with it. I mean, the, the literature is way more robust than it was even just several months ago. On DH components. There's like dozens of pages that listed out and you even have example videos. So I would recommend just giving it a shot and seeing. But yeah, you can build custom widgets. There are a few out of the box. The thing is you cannot just drag and drop a button, right?

You used to. Right? There's no option for that when you go to App Studio or if you want to use it, you have to go to the extent length of importing that custom code and then configuring it in your code, right? It's all custom. Once you import it, you have to go out like you are not out of the box anymore, right? So whenever there is an upgrade, there is a challenge you might face that no one knows because what is your custom product? No one knows, right? So eliminate those kind of upgrade challenges. For future.

We need to streamline how the UI should look like, and we should adhere to more of the out of the functionalities as is. Yeah, I should also call there are a number of additional components that Pega has that aren't standard in the tool, but that are built that can be imported that they themselves have built. So that also might meet the use case as well. I forgot to mention that. But yeah. So there is the component library. That's right. In App Studio there's additional components that are available on the design site. And then of course you could extend anything custom.

Right. Great. Thank you. Thank you. Hi. So I have two questions on Constellation. One is how do you guys set up? There are two ways of setting up. One is using Constellation URL and directly accessing the Pega website or through reactjs.

So how did you guys set up this? So for our client we were on Pega Cloud. So we just got that environment as is as is. So it's not an. Yeah. We didn't. Yeah we. So that was a good benefit for us to go on Constellation because they are starting brand new in Pega. Right.

So that was the one of the push to use Constellation to use the SDK functionality. So when we had that Pega environment, it was already upgraded with Constellation and we started using it. Okay, so we are one of the early adopters. So we use the same, you know, using the DS component to call the external URL and start using it. We tried to set up a react SDK. It's a longer process. Yeah. We have no idea how to do that. Coming to the second one, it's the common question everyone asks here.

How did you migrate? When you're talking about hybrid process migrating from the cosmos to Constellation. Right? How did you do that? Creating a template and then uploading it. Everything. If there is any lookup value available, like, you know, a custom lookup icon or a button, how do you guys, you know, overcome that? Uh, we didn't actually do any migration. This was this was their first go around.

So we didn't we weren't changing from traditional UI to Constellation. Um, so again, that's why we're not really necessarily saying this is absolutely the time to do it. But there is the literature is expanding on that, like I said. But we haven't we didn't have experience with that. With this. We did a couple of privacy on this, you know, building a scratch like new application. No issues migrating. We are still not. Yeah.

Yeah. I mean it's they are also trying to figure it out. Migration. It's a drastic change. We are having call with Pega every week. You know, uh, I don't know when the tool is going to be available. It may be in a marketplace place, or it might be an an extra service that Pega is going to provide where they will migrate the team cosmos to Constellation. But we don't know when it's going to, you know, be released. True.

Right. Yeah. I mean, I would recommend, um, in the Innovation Hub, um, on the UI side, there's a few folks there who maybe would have a clearer idea as to what that path looks like. Got it. Thank you. Sure. Um. Hey, I just got a question about the benefit slide that you showed. You know, you talked about faster UI ten times faster, and, you know, server side, um, you know, the load reduce and server side or client side, right?

So we actually are in the journey of considering Constellation. We are on eight six right now, but we got like existing case types from the past like six, seven years old. Now if there is no conversion to like, you know, the the person was asking, right. There's no easy way for us to migrate. We'll have to rebuild. If I go to my business and say A, we will consider one step at a time and then start rebuilding it in Constellation. Then the first question they'll ask is what benefits? Right? If I show the benefits that you showed saying that's faster.

They ask me how. I say it's because it's based on React.js. You know, React.js is the is underlying, um, you know, mechanism that's making it faster, right? So they say, then why don't we build it in react? Why should we use Pega? Right. So what's Pega's USP behind Constellation that I can give a convincing answer to my business so that they, you know, they are bought into both Constellation and Pega together, right? So, you know. I mean, I guess, uh.

Thanks, Tom. Um, I guess, uh, the main thing I would say is that, yes, you do get those benefits and yes, you could build custom, but then that is additional maintenance going forward. This is a one time revision that you'd be making, and then you have the benefits of the App Studio to directly see and preview and modify directly, as opposed to if you're going to go with a custom path, which is absolutely fine. That's why, you know, that is common approach that they're laying out here. But your maintenance going forward could be higher overall if you if you want to make some change. So I mean, I wouldn't necessarily say there's I think really the, the one of the main drivers of Constellation is because we had the UI and the development so tightly coupled. And what you end up getting is that people start modifying it. And if you make a little mistake here, a little mistake here, then, you know, grows and grows and snowballs into the fact where when you're trying to fix something as simple as, like maybe there's too much white spacing, you end up opening like 20 some odd rules to chase it, right? So the idea is that if you're going to use the prescribed environment, use it as it is, because everything is already prescribed and you can't really break it or go custom.

And there's really no at least in my conversations, there's really been no, no, please use this or please use this. Both are just as well. It's just let's break up this idea of this close coupling of the solution with the front end. And so it's really a question of what do you find easier to maintain. What do you prefer to go custom or would you prefer to use, you know, the out of the box. But of course, something to consider is that, you know, the more you go custom on the front end, how feature rich is it and how much do you need to build to accommodate that? It might just be easier to use what's available. Sure. Thank you.

Um. Hello? Uh, Philip. Yeah. Raghav from Booking.com. I have a couple of questions. Uh, on the slide. First of all, great thing. Uh, great presentation.

I really love the content of it. Thank you. First thing is on the Constellation adoption. So I see a the flow of things that should happen if it is a UI kit. What to do if non UI kit, what to do. But but what is the uh measure for applications which are using Pega strategic apps like CLM, KYC. So those people those apps do do Pega recommend them on Constellation or not yet? Um, not yet. Right?

That's why I said, like when we started using CS for Constellation, we started in a limited version because it was not there. So they are doing the migration one by one. I think the collection and some of them are there in the pipeline to do that. So once it is available then that will be a path forward. But I don't think everything is already there in Constellation. That's not so for now. They have to wait and then. Okay. And the second question is, I think the most of us have this, uh, the common, uh, gap in this, the modal dialog, there are model dialogs which are frequently used in the UIKit environment of Pega by all the customers and most of the business.

Uh, people love that to show, uh, content away in the modal dialog and then collapse it whenever they need to. What is your take when you had discussion with Pega on the modal dialog? And also there are toasters and drawers that are introduced. Is there a way we can leverage that from traditional Pega App Studio? Because as of now, we don't get to see that how to use it? I don't think there is a way in Constellation to use that. We also had a similar conversation, but the benefit for us was though it was a CS application, right? We had the dialect on the top already for them to use. So those were all configurable and exactly similar to how it used to be.

But for individual field, you are right, it's not there. And you cannot just use from cosmos to Constellation as of now. So what is the sentiment on the model dialogs? Particularly because we have to give a recommendation for the for the business as well, saying that this is out of the business for now. So we cannot keep the model dialogs in your designs of UI. Yeah. Do you have anything on that? Uh, no, I haven't really talked about that. I would recommend again going to the Innovation Hub, seeing if they have any guidance on that.

Okay. Okay. Yeah. We also had the same question, but nothing yet. They come. They are asking us to come up with different approach to how you can achieve it. But yeah, we have to have that. The reason I'm asking is when you say no, we should also have a method to it. But I don't know, uh, where to get that answer from.

Yeah. So we are constantly we give them a lot of feedback. Right. So they they did a lot of improvement on the product and we got a lot of patch now also this new patch is coming on on fixes right. Maybe one of the recommendation. They took a lot of recommendation and prioritizing it. This is one of them that's already there. You can check that they should have a website somewhere to maintain or show it. Yeah.

Yeah, sure. Thank you so much. Yeah. We got to clear the room, so, um, but feel free to find us outside if you have any additional questions. Thank you. Thanks, all. Thank you. So much.