Data entered in a new harness is lost after a sync operation
Valid from Pega Version 8.1
If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Offline capability and Enabling offline support for cases.
and the sync operation takes place. For more information, seeFetch quality metrics for Pega unit tests by using the REST API
Valid from Pega Version 8.1
You can use the REST API to fetch quality metrics for the Pega unit tests of your application, such as unit test compliance, unit test execution results, test coverage, and guardrail compliance.
You can use the metrics returned by the service for gating purposes in a release pipeline.
For more information about the Pega API, see Pega API for Pega Platform.
Known issue: SAML IdP import uses only the last certificate
Valid from Pega Version 7.4
When you configure the identity provider for a SAML SSO authentication service, the backing keystore rule for the verification certificate is created with only the last certificate from the IdP metadata, instead of using all of the certificates.
Additional activities in table layouts
Valid from Pega Version 8.4
Table layouts now provide you with the option to run activities either before or after updates to a table. This gives you greater flexibility when you design user interfaces.
For more information, see Configuring table activities.
Semantic URLs in Pega Platform
Valid from Pega Version 8.5
URL addresses for Pega Platform™ applications and application resources now appear as clear, meaningful paths. This enhancement helps users understand the structure of the application that they are using, which makes navigation quicker and more intuitive.
Support for Thai calendar
Valid from Pega Version 8.4
Pega Platform™ now supports the Thai solar calendar. The update improves readability for users who rely on this date format, and enhances their experience and engagement.
For more information, see Configuring the Thai calendar.
Guardrail warnings for UI components
Valid from Pega Version 8.4
Pega Platform™ now displays guardrail warnings about user interface elements that might be high maintenance. With this enhancement, you can ensure that your application meets the latest development requirements for efficiency and ease of use, and save time during future upgrades.
For more information, see Reviewing UI components.
Improved contracts for implementations
Valid from Pega Version 8.4
For more complete contracts, automations now support embedded pages, default values, and picklists. These enhancements provide a more robust model for inputs and outputs that is easier to update and maintain.
For more information, see Viewing automations.
Increased visibility of strategy design changes with simulation batch tests
Valid from Pega Version 8.4
Improve your understanding of the impact that individual changes to strategy design have on the decision funnel by running batch simulation tests directly from the strategy canvas. With batch simulation tests, you can check that your strategy changes produce the expected results, and immediately see the results in context.
For more information, see Increase the real-time visibility of strategy design changes with simulation batch tests (8.4).
Upgrade impact
After an upgrade to 8.4 and later, simulation outputs produced from earlier versions cannot be used to view canvas counts.
What steps are required to update the application to be compatible with this change?
Following a software upgrade to 8.4 or later, clients must re-run existing simulations in Decision Funnel mode to view the counts in the canvas.
Enhanced OpenAPI Specification generation
Valid from Pega Version 8.4
To better understand the purpose of your REST API, you can now generate a more complete OpenAPI Specification (OAS) from REST service rules in Pega Platform™. The system uses relevant records to build an accurate schema definition for page and page list outputs, and generate stronger schema type definitions for all inputs, outputs, and fields, such as array
or boolean
. You can also generate OAS by mapping values to JSON or Clipboard in the request, or mapping values from JSON or Clipboard in the response.
For more information, see Service REST rules.