Published Release Notes

New dynamic setting to manage validation of hidden fields

Pega Platform™ version 8.6.4 introduces a new DSS setting for Theme Cosmos and other section-based applications. The validateHiddenField setting controls whether the application validates fields that you hide through visibility rules. By default, validateHiddenField is set to true, which means that the application fields are validated for completeness even if they are not displayed in the form. You can also switch off this functionality by changing the setting value to false. 

For more information, see Managing field validation in hidden sections.

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.

Enhanced refresh token strategy

You now have more precise control over your refresh token expiration strategy. When a refresh token is enabled, you can choose to set its initial expiration based on the value provided by the IDP. The refresh token expiry can be derived from IDP’s session timeout when SSO is used with external IDP for user authentication in the authorization code grant flow. You can also specify a separate refresh token expiration strategy based on your use-case. 

These can be configured in the OAuth2 Client registration rule form.

For more information, see Enhanced refresh token strategy.