Published Release Notes

For Microsoft SQL Server deployments, change settings to create data types in Integration Designer

For on-premises deployments that use Microsoft SQL Server, set the Pega-Reporting/reporting/useMergeHintForRRquery dynamic system setting to true. If you do not configure this setting, you might not be able to create a new data type in Integration Designer that uses Pega as the system of record. Configure the setting as follows:

• Owning ruleset: Pega-Reporting
• Setting purpose: reporting/useMergeHintForRRquery
• Value: true

For more information about configuring dynamic system settings, see Creating a dynamic system setting.

Translation support added to application guides

You can now localize the content in your application guides. By referencing paragraphs instead of rich text in your chapters and tasks, you can provide guidance to users in their native language.

For more information about application guides, see Creating a guide for end users.

Data entered in a new harness is lost after a sync operation

If you create a case in an offline-enabled application and enter data in a new harness, this data is lost after you click Submit and the sync operation takes place. For more information, see Offline capability and Enabling offline support for cases.

Fetch quality metrics for Pega unit tests by using the REST API

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.