Pega Platform changes with update impact
As Pega Infinity software advances, Pega is committed to providing software updates with minimal disruption so both you and your customers can continue to access and use Pega applications throughout the entire update process.
To achieve this goal, the development process follows a near zero-downtime standard that attempts to ensure that the latest Pega software features and enhancements impact your applications as little as possible from release to release. The near zero-downtime standard sets the following goals:
- Changes allow your applications to run during updates.
- Changes are backwards compatible for your applications that are based on Pega Infinity.
- Performance and security enhancements may impose a minimal update impact, since application stability and security are our highest priorities.
For updates from Pega Infinity release 8.4.2 and later to release 8.5.1 and later, Pega supports near-zero downtime updates on Pega Cloud services and on-premises environments (for Apache Tomcat and PostgreSQL). For details about the process and standards for Pega software updates, see:
- Pega Cloud update process for Pega Infinity release 8.4.2 and later
- On-premises update process for Pega Infinity release 8.4.2 and later for Tomcat and PostgreSQL
Known update impact in Pega Platform 8.7 features and functions
As part of its near zero-downtime commitment, Pega has reviewed the features and fixes in Pega Platform 8.7 and has identified the following areas where a minor update to Pega Infinity 8.7 will have an impact. An update impact occurs when a feature or enhancement imposes a noticeable or blocking change. Click each area to learn about the impact and a workaround for it.
Known update impact in previously released features and functions
Because impacts are cumulative, if you update from early versions of Pega Infinity, you should review the following update impact details in previously released features and functions.
Known update impact in Pega Platform 8.6 features and functions
As part of its near zero-downtime commitment, Pega has reviewed the features and fixes in Pega Platform 8.6 and has identified the following areas where a minor update to Pega Infinity 8.6 will have an impact. An update impact occurs when a feature or enhancement imposes a noticeable or blocking change. Click each area to learn about the impact and a workaround for it:
- Updated selected third-party JAR files to support Pega Platform functionalities
- Addition of Servlet Management
- Additional connection pool parameters for JDBC URL external databases
- Upgrading to the secure threading mechanism for email bots
- Deprecation of EAR deployments in Pega Platform 8.6
- Text predictions simplify the configuration of text analytics for conversational channels
- Upgrading to Hazelcast 4.x requires downtime during updates to Pega Infinity 8.6
- Legacy Parse XML rule configurations must be updated to edit them
- Connect MQ rules configured with alias queue do not work after update
- Insights from 8.5 require additional configuration after update
- Data model inheritance does not depend on ruleset context
- Improved indexing of StringList and StringGroup property types
- Connect MQ rules configured with alias queue do not work after update
Known update impact of Pega Platform 8.5 features and functions
Pega has reviewed the features and fixes in Pega Platform 8.5 and has identified the following areas where a minor update to Pega Infinity 8.5 will have an impact. Click each area to learn about the impact and a workaround for it:
- Tamper-proof Pega Web Mashup loading
- Visual Business Director data is automatically cleaned after a retention period expires
- Uploading customer responses into adaptive models is no longer available
- New database tables for email bots
- Native synchronization indicators for offline-enabled mobile apps
- Improved case auditing in App Studio
- Failed Robotic Assignments work queue type changed to Standard
- Improving basic access control
- Limits on active data flow runs
- Support for validations in Declare Expression rules
- Close button on a pop-up application update removed from App Studio
- Removal of Pega Mobile Client 7
- Web portal reuse removed from the mobile channel
Known update impact of Pega Platform 8.4 features and functions
Pega has reviewed the features and fixes in Pega Platform 8.4 and has identified the following areas where a minor update to Pega Infinity 8.4 will have an impact. Click each area to learn about the impact and a workaround for it:
- Increased visibility of strategy design changes with simulation batch tests
- Relationships between elements of Microjourneys in application inventory
- Pega Express methodology in App Studio for successful Microjourneys
- Personalized views in table layouts
- Custom application URL alias in the application definition
- Rules can no longer access Pega internal Java packages
- Support for the JSON Web Token Bearer grant type for accessing external APIs
- PDF/UA support
- Updated default dynamic system settings for requestor pools
Known update impact of Pega Platform 8.3 features and functions
Pega has reviewed the features and fixes in Pega Platform 8.3 and has identified the following areas where a minor update to Pega Infinity 8.3 will have an impact. Click each area to learn about the impact and a workaround for it:
- Improved control of case locking and retry mechanisms
- Automatic management of run-time context for background processing
- Cassandra 3.11.3 support for Pega Platform
- Improved rich user interface controls in IVA for Web Chatbot
- Test coverage support for more rule types
- Set a time zone for the DateTime control
- BIX ruleset is now included with Pega Platform
- Improved performance for work ID generation
- Support for the decisioning-enabled NLP text analyzer in IVAs and Email Bots
- Unit testing support for more rule types
- Create and view application settings in App Studio
- Text analytics models editing and versioning
- Text analytics models migration
- Simple associations for quickly joining classes
- Association changes after update
- Change tracking tab removed from declare expressions
Previous topic Pega Customer Decision Hub hotfixes Next topic Pega Platform version support for Pega-supplied applications