@FranciscoJavierC9622 

When updating Pega from version 8.7 to 8.23 on-premise, you will need to follow the standard software update process which integrates the latest Pega automation technology to support seamless adoption of the latest Pega Infinity features and improvements across environments using your development pipeline. During the environment updates, you will experience environment downtime, during which time you cannot access Pega applications. Any data saved to the database before the update process is never lost during the update process. User sessions are not persisted: active users might be logged off during the environment restart. You should reschedule any upcoming activities, such as job schedulers, before you initiate the update process. If you update from Pega Platform version 8.2 or earlier, stop all background processes you initiate the update process and restart the stopped processes after you complete the update process. If you update from Pega Platform version 8.3 or later, the update process waits up to 30 minutes for any activity that is running in the background to finish its work; if the activity is not finished after 30 minutes, the background process is terminated. You must also migrate your existing mashups; beginning in Pega Platform 8.5.1, Pega Web Mashups include a channel ID in the mashup code for validation with your mashup server. Create new mashup code on your updated, cloned environment running release 8.5.1 so the mashup rule form includes a Mashup channelID that is automatically included in your application testing rule in your update pipeline. Be sure to update existing website configurations with the new mashup code.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

On-premises update process for Pega Infinity release 8.4.2 and later for other ap

On-premises update process for Pega Infinity release 8.4.1 and earlier > The on-premises update experience

Updating Pega Infinity for on-premises environments

Pega Platform changes with update impact