INC-143193 · Issue 595938
Handling added for UI overlap issue
Resolved in Pega Version 8.4.4
Elements of the window "Test Case Record Configuration" were shifted into one another when the Application name was too long that it overlapped with the other UI Elements. This has been resolved by adding a style sheet with overflow hidden.
SR-A69787 · Issue 253568
DSS added to allow validation to be disabled if Edit-input is configured
Resolved in Pega Version 7.2.2
Japan has a special date format based upon the year of accession of the emperor. An Edit Input rule that converts that format into standard Gregorian format and applied it to a date property worked as expected, but when the initial client validation fired and generated an error on the text field, the Edit input also fired and converted the text as per the required format. At this point the refresh condition occurred, which again resulted in firing the client validation and removing the error. In order to prevent client validation when an Edit Input is likely to alter the contents, a Dynamic System Setting has been added. Based on the value of this DSS, validation can be disabled for all the fields where Edit-input is configured.
SR-A24901 · Issue 266257
Restored nested sections visible in Designer Studio
Resolved in Pega Version 7.2.2
When trying to restore a earlier check-in version inside a nested layout, the restored section was corrupted i.e., the elements inside the dynamic layout (repeating grid) were not visible in the Designer Studio even though they did display as expected at runtime. Analysis showed that when a rule was deleted from a section with nested layouts, only the properties which had values were committed to the database. On restoring the rule, only committed properties were re-created on the section XML, leaving the XML incomplete and generating an error and layout rendering failure. To fix this, the pzpega_ud_gridlayout_structure JS has been updated to handle the non-existence of empty nodes and initialize them.
SR-A90755 · Issue 263310
Restored nested sections visible in Designer Studio
Resolved in Pega Version 7.2.2
When trying to restore a earlier check-in version inside a nested layout, the restored section was corrupted i.e., the elements inside the dynamic layout (repeating grid) were not visible in the Designer Studio even though they did display as expected at runtime. Analysis showed that when a rule was deleted from a section with nested layouts, only the properties which had values were committed to the database. On restoring the rule, only committed properties were re-created on the section XML, leaving the XML incomplete and generating an error and layout rendering failure. To fix this, the pzpega_ud_gridlayout_structure JS has been updated to handle the non-existence of empty nodes and initialize them.
SR-A19246 · Issue 254062
Customized ordering ability for delegated rules added
Resolved in Pega Version 7.2.2
Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.
SR-A19246 · Issue 254058
Customized ordering ability for delegated rules added
Resolved in Pega Version 7.2.2
Previously, the order that delegated rules were displayed in was always the reverse of the order they were added to the System-User-MyRules form, showing the most recently delegated items at the top regardless of the order they have on that page. An enhancement has now been added to allow customization of the order through a provided extension point using 'post load processing' of the data page D_pzFilteredDelegation.
INC-138253 · Issue 597572
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.5.2
As part of property optimization, After exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.
INC-138253 · Issue 597569
Handling added to ensure proper Data-Admin-DB-Table name records
Resolved in Pega Version 8.4.4
As part of property optimization, After exposing the property "SolutionName" using the wizard, the value was not visible in a new column for existing records after the completion of the column population job. This was traced to an issue with DBSchemaDDLExecutor expecting lowercase Data-Admin-DB-Table names, and the wizard has been updated to ensure Data-Admin-DB-Table name records are all lowercase.
INC-150704 · Issue 613439
Azure Repository connection updated
Resolved in Pega Version 8.4.4
Attempting to connect to Azure blob storage using SDK v8.6.4. SDK was not working. Investigation showed that the x-ms-version:2013-08-15 was set by default; the issue has been resolved by setting the x-ms-version to 2018-03-28, and Pega will be working with Microsoft support to understand what has changed at the Azure Storage end that introduced the issue.
SR-A76647 · Issue 253238
Resolved ConcurrentModificationException in mContent iteration
Resolved in Pega Version 7.2.2
When adding or removing the items from a repeat grid and submitting the modal dialog, an intermittent ConcurrentModificationException was coming from the API ClipboardPageImpl.clearMessages(). This was traced to the function iterating over mContent and has been fixed by making a copy of mContent and iterating over that.