New alert for job scheduler activity that exceeds a time threshold
Valid from Pega Version 8.6
Pega Platform™ now saves the PEGA0130 alert in the performance alert log at the time that a scheduled job exceeds the configured threshold value. To identify performance issues with long-running processes, you can monitor the log for the alert while the job scheduler runs.
The alert is enabled by default. You can change the default threshold value or disable the alert in dynamic system settings.
For more information, see PEGA0130 alert: Current Job Scheduler run is taking too long.
Improved indexing performance by gradual retrieval of data
Valid from Pega Version 8.4
Search functionality in Pega Platform™ versions from 8.4.5 to 8.6 now includes the option to improve indexing performance when reading query results from a large table in a database. For example, to load the recommended 50 records at a time, in the Pega-SearchEngine ruleset, create the indexing/distributed/fetchsize dynamic system setting, and set the value to 50.
Creating the fetchsize dynamic system setting ensures that your system does not crash while indexing classes with numerous instances.
For more information, see Creating a dynamic system setting.
Data model inheritance does not depend on ruleset context
Valid from Pega Version 8.6
Search and Reporting Service (SRS) in Pega Platform™ 8.6 now provides an improved method of synchronizing data model by distinct users. In applications built on earlier versions of Pega Platform, some users might encounter difficulties in indexing data. Now, the data model that the system sends to SRS does not depend on access privileges. With this enhancement, each user of your application is eligible to synchronize data.