INC-179111 · Issue 659476
Toolbar delete handling modified
Resolved in Pega Version 8.5.5
After upgrade from Pega 7.4 to 8.5, the toolbar delete button behavior was different. Previously, the pzRuleFormToolbarDeleteRule section rule invoked RuleFormMain on refresh, but the updated version was calling RuleFormHeader, preventing the deletion of the assignment from the class instance. This was an unanticipated edge case and has been resolved by updating the action in the button to refresh the section RuleformMain instead of header.
INC-180468 · Issue 659924
JAWS correctly reads work group header
Resolved in Pega Version 8.5.5
While creating the groups within the organizational unit, JAWS was reading the name of the frame as "Process Work Area" instead of "Create Work Group" and "enter data" instead of the name of the edit field with edit instructions. This has been resolved by adding a property to the short description label so it contains the instance type that is being created.
INC-180603 · Issue 661741
Added protections for GetSiblings
Resolved in Pega Version 8.5.5
Cross-site scripting protections have been updated for the GetSibling activity.
INC-181091 · Issue 662779
Strategy rules open from proposition filter after update
Resolved in Pega Version 8.5.5
After update, strategy rules could not be opened from the proposition filter. This was caused by the pxInsName property being populated only when a strategy rule gets selected/configured from the CB gadget. For upgrade scenarios where the condition is already configured with a strategy rule, the pxInsName property will be missing. To handle this upgrade use case, the "Rule-open-by-keys" action will be used instead of "Rule-open-by-name", as rule keys are always present while pxInsName gets populated for only new configurations.
INC-182150 · Issue 669851
DSS added to control Pega Version Banner
Resolved in Pega Version 8.5.5
Nuisance errors were being logged related to the application trying to connect to Pega to confirm available versions. This has been resolved by adding the 'when' rule pyShowVersionBanner to pzStudioHomeWrapper which allows disabling/enabling the Version Banner based on the setting used in the DSS ShowVersionBanner. pyShowVersionBanner defaults to true when DSS ShowVersionBanner does not exist.
INC-160190 · Issue 658124
Logic updated to allow page property and declare index with the same name
Resolved in Pega Version 8.5.5
A Property which was in a page list which in turn was embedded in a Page was not visible in the Report Browser. This was traced to the two properties sharing the same name, and was caused by a check which ensured only entries with unique names were added. In order to support this configuration, logic has been added to pzAddPropListForClass_TreeGrid such that if a page property and declare index share the same name, they are both added to the tree grid.
INC-166120 · Issue 657054
Parameter added to prevent name localization in Dev Studio Reports
Resolved in Pega Version 8.5.5
Running the DataTableEditorReport against a customer table translated names that matched localized values, such as "Mr. Block" became "Mr. Sperren" when the locale was set to de_DE even though the property was marked as "Do not localize" in UI Controls in the report definition filter. To resolve this, the parameter 'pyskiplocalization' has been added for use in the RRFilters_logic and while displaying the select Values popup.
INC-174756 · Issue 650538
Queue processor correctly moves items to Broken Items
Resolved in Pega Version 8.5.5
When an exception occurred while Queue Processor processed an item, he queue item was not moved to Broken Items. The error " inconsistent datatypes: expected - got CLOB DatabaseException caused by prior exception" was generated. This has been resolved by modifying the NativeSQL builder and NativeSQLBatchExecutor to allow the batch of queries to be retried. Additional changes were also added for Oracle databases to identify the correct column types.
INC-175622 · Issue 652277
Screen reader announces report names
Resolved in Pega Version 8.5.5
An update has been made to pyReportBrowserItem to ensure names of the reports on the report browser are read correctly.
INC-175797 · Issue 662049
Date/time filter works in source column
Resolved in Pega Version 8.5.5
The date/time filter was not working in the Source column for a report definition. This was traced to "pxCreateDateTime" resolving and storing the pyDataType in the report as "DATE TIME". While "DATE TIME" is an acceptable data type it was not supported by pzGridSortPaginate and thus the filter did not work. This was a missed use case, and has been resolved by updating pzGridSortPaginate to check the dataType as both "datetime" and "date time".