Published Release Notes

Ability to restrict access to the Import wizard

You can now restrict access to the Import wizard so that users implement an automated pipeline to deploy changes between environments such as staging and production. Deployment Manager is one method by which to create pipelines. By using pipelines to propagate changes, users can apply a standardized and automated deployment process for migrating their applications.

For more information, see:

• Ensuring that users migrate applications with a pipeline by restricting the Import wizard
• Understanding model-driven DevOps with Deployment Manager

Define function input parameters on the Create or Save As forms

When creating or updating a Rule-Utility-Function ruleset in Designer Studio, use the Create or Save As forms to define or change parameters as a part of the form. The Parameters section on either of these forms allows you to set the function's name and Java type before opening the function.

Previously, you updated these fields on the Parameters tab for the function after the form was created. Moving these fields to the Create and Save As forms helps to proactively detect functions with the same signature in the same ruleset before saving the function.

For more information, see Defining function input parameters on the Create or Save As forms.

Search and Reporting does not index large items

When using the Search and Reporting (SRS) microservice in Pega Platform™ 8.5, you might encounter problems with indexing large out-of-the-box rules. The issue is not visible in Queue Processors, but you can access logs to verify which items the system does not index.

Ability to periodically defragment the PR_SYS_LOCKS table

Lock management in Pega 7 is controlled through the database table PR_SYS_LOCKS. Because of the high volume of entries inserted into and deleted from this table during case processing, the data in the PR_SYS_LOCKS table can become highly fragmented, causing degraded performance over time.

You can now periodically defragment this table. The following Dynamic System Settings control when and how often defragmentation takes place using DefragSysLocksDaemon:

• syslocks/defragIntervalType

  • ​Custom interval type to run defragmentation

  • Set this first – determines whether defragmentation occurs daily at a specified hour or at a recurring interval

• ​syslocks/defragHourOfDay
  • ​​Used to run defragmentation at a specified hour
  • Accepts only integer values in the range 0-23
  • Example: run defragmentation daily at 1 AM by entering a value of "1"

  • Can be ignored if syslocks/defragIntervalType indicates a a specified periodic interval

• syslocks/defragIntervalInHours
  • Used to run defragmentation at specified periodic intervals
  • Accepts only integer values > 0

  • Example: run defragmentation every four hours by entering a value of "4"

  • Can be ignored if syslocks/defragIntervalType indicates a specified hour

For more information, see PEGA0056 alert monitors PR_SYS_LOCKS defragmentation performance.