INC-125803 · Issue 568661
Cross-site scripting updated on activities
Resolved in Pega Version 8.1.9
Additional Cross-site scripting work has been done on activities.
INC-127981 · Issue 563000
Rulesets removed from direct invocation ability
Resolved in Pega Version 8.1.9
Internal rules have been updated so that they are no longer available to be invoked directly by a client or service.
INC-146837 · Issue 602673
PerformCriteria contains CurUserHasRequiredSkills 'when' rule
Resolved in Pega Version 8.1.9
A customer version of the PerformCriteria data transform was generating a validation error due to a qualified statement that resulted in a null result. This has been resolved by updating the PerformCriteria DT to include the CurUserHasRequiredSkills 'when' rule.
SR-D65866 · Issue 536427
Corrected approval step task message
Resolved in Pega Version 8.1.9
When a case progressed to the approval step, the task name did not properly appear as part of the "Please approve or reject this" message. In another scenario, a portal which supported locale switching was not translating "Please approve or reject this" when the locale was switched, but instead displayed the message in the original language. Investigation traced this to the pzInstructionsForApproval data transform storing the localized field value, causing it to persist inappropriately. This has been resolved.
SR-A8387 · Issue 217780
Added prevention for inappropriate Google Chrome autofill
Resolved in Pega Version 7.2
When login userid and password were stored in the Google Chrome browse and autofill was enabled, Google Chrome was using those values to populate the RuleSet rule form's input field (hidden on UI on Versions tab) and password field (on the Security tab). Those invalid values caused a save failure. To fix the issue, the system will pre-populate the hidden input field so that Google Chrome does not auto fill this field on the client side.
SR-A3950 · Issue 209476
Corrected order of tabbing focus in Activity rules
Resolved in Pega Version 7.2
After opening an Activity rule, the Description text field did not receive focus at the expected point when tabbing through the steps. The activity steps have been rebuilt to correct the tabbing order.
SR-A5453 · Issue 215368
Fixed Edit in Excel with load balancing enabled
Resolved in Pega Version 7.2
Edit in Excel was not working for decision tables if a load balancing was enabled. This was traced to the load balancer port number being added to the RequestHomeURL, causing a malformed strURL for opening the decision table in Excel. A check has been added to evaluate whether the strURL starts with a proper protocol and host instead of checking for RequestHomeURL.
SR-133163 · Issue 203273
Refined property-set expansion to support complex activities
Resolved in Pega Version 7.2
Attempting to expand a property-set in an activity with many steps (20+) caused a failure and the activity locked up. Tin order to support complex activities, the activity call and clipboard functions in this call have been refined for efficiency.
SR-A5355 · Issue 215511
Resolved browser hang with large Map Values
Resolved in Pega Version 7.2
While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer , the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.
SR-A8561 · Issue 217554
Resolved browser hang with large Map Values
Resolved in Pega Version 7.2
While opening very large Map Value ruleforms, some systems were hanging and thread dumps were seen in the logs. With Microsoft Internet Explorer, the error was "There was an error while loading the content given. Microsoft Internet Explorer Error Description: Not enough storage is available to complete this operation." This was an issue with the display grid not being able to show huge number of records in the map value grid. To resolve it, the map value grid will be hidden if it exceeds the given cell threshold.