INC-178070 · Issue 658677
Browser invocation allowed for UnlockOperator
Resolved in Pega Version 8.5.5
Attempting to unlock an operator who was locked out due to security policies was failing. This was an unintended side effect of security work performed earlier, and has been resolved by reenabling 'Allow invocation from browser ' for pzUnlockOperator. This activity requires an authentication check with privilege protection.
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-194330 · Issue 708711
Added special character handling for DecisionTable column-label
Resolved in Pega Version 8.7.2
The label of a decision-table column was being appended to the original decision-table return-value. The column label and comparator were handled differently for columns containing special characters (+, -, *,...), causing the data after the special character to be trimmed and appended to the row output value. This has been resolved by adding handling for special characters so the output and the label are rendered properly.
INC-200802 · Issue 714845
Line break handling added for setting required question asterisk
Resolved in Pega Version 8.7.2
If a survey question was formed in multiple sentences, the asterisk marking it as required was not displayed in screen. The asterisk displayed as expected if the question was one sentence. This has been resolved by updating the setMandatoryIconforQP script handle linebreaks and set the required symbol as expected.
INC-205666 · Issue 702936
Database table correctly prevents deletion if there are descendant classes
Resolved in Pega Version 8.7.2
When deleting a concrete class with descendant classes via an activity (Rule-.Delete), the Rule-Obj-Class.ValidateDeleteInternal activity was throwing an error message indicating the class could not be deleted due to descendant classes. However, the corresponding database table rule was deleted anyway. Investigation showed this was caused by ValidateDeleteInternal not reaching the Obj-Save-Cancel step. This can be fixed by modifying step 11, the post when conditions, to jump to END and set the END label at the Obj-Save-Cancel step instead Exit-Activity, but this issues has been resolved by updating all failure states to run end step. In addition, security has been updated to disallow "Allow invocation from browser".
INC-209426 · Issue 706804
GetFunctionsForLibrary retrieves 10,000 rows
Resolved in Pega Version 8.7.2
Some functions were missing from the expression builder browser and search results when pyShowInternalLibrary was set to true for including internal functions in the results. To resolve this, the default value for "Maximum number of rows to retrieve" in pzGetFunctionsForLibrary has been increased to 10,000.