PegaWorld 2026: Easy as ABC: Update Pega Infinity on Pega Cloud

Hello everyone. Thank you for your time. We are so excited to be here at Vegas and talk about updates. We're going to share some cool enhancements and the changes we have made to the update process, especially updating to Infinity 26.1. But one second. What is this, a, b, c I didn't see anything in the speaker notes. It's always bring coffee for updates, and I hope all of you have grabbed coffee for this session. Well, I thought it was always blame code updates, but we will get through this. Um, do you want to go ahead and introduce yourself? So I'm Meenakshi and I'm a product manager at with Pega. And my focus is to make updates as easy as for you so that you spend less effort in updating. And I'm the Chaos Product manager at Pega. I take roadmap, dreams and limitations and try to carve out releases.

Jokes apart. We have a very large team. We manage the underlying cloud infrastructure, the cloud network, the storage. We figured out the cloud security, compliance, security. So we have over 100 teams that look into the Pega cloud infrastructure. We do a lot of proactive updates, keep things ready, and most of it is not even known by all our clients. They just happen behind the scenes. But today, we're going to just talk about the Infinity updates to 26.1. Pega Infinity 26 is right around the corner. I'm sure you've seen all the keynotes. Cool new features announced by Alan Kerim, and you would have experienced many of these features in our innovation hub. The first thing that I tell all my clients is how do we get to it? And that's what our session all about. We will look at my PegaCloud. That's our self-service portal where you can go through the journey of Infinity 26.1.

We'll talk about how the process has evolved, the investments that we have made. So let's get started. The first question all my clients would ask is why should I update? And I will tell always the same answer is that the moment we finish the update on your environments, by default, you will get access to all the security benefits. We have an extremely large team that looks into all the vulnerability assessments. We conduct internal audits. We have over 25 plus compliance certifications that we go through every year. So all those benefits is packaged into the update. And this applies to your environments, right? When it when the update is successful. Same goes with performance benefits. We also have a performance team. They continuously perform a lot of tests on it to understand how we can be more cloud native. How we can leverage the auto scaling features.

Make sure that it's resilient to disasters. So all those features are packaged in the Infinity 26.1 feature. The feature set, and they would be available to you right from the moment we update your environments. You don't have to do anything. I don't have to adopt anything. You don't have to spend any effort any time. The moment the update is complete, all the bug fixes, performance improvements, security benefits, they're just right there for you. And that's why we always push our clients. We always encourage our clients to be on the latest and greatest all the times. Right? And I'm excited about the Infinity studio and the experience that it brings in with combining the build, the design experience, the build experience and the runtime experience. And all of this is weaved by an AI assistant. And that's the wonderful thing that you will look at when you are updating to Infinity 26.

So let's understand where is the industry moving today? Updates. No longer is that big painful project that happens every few years. Our leading enterprises consider updates to be part of how platforms operate. So did you know that organizations that stay current are spending a lot more time innovating and less time updating and catching up with with the latest versions? Yeah. And before, before we just talk more, just give me a quick raise of hands on how many of our on PegaCloud. Okay, perfect. And how many have gone through an update in the past? So okay. So this is primarily the first time many of you would experience an update to 26.1. So that's awesome. So I just want to add some statistics. Last year when we launched 25.1, we also launched our self-service portal. And all the clients that went through it. They did not have to call in.

They were able to use our portals to conduct their entire update journey, and 50% of them were able to finish their updates within 30 days or less. And I highly encourage that. You also log in to our PegaCloud portal. We're going to show the demo today as well on what that update journey looks like. Um, a small story. Back nine years ago or so, we started the project to simplify the updates. At that time we had to call in. We had to have race support tickets. There was a lot of coordination that needed to happen with our support teams. And since then, fast forward ten years, I would say that we were able to launch the near zero downtime update experience. It means that as we update the Pega applications hosted on your production environment on PegaCloud, you can continue to use the rules. You can continue to generate cases.

You can continue to source the application. All the integrations would work. So that's, that's where we were able to achieve in the last couple of years. So our vision is to make updates as easy as ABC. And honestly, I think a lot of you would agree that we have a long way to catch up. Now let's break down what this ABC is. So A is for assess. You understand what's really changing in this new version and what features are coming in and how would it affect your applications. B is to build confidence. You verify and test your application in a safe environment so that you don't have to worry about your root to live or your actual environments that are being used by the teams. C is when that final decision is made that you update all your environments. So A and B is all the planning and the confidence that you establish.

And C is when you actually do the updates. So this is a simple, structured and guided experience and we'll look through it. What does it look like. So let's start the update. We'll do this. We'll coordinate this between me and her. So I'm going to talk about all the old features that I developed when I was a product manager, and she was responsible for all the new features that are going live in the next couple of weeks. So, so the way it works is previously, if a new version of our platform used to come out, people had to go and read all the release notes of various product documents. So let's say you had customer service, you had Sales Automation and and on top of Infinity and customer service or finance, you would have to download those release notes. You'd have to read through, let's say 60 pages each.

That's a lot of effort. So all that is going away and, um, and she's going to talk about the new features that we have launched around that. But yeah, it's a three step process. You read all the release notes, you understand what has changed. Then you go to the marketplace, you download some few tools to assess the update, but that's just assessment. The next step is to actually conduct the update. We provide you a clone environment for verification. We then schedule all the updates. And then finally on the production environment we're going to talk about go no go today. So let's dive deeper into each of these sections of this update process. And starting with section A, I'm actually going to talk about how the release notes part has changed. Let's dive into it. And honestly, if you're moving, let's say from 2021 to 26, you're skipping two versions in between.

Yeah, two versions in between 2022 and 25. And then you have 26. So imagine the effort that it takes to go through all of these release notes in understanding how your features are changing between these versions and more to if you're using different products in Infinity, for instance. Customer Service. Pega Platform. Its exhaustive process. So what we have done is on PegaCloud, you have my PegaCloud. That's your cell service solution. You can manage your subscription using my PegaCloud to manage your environments or your route to life. Now, when a new version of Infinity comes out, you would see that a new version is available for you to update, and it will prompt you to start the planning through assess update. Now let's understand what is this assess update. We know we are solving the problem of reading release notes and many of such release notes, but what is important for the update?

It is the update instructions for the features that you use. Now these update instructions are consolidated from all the versions that's applicable to you. So if you are on 241. We will read through all the release notes and generate a comprehensive update instructions for you if you're using customer service. We will combine this information from Platform customer service all through the power of Knowledge Buddy, so that you have update instructions specific to the products you use, and from the source version to the target version that you're going into. What does it do? It basically narrows down the amount of information overload that you have through all of these release notes. So all that you need to go through your update and plan your update is update instruction. And moreover, on PegaCloud, we also eliminate any noise that is not needed on PegaCloud because we manage the infrastructure and operations for you.

So Hazelcast. No worries. Tomcat no worries. So all of this instruction is eliminated from from this feature. Once you have it, you can actually share it with your teams and assess it further to understand how each of your application would be affected because of these update instructions after the update. So this is this is great. So you're saying that if I log in to my PegaCloud now I should see an update feature that based on my products installed on PegaCloud, I would be able to understand what has been released. What are the cool new features? What should I be worried about most? Right. And when is this feature coming live? When it's already. Out. There. It's there. As soon as Infinity 26 comes out, you will have it again updated to Infinity 26. So let's dive deeper into the second part of the SS update.

Now that I know what's the exciting features in the product documentation, the next step is to understand and estimate the effort that is required to update my application. Is something going to break or is something going to need to need to be changed by my development teams? How do I estimate that effort? How do I understand what needs to change in my app prior to the update? So in the previous world, we used to go and log into our Pega marketplace, and you had the opportunity to download these upgrade checkers. They are by product. So if you are a customer service consumer, then you go and download the customer service upgrade checker. If you are using Sales Automation, then you use the Sales Automation upgrade checker and then you have to download, you have to install this in your PegaCloud environment, and then you have to hit go, and it's going to come back to you with a report of assessing your application with the latest Infinity 26.1 features and say, okay, we see that you have overridden all these rules, and these rules need to be changed.

Now, just a word of caution. If you stay true to the Pega out of the box features and did not override the rule sets we shipped, you don't have to worry. Like for majority of our customers, These checks will simply pass, but the platform is quite open ended. It allows you to do complicated things, and some of our clients may have extended the platform and changed and introduced custom components. They might have written custom Java activities. So these upgrade checker tools, checks, looks for rule overrides and flags them and kind of gives you the estimate of, of what it would take when we are going to perform the update. And can you show us what's changed. Let's understand what's changed. So you looked at all the update tools from marketplace. Now we will bring this update readiness assessment within your Infinity studio or within your app studio.

So this will not be packaged with Infinity 26, but on PegaCloud will independently release whenever a new version of update assessment tooling is available. You no longer have to worry about what tools to download from marketplace will pre-install it for you on your desk machines. Now, as a developer, if I want to assess if my application is update ready, I can always go to the Infinity studio or the App Studio and evaluate if my application is update ready. Now what it does is it would highlight the rules that should not be overridden. For instance, it will highlight all the deprecated features that you're using, the withdrawn features that you that would go out of support or. It would also highlight the configurational changes that you should change for your update to work for your application to work after the update. Now, once I understand if my application.

Or is my application ready for update? Now imagine in my router there are multiple applications that are running and a decision maker who is planning the update for your router live on PegaCloud would need to understand, are all the applications update ready? So to achieve that from my PegaCloud, you will soon have an integrated report that would give you update assessment across all the apps that live in that in that route today. What does it mean? Are all of my apps update ready and what are the key required actions for me to make my applications update ready? By this time the the the, the user would understand what is the effort required by each of the application teams. Certain applications could be update ready low effort. Certain applications will not be update ready high effort. So it will give you a good estimate of what is the work required to test your application in the next stage.

So this is great. So you can do the update assessment at any point in time. There is no rush. Whenever you are comfortable, there is no charge to it. You just have to log in to my PegaCloud and run the update assessment and you would get a report on based on how far you have progressed in your software development lifecycle. On PegaCloud. Right. So once you feel that, okay, I have a good handle on this, I know what to change for. As I said just before that, for most parts you would not have to make any changes. If you are using out of the box features and you haven't customized anything on a platform, and then you're ready to begin the update process, the first step is to ask for a clone environment from Pega. This is completely free of cost. We give it for the first 30 days and this is.

You can choose. Do you want the clone update environment from staging from your dev environment? And you can make that selection here. In just a couple of hours. You will get a notification that your clone environment is updated and you're ready to begin your assessment. So how do you begin your assessment? So as part of your software development lifecycle, you are developing on your dev environment, testing on your QA environment, and you're pushing the application changes to your production. That's probably you do every week, every few weeks to months, depending upon your Sprint cycles. And as part of that process, I'm sure you have a lot of automated tests. If you do not. I highly encourage that you have a lot of automation to verify your functional nature of your application. So you would exactly run the same tests on this updated clone environment. You would verify the functionality of your application.

See the workflows are working fine, your external integrations are working fine. If you have inbound calls to your Pega application PegaCloud, you would verify those. Basically run your simulated automated tests, and shortly we'll talk about how you can generate them using GenAI as well. But you would run the same tests to get confidence that the new updated Platform is running fine for your application. Nothing is breaking and you are ready to go. So once you have that confidence, the next step is to start scheduling the live environment updates for your due to life. So before we get there, let's understand how is this process even changing? So as you start your UAT and you have requested an updated clone. So this is what we where we verify our application safely. You get an isolated environment. It doesn't really impact your outer life. Your development teams are comfortably testing, you know, developing applications.

In the older version, there's a separate effort going on and validating your application against a newer version. So what we are going to do is when you get your updated clone, we will pre install the update tools for you and we will run the assessment for you as well. Now this assessment would be available for you to use. This will have all the required actions that you need to take for your application to work. Post update. And the second key part would be the testing. So as your teams start testing, you need to understand is the testing complete before you take the next step? So we are bringing in the other key information, which is how many of your case types are validated in that environment or how many applications were accessed in that environment. These two information is going to give confidence to a decision maker that, am I done with the testing or not?

And am I good to proceed with the actual update or not? Now, as you progress the testing, the to be state would be that there are zero outstanding actions pending for your application. So by the moment you are done with the testing, you have validated all the actions you have upgrade fixes if. In case your applications need. So. And once you actually start rolling out the update to your router life, these upgrade fixes will be applied on your application so that your application continues to work. And thank you. I got to ask you though, why do you get to speak about all the new cool features? And I only talk about the previous use cases that you modified, right? But next time I'll have to change that. No worries. So we saw until now that you could look at the release notes using the power of GenAI.

You could understand the new enhancements we made and how are we going to impact your application if you have customized, of course. And then we also looked at the fact that you have an access to a updated clone environment for for 30 days to assess the impact of the update on your application, get confident. And now that you have done these steps, we are ready to take the next step. The next step is to start scheduling the the updates for your environments like production, your dev environment, your staging environment and there is no rush. Unlike our competitors, we do not force update by a given date. We strongly believe that if we have a great product out there, you would want to go to the latest platform at your own convenience. So as I said, no force updates here, no deadlines here. It's completely at your convenience and you can start feeding these schedules the moment the Infinity 26.1 is out.

Okay. There's one thing that I want to touch upon that the update process, any, any philosophy around the update process is a process of, as a philosophy of risk reduction, right? So as you go and start updating your production environment, how can I minimize the risk? So I minimize the risk by looking at the release notes. I minimize the risk by doing UAT testing on my updated environment. But now you have one final method to reduce risk, which is the go no go process on the production environment. So for the last time, you would get access to a temporary production URL. On the production environment, a temporary production URL is nothing. But you can think of a single web node that has access to the new rules that we are shipping as part of the update and, and the temporary data schema. Right. And, and you can log in to the application.

You can perform visual confidence testing that my application looks great. My UI is fine. Some of my workflows are looking great out there. And once you are confident, then you hit the go button. You probably have like 30 minutes or 1 hour or so to perform this visual confidence testing. And as soon as you hit the go button, we will perform the rolling restart of your production environment. Everything would be near zero downtime. And you can. And your users can continue to use their application during this time. And that's our process to complete the production environment update. So to make updates faster, we we have been doing this for the last ten years. A lot of our clients are coming through from various versions, from eight dot CDs to 23 to 20 4 to 25, and now 26. So we do feel and believe that having automated tests is key to make this process faster.

The fact that and this is not something new that you have to do only for the process to update, it's the same set of automated tests that you would run anyway for pushing your changes from dev to staging to production. So we highly encourage that you invest in a automation test strategy. And she's going to talk about some of the features around how we can make it easy for you guys to create automated tests. Go ahead. All right. So let's understand how is Pega application test helping us? If you have not already checked out, please check out Innovation Hub to check the test automation feature. Um, so as we discussed, we need to have a strong test foundation not just to certify our applications as we release new changes and bring in new experiences for our users, but also to verify and update in less time and less effort.

So for that Pega application tests starting Infinity 25 gives you an ability to generate API and UI tests. Having a strong foundation using Pega units, API and UI tests, you can validate your application in no time and less effort. Now, once you have generated these tests right, you need a way to trigger these tests or execute this test natively on PegaCloud, so you no longer have to depend on any external launching tool to run these tests, such as Jenkins or Selenium Grid, or so on. So these are playwright tests. These execute right within your PegaCloud ecosystem. Now, if you want to integrate this further to your application development process, you can always integrate these tests with deployment Manager. Deployment manager gives you the capability to run both API and UI tests for your applications. Now it also provides you the capability of how can you manage the evidences of the test?

It gives you the ability to review the test summary. It basically helps you go through the recorded videos of how these tests ran when in the headless mode. So it provides you all the required Evidences in test automation management. Now we've understood how application tests can be, or how you can build a strong foundation of automated tests. Let let's understand the second piece of it, which is pretty much the application development practices. And I think most of you are already aware of some of these concepts. First is extension. First design. We talked about it. No, not we do not recommend you to edit out of the box rules. So always go with an extension first approach. Second, adopting Constellation will minimize all the customization that is available today on a traditional UI application or Pega Infinity. So Constellation will help you configure your application in a way that their minimal customization and so is the overhead reduce on you.

Second is quality and guardrail. So guardrail we recommend that you should have 90 and above. And second, you should have clear segregation between the UI, the business logic layer and the data layer. Third one is API and configuration. The more you extract your configuration out of the environment, the easier it is for you to manage those configurations. Second, you do not want to juggle between the update issues and the API integration issues, and often our clients get stuck there. So having a strong, strong versioned APIs and stable APIs is key for a faster update. So before I start talking about these additional new programs we are launching. So call to action. Once you go back from Vegas to all the different countries who came from, I highly encourage that. You look out for the GA of Infinity 26.1. Remember those four things? Number one log in to my PegaCloud.

Click on the Assess update feature so that you can get access to your gen AI generated release notes, plus update assessments. To understand what is the level of effort that you might have to perform for taking the new update. So that's one. The next step would be request the clone update and environment and start playing around on how the application looks like on the updated platform. And step three schedule the live environment updates with Go No go for your production environment. So we are launching these two new programs. The first one is called the Pega Update Success Program. So what this program does is that we have now a dedicated Pega testing team that is going to perform Pega update testing on your application with your tests that we have provided to that team. So think of a dedicated VPC in PegaCloud that our test team will have access to your application.

Not your data, just your application. They would have a knowledge transfer from your team to run some of these tests, understand your application and run these automated tests. And every time as we head to the 26.1 GA, our testing team would take the latest build, apply the updates to your application, run your test just to make sure that the next version that we are launching does not break your application. Is regression free. So this is the first program. It's completely voluntary. We have a dedicated booth in the cloud section, so feel free to come and register for this as well. The second program is an early access program. So what we would do is in your dedicated VPC, we would provide you with a Pega environment that would run the latest version of your application. And you can log in, you can check out the new features that we are launching.

And there would be a dedicated team that you can provide feedback to you. This is to make sure that the features that we are launching in Infinity 26.1 are complete. You want to adopt them, you would love them, and you can provide feedback to make sure that whatever we are launching has your input. And this is, I think, the opportunity you guys have to shape how the product is going to be released right before GA. So two new programs I highly recommend to subscribe to these programs. And we would be at the booth and we can cover more details about them. But yeah, that's pretty much what we wanted to cover. So we can open the floor for questions. And that's you, Mike. So please feel free to walk up to the mic if you feel like asking the question from where you are sitting right now, just shout the question.

I'll repeat the question for you so that it's recorded on the mic. Okay, I. Had a question like I was going through the PDC, they were saying PDC assistant is also part of the GA product. Is that. Is that part of the GA or it will be in another version of it? Yeah. So PDC stands for Pega diagnostics. Cloud. So for the benefit of the audience, I'll just explain the product what it does real quick. So as you develop your applications on PegaCloud, you want to be able to monitor how the application is performing. So we for that we have Pega Diagnostics cloud PDC. So you can log in. You can monitor the health of your application. It also does something like HTTP monitoring. It's going to look at the inbound traffic to your app. And it's going to look at HTTP status codes. And then we measure the HTTP like 400 200, three hundredths to understand whether there was a dip in the request response or not.

So great tool for monitoring the health of your app. It also has recommendations on how you can improve the app, like slow performing queries or how to look into some of your integrations. So it has all that. So how does it fit into the ecosystem of updates? Right. So as I'm developing my application right after staging, do you want to talk about the update assessment feature that we have? Sure. So yeah, I think, um, as you develop your application, right. And you want to assess whether your application is stable after a new version is deployed and whether your environment is stable. We do monitor, uh, the new deployments in staging, and we use PDC to understand if there were any new exceptions that were raised by this new version of application. We also monitor any critical DB events and any critical events that would indicate that the environment was so long stable.

But something happened with this new build because of which the environment is no longer stable, and that would flag that that probably that deployment is not really ready for production. So the user can go ahead and review that, that, that I think you might have really checked out that also in the PDC booth today. Uh, and you, PDC pretty much tells us whether we are ready to go to production or not. But also to answer your question, um, PDC is independently released, so any features that you saw in PDC are already live and it doesn't follow the same schedule as Infinity 26. You've got to ask two more questions. So does it consider the frameworks also because if I'm going to. 26 and if I have the framework. Customer Service. So how does it work in the framework? Yeah, that's a great question. For the benefit of the recording, I'm just going to repeat the question.

The question is depending on the products that you have installed on PegaCloud as part of your contract, let's say Customer Service or Sales Automation, or one of the vertical frameworks or horizontal frameworks that we've shipped like Customer Service for finance or Sales Automation for Insurance. Does our update checker. Um, on my PegaCloud that we plan to automate is also going to look at all these different verticals and horizontals. Right. So I would like to answer that. So we are supporting only 23 and onwards on PegaCloud for update checker. Um, so 8.8 the marketplace component will still be able to assess it. But the new update checker, that update component that we are having for PegaCloud would not be, would not be supported for 8.8 because it's already out of support. Talking about out of date support. Like what are the is there a cycle for 26?

Um, Infinity. Like it does it have the standard same cycle, like standard and extended support kind of thing? Does it follow the. Yes, that continues to remain the same. Okay. So typically we have like one minor version update every year, like maybe 25.1, 26.1. And then we have a set of patches throughout the year. So that's, that's our cycle to ship software and patches for zero day fixes required. Like we also release Hotfixes. So if you remember the log for J situation a couple of years ago. So Pega was one of the fastest company to deploy the log for Hotfixes across the fleet of over 3000 to 4000 environments. We have internally something known as the Global Operations Center. So that's a tool developed on Pega Infinity. Our operations teams uses them uses that tool. So basically what it does is it has the orchestration and automation to take a hotfix.

And then you can select the whole fleet and just click deploy. And it will just deploy the hotfix and restart, let's say over 70,000 EC2 instances in the next couple of days. And we can time it. We can choose do all of that in three days or do all that in seven days. And it has the intelligence to figure out like it's a rule only hotfix, then no restart required. If it's a rule N code hotfix, we deploy the code then do the restart and deploy the rule. So it does all of that internally behind the scenes. I just want to add that um PegaCloud has invested, I would say millions of dollars over the last 5 to 6 years developing this automation to push out hotfix updates, Infinity patches in a zero downtime way. And we, I think, have over 100 engineering teams that develop various aspects of control plane, security, plane.

Um, the compliance aspects, testing, infrastructure, networking, storage, like so. So everything gets like tested in multiple pipelines and tests. Um, one question that did not got asked is how does Pega maintain upgrade compatibility as we ship new versions? And how do we minimize the risk of making a software generally available? Right. So as engineering teams create the next version of Infinity 26.1, we have pipelines that create these builds and run thousands of tests in different customer simulated scenarios. That's the first step. Second, as we create alpha beta builds, they get deployed to some of our internal applications that are mission critical for us. So for example, the tool that you use to raise support tickets or the global operations center that we use to deploy Hotfixes or patches or infrastructure updates. PDC Deployment Manager so these are all Pega Infinity apps. So we first apply the update on these mission critical apps.

Because if they are down we are talking about like huge outage situation for us. Like my phone would ring nonstop if that happens, right? So, so we go and deploy these updates to these internal tools that are mission critical for us. Then we as part of these programs, we have a handful of clients where we go and apply the update to make sure that we are not introducing regressions. And then we start this process for all our clients that are when the Infinity is generally available. So that's the kind of investments we have made to make upgrades better for all our clients. And I would highly encourage that. As soon as this version is out, plan this so that you can stay current and on the latest version as soon as possible. So you have Automated test cases. So suppose I have a testing team who want to create a test.

So do they have to log in to Infinity studio to create Pankaj Jain? Yes that's right. So it is available on App Studio. It's supported on Constellation based applications. So you can actually choose go to your application, choose the case types for which you want to create those test cases. It is the source basically the the source system where these tests are managed is Infinity studio or to be precise. App Studio. They are not really maintained the way the test cases are usually or test scripts are usually managed in any third party automation tools. That can be fine, but if I want to do that, I need to give them the correct. That's right. Yeah. Yes. Not code changes, but test changes. Changes. Uh, from the access point of view, I think, uh, I'm not really sure about how the access is managed for test versus dev.

Uh, we can probably check that out in Innovation Hub. There is a dedicated team on that. Uh, but yeah, I think, uh, they, they should have access to managing tests only. Probably you can have. Yes, yes, there could be privileges. Privileges for, for managing tests. I think it's possible. So I highly encourage do check out our application security booth in the innovation hub. You will get dedicated support there for answering questions on how to configure access, how to configure RBac and Abac, using the Design studio to make sure that your enterprise is, um, well, segregated. In terms of access control, I think there are some cool new features that we have launched in that space. We are trying to also introduce a default. So based authentication for admin administrators and trying to get away from basic access control. So that is something I highly encourage that.

I think you would be interested to check out at the application security booth, right? Yeah, please go ahead. So, um, I have a question related to Hotfixes. And these are not vulnerability related. Hotfixes. But suppose you when you launch this, any version, right, let's say 26.1, some client faces some issue which was not identified and you decided to create a hotfix for that. Are you going are you guys planning to improve the communication on that so that all the other clients will be notified? And do we have to like upgrade like patch upgrade to get a hotfix or, or it can be just installed. And because we are facing that issue today and recently we faced one issue where there was a hotfix which Pega created, but it was not communicated. and it created like huge outage in our production. And then we came to know that Pega already knew about that issue, and there was an existing hotfix, but it was not rolled out like we didn't know about it.

So is there anything done for this communication? Yes, I think that's a great question. So some more details before I start answering that question more directly. So I would say that when this hotfix right. So there are different situations. One is when we have a vulnerability that we detected in one of our, let's say open source code that might be using log Forge was a classic example that affected a lot of those companies. I just want to remind that when we go and create a hotfix, our aim is to fix the security of all our clients at the most rapid time possible, right? Like we are looking at hours. So we are doing the like, it's not like everything can be in depth tested for days and weeks to fix a security of a client. So that goes with minimal testing whenever we are in a situation like Log4j2.

So that's the kind of hotfix we're talking about as we as the days progress and we start deploying those Hotfixes, obviously we might have encountered some issues and I'm very sorry that you had to encounter that issue. Um, but then once we do, then we start integrating that fix in a second hotfix and also in a forthcoming patch so that that issue is never repeated. So that's how it works. And during this process, I would say that the scenario that you mentioned was, let's say I am updating my clone environment for verification. And I encountered a scenario that my application is not working, which means now we have to provide you with a fix ASAP. Right? And I think that's the step one for us. The fact that we couldn't upgrade our client and the client is on hold and waiting for the update to be completed.

We take that very seriously. Our support teams were declared as the highest critical incident. It would engage the right engineering teams at Pega and make sure that our local change, or a hotfix or the next patch is provided to you as soon as possible. So that's that's our process right now for any regressions encountered during the clone update testing for. We hope it doesn't happen because we have a lot of checks and balances before we update the production, but it does happen once in a while that some of our clients, we might realize something that is on production, but we never found that on the staging or on the dev environment or on the clone updated environment. So that's why we highly encourage all our clients that your QA system mimic, or it should be near about the similar way to your production. And if it is not, that's when you might have some escape defects to production, right?

We also have the production mirror offering where you can actually perform load testing of your application, and that's almost 100% kept in sync with your production. Like you have a benefit to request for syncing the production with the production every month. And Meenakshi's teams on the plan match is about to release a feature that will allow you to do that from deployment itself to move case data from production to production, or any other system for that matter, to to do the testing. I hope this clarifies the question. Okay. Well, it was nice having all of you. Thank you for your time, and I look forward to successful Infinity 26.1 release, and I hope that you are going to be on it. In the first month of the GA of Infinity 26.1. Thank you. Thank you everyone.