INC-192102 · Issue 678532
Performance improvements for stale thread warnings
Resolved in Pega Version 8.7
Stale thread warnings were causing performance issues during dataflow run execution. Stale thread/slow component warnings are added as part of the dataflow execution when a processing thread takes more than 5 minutes to process a single dataflow record. The stacktrace of the dataflow thread is added as part of the warning for debugging purposes, but in some scenarios the stacktrace can become very large. This has been resolved by removing the stacktraces from the warning, improving the query logic, and adding the run ID to the exception method to assist if there is an error.
INC-201366 · Issue 691508
Performance improvements for stale thread warnings
Resolved in Pega Version 8.7
Stale thread warnings were causing performance issues during dataflow run execution. Stale thread/slow component warnings are added as part of the dataflow execution when a processing thread takes more than 5 minutes to process a single dataflow record. The stacktrace of the dataflow thread is added as part of the warning for debugging purposes, but in some scenarios the stacktrace can become very large. This has been resolved by removing the stacktraces from the warning, improving the query logic, and adding the run ID to the exception method to assist if there is an error.
INC-194305 · Issue 681681
File Dataset wildcards updated for ADM storage
Resolved in Pega Version 8.7
Attempting to access the filepath was failing and an error was seen indicating "Could not obtain lock 'Create repository file pegacloudfilestorage:ADM/Rule-Decision-AdaptiveModel/Data-Decision-Request-Customer". While creating a file name, a lock is generated while checking the file names of existing files. If the file data set has a large number of files, a condition may occur where some threads are unable to save data and an exception is thrown. To resolve this, the wildcard previously used in the file name has been replaced with the Pega node id + thread id + current timestamp. This will ensure all wildcards are unique and there is no need to lock and list existing files.
SR-C41775 · Issue 380461
Autopopulate mapping corrected for property references created under previous system versions
Resolved in Pega Version 8.1
After upgrade, the pzAutoPopulate information was missing when opening a work object which contained a property which referred to a data page. This caused the data page load to fail because the parameter (which was actually present on the page) did not get passed. Investigation found a backward compatibility issue that caused the autopopulation to fail in the new version: reference links were not built with the right parameter values during blob serialization because parameter information was stored in pzAutoPopulateMap (new) instead of pzAutopopulatedKeys (old). This has been corrected so the properties will be mapped appropriately.
INC-174652 · Issue 654140
Case Archive updated to better prune email and attachment metadata
Resolved in Pega Version 8.7
After configuring pyPegaArchiver, pyPegaIndexer and pyPegaPurger to remove old cases, there were no records present in the pr_metadata table but the records related to Data-Corr-Email, Data-WorkAttach-File and Link-Attachment remained. As there is no harm in removing these entries because the system has already copied the reference to these attachments, the entry in pr_metadata can be removed without any issue. With this update, external and shared entries now get removed from pr_metadata table when a purge is performed, however they do not get removed from the target table.
INC-135405 · Issue 582004
Simple button style updated to allow customization
Resolved in Pega Version 8.5.2
The Simple button style was not picking up the correct border style that was defined in the Skin rule when in the hover state. This was traced to the border radius value hard-coded in one of the custom files taking precedence over the value added for the border radius in the skin format. To resolve this, the simple button styles code has been removed from the controls.css file that had the border radius value hardcoded. The styles for simple button format will be configured in the skin, and a mixin has been added for modal buttons border styles that can be configured in the skin itself.
INC-145535 · Issue 600785
Corrected layout group overlapping content
Resolved in Pega Version 8.5.2
When an editable Table with Master Detail Edit has a section that contains a Layout group (Tab) inside the Master Detail Flow Action, if there are more layout group headings than that can be contained in the screen, a left and right arrow are displayed to toggle between headings in the layout group heading bar. However, timing issues sometimes caused the contents of the layout group to overlap on top of the content below the layout group and the screen was freezing with a loading icon. This was traced to console errors, and has been resolved by adding an 'undefined' check to prevent those errors.
SR-C32155 · Issue 374359
Null check added for empty clipboard page in GetPopOverData
Resolved in Pega Version 8.1
When first launching a screen which contains a repeat grid, the table definition contains a prim_page value like "TempSelectedCustomer". Clicking the filter icon on any column of the repeat grid then caused the pzGetPopOverData activity to be fired from the UI with the parameter preActivityPage and value "TempSelectedCustomer", but there was no such page in the Clipboard and an exception was generated. If the browser was refreshed and the same scenario run again, pzGetPopOverData activity was fired from the UI without the parameter preActivityPage and no issue was seen. To resolve the error on the first pass, a null check has been added to the pzGetPopOverData activity first step.
SR-C32295 · Issue 372890
Emails sent from Service Request template created correctly
Resolved in Pega Version 8.1
When an application was created from the 'Service Request' template via Pega Express, emails sent had a blank body. This did not happen with applications built from the Custom template. This was traced to the Send Email smart shape internally calling pzSendEmail which then calls SendSimpleEmail activity. This activity was available both in Work- and PegaSample, and as this case type class was inherited from PegaSample, it picked SendSimpleEmail from the PegaSample class and resulted in a dummy implementation. To fix this, SendSimpleEmail has been withdrawn from the PegaSample class so that same rule from Work- will be picked.
INC-173436 · Issue 648821
Performance improvement for Application Save: Node Level Data Pages
Resolved in Pega Version 8.7
As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.