SR-A100724 · Issue 268499
Resolved cascading error messages in case work user portal
Resolved in Pega Version 7.2.2
Whenever there were error messages seen on the UI of the case work user portal, taking any action on that screen (e.g. delete /save/submit) caused the number of error messages to increase every time. This was caused by a harness issue relating to isAncestor, and has been fixed.
SR-A76831 · Issue 255486
Grid headers show "Required" when PegaWAI enabled
Resolved in Pega Version 7.2.2
With PegaWAI enabled, grid headers marked as required were displaying the noncompliant '*' label instead of the accessibility-enabled 'required' label. This was due to missing styles for table headers and has been corrected.
SR-B6425 · Issue 270890
Scrum Board chicklet error resolved
Resolved in Pega Version 7.2.2
After collapsing and expanding a user story chicklet in the Scrum Board, adding a new note to the user story would cause the user story chicklet to disappear. This was a rendering issue due to an error in the type property syncing with the level property, and has been fixed.
SR-A15627 · Issue 232738
JBoss shutdown errors resolved
Resolved in Pega Version 7.2.2
During a controlled shutdown, database-level exceptions occurred and a hard reset was required. This was traced to the container not correctly detecting dependencies, leading to JBoss prematurely terminating JMS and JDBC resources that were needed during Pega shutdown. Pega applications on JBoss now contain information to ensure the application server understands that this resource has dependent processes and the lookup-name (with the JBoss specific namespace) is maintained correctly to make sure it isn't cleaned up prematurely. The web.xml file has also been updated to include a lookup-name in the entry for ResourceRef_1 to handle cases where the datasources are injected using CLI scripts after JBoss is started and before Pega is deployed.
SR-A97991 · Issue 263957
Index reference synchronizer upgraded to capture previously shipped rulesets during upgrade
Resolved in Pega Version 7.2.2
During upgrade, some sites were seeing an SQLIntegrityConstraintViolationException error. This was caused by the presence of rulesets (e.g. PegaUVU, PredictiveAnalytics-UI) that were once shipped but are no longer, but that have rules that are still shipped. To correct this problem, the index reference synchronizer has been upgraded to capture those previously shipped rulesets.
SR-A98390 · Issue 252437
Scheduled report cleanup error resolved
Resolved in Pega Version 7.2.2
Exceptions were thrown in the logs by the scheduled reports task when trying to clean up the previous day's generated attachment reports. This was due to the name exceeding the length restriction on the property (60 characters) and failing validation, and has been fixed by truncating the field.
SR-A87928 · Issue 255259
Fixed cataloging for v5 hotfixes
Resolved in Pega Version 7.2.2
Recent modifications to obtaining catalogs for supporting additional products (i.e. frameworks) caused a regression in being able to check dependency information on v5 hotfixes, preventing DL files from being created for them. This has been fixed.
INC-144555 · Issue 603069
Changelog cleanup added for de-optimized properties
Resolved in Pega Version 8.5.3
Unwanted optimization was automatically added to properties for the Application-Work-Casetype class created using the wizard in the App Studio. Attempts to remove the optimization did not work: the property advance tab was showing the optimized classes details even after deleting and recreating the property. When a property is optimized the system adds entries to pr_changelog for the list of classes it has optimized. When the property was deleted, the pr_changelog was not cleared. This was a missed usecase, and has been resolved by overriding the Cleanup activity at Rule-Obj-Property class to delete the pr_changelog entry associated with that if it is present.
INC-153138 · Issue 625569
Database primary keys generated as NONCLUSTERED for imports
Resolved in Pega Version 8.5.3
When a primary key was defined for a table and the table was exported and then imported, the primary key was generated as CLUSTERED. This resulted in an MS SQL Cluster Index violation because all Pega-shipped tables generated during installs/upgrades have a PK constraint index with NONCLUSTERED index type as it allows for a longer key. This was a missed use case, and has been resolved by updating the system such that when importing with MS SQL database, the primary key index is made NONCLUSTERED all the time so it will be consistent with the base platform.
INC-154042 · Issue 621260
Pega Catalog custom upload control modified
Resolved in Pega Version 8.5.3
Attempting to upload a catalog.zip file caused the system to hang and thread dumps were seen in the logs. Investigation traced the issue to the custom control used to upload the catalog, which was posting the entire content in form data rather than sending a multi-part request. The control contained both legacy code which used form.submit() and encoding along with new code that used SafeURL and sent an async request. With this, encoding could not be set to multi-part in case of an AJAX request. To resolve this, the catalog upload control has been modified to use the appropriate legacy code that performs form.submit() and sets the encoding properly.