Change management for Pega Cloud
Periodic system maintenance is essential to maintaining the ongoing stability and security of your Pega Cloud® environments, as well as allowing you to benefit from ongoing innovation in Pega Cloud. This maintenance is part of the services that Pega provides for Pega Cloud.
The maintenance features ensure that virtual spaces and the environments that are associated with Pega Cloud stay up to date with software updates and patches, and the latest features and services that are included in Pega Cloud.
Scheduled maintenance window
A maintenance window is scheduled for each client, with a strict timespan during which Pega Support can schedule and subsequently perform maintenance on the environment. By default, the maintenance window is set to between 11:00 PM and 5:00 AM in the local time zone.
Contact Pega Support to request a different maintenance window.
Infrastructure updates
Infrastructure updates are a part of the standard maintenance of Pega applications.
These updates include:
- Security and performance benefits
- Service enhancements
- New capabilities
Infrastructure updates do not change the version of either Pega Platform or the strategic applications deployed. The update does not cause any downtime for your application.
| Pega Responsibilities | Client Responsibilities |
|---|---|
| Manage communication - notifications before update begins and after complete | Reschedule any conflicts during the maintenance window |
| Document any issue that was discovered during update process | Review notifications that include details about an upcoming software update |
Software patches
In the following image, click the + icons to see the Pega Platform release naming conventions:
Pega Platform patches, when made available, are deployed in your scheduled maintenance window. These patches improve components like security, supportability and reliability improvements, and bug fixes.
Patches are created from client feedback. It is important to frequently adopt patches to enjoy a secure, stable, and effective solution. When patches are available for a minor release, it is key to note that the previous patch for the specific minor release is no longer available when another patch becomes available.
Pega Cloud applies the patch to each environment with zero downtime and without affecting the environment infrastructure.
Change requests
If you need to request changes to your Pega application environment, submit a change request through My Support Portal (MSP).
A change request case is created. These change requests are taken care of immediately unless there is a request for changes to production-level environments. Production-level environment changes need to be approved by the Change Advisory Board (CAB).
The Pega Change Advisory Board (CAB) upholds and enforces all Pega Change Management Policies while assessing, authorizing, and prioritizing changes that are requested for production environments to prevent negative impacts on the environment.
This Topic is available in the following Module:
- Pega Support v1
Want to help us improve this content?