SR-119538 · Issue 177397
Detection added for custom work history tables
Resolved in Pega Version 7.1.7
In order to fully embrace mobile capabilities, columns were added to the work history tables to allow actions to be tracked as a geographical map where each history event is a numbered locale indicator on a map instead of a row of entries. From lat/long it is also possible to call a Google service and get the street address as well. However, this functionality caused some issues post-migration with if there were customized pc_history_work tables mapped to custom classes. To remedy this, a check has been added to only query for pxlatitude/pxlongitude if columns are exposed and shown, and that will detect if the columns aren't present.
SR-119869 · Issue 176176
Access Role Editor link errors fixed
Resolved in Pega Version 7.1.7
When using IE11 or Google Chrome, clicking on the hyperlink to a privilege associated with a class in Access Role Editor created issues that prevented changes from being made or saved. In some cases, after clicking 'Remove Checked' in the popup dialog, the developer portal loaded in the popup. This was caused by the forms-based role selection not being converted for cross-browser support, and has been fixed.
SR-117114 · Issue 171740
Added localization formatting for date values (YYYY-MM-DD)
Resolved in Pega Version 7.1.7
In Sweden, dates are given with a hyphen "-" and not slash "/" as the date separator as per ISO-8601. The SV localization has been changed to follow this style.
SR-118567 · Issue 167257
Enhanced task queue handling for custom applications
Resolved in Pega Version 7.1.7
In some situations, a custom agent would periodically fall over when processing a large backlog of queued items. This was caused by an exception thrown when placing a task in the queue when it is already present. The system has been updated to better handle this situation and allow agents to continue to execute with the present schedule when a duplicate task is found.
INC-137709 · Issue 584297
New security role added to restrict access to development-specific classes
Resolved in Pega Version 8.5.1
A new security role and related RAROs have been implemented to allow better security for end users on non-BAC systems. This restricts access to Rules and execution of activities on classes that are development-specific.
INC-128811 · Issue 587213
Operator created with save-as has correct application access
Resolved in Pega Version 8.5.1
Creating an operator using Save As retained access to the applications of the original operator even if they were removed in the creation process. This was due to the saveAs operation of the Operator not retaining consistency between the records in the ValueList pyAccessGroupsAdditional and the page list pyaccessgroups_opid. To resolve this, the PreSaveAs of the Operator ID has been updated to maintain consistency in the records.
INC-132517 · Issue 578985
Correct manager name retained for skill-based routing updates
Resolved in Pega Version 8.5.1
In App Studio, having a manager update a team member's skills changed that team member's reporting Manager name (.pyReportTo) upon save. This was a use case where multiple operator IDs were required for the same person (name and email), so that using the report definition parameter 'BestOperatorValue' for the pzUpdateOperatorInfo activity caused an incorrect manager name to be set to the team member's operator ID. This has been resolved.
INC-127392 · Issue 574286
Delegated Decision table rule grid loads in iFrame with SSO
Resolved in Pega Version 8.5.1
The delegated decision table rule grid and checkout options were not displayed when launched from iFrame using SSO sign in. Without SSO, the delegated decision table grids were loading properly for the same Access group. The heart of this issue was that decision tables were using an older style of Designer Studio javascript which was not designed to be embedded in an iFrame due to issues related to Cross-Origin Resource Sharing (CORS). In order to support the usecase of the Pega end user portal/application being integrated to an external domain application using an iFrame, enhancements have been made to the necessary delegated rule function definitions.
INC-135095 · Issue 581849
Tracer toolbar shows correctly in IE
Resolved in Pega Version 8.5.1
After upgrade, the developer toolbar for the tracer pop up was not visible in Internet Explorer. Investigation showed that Microsoft Internet Explorer was loading the correct elements, but they were not displaying due to recent updates made to prevent Cross-site scripting vulnerabilities for the tracer. This has been resolved.
INC-129275 · Issue 577016
Resolved errors when refreshing test case
Resolved in Pega Version 8.5.1
On refreshing any test case for decision tables, a "rule no longer exists" error appeared on screen and a pzRuleNotFound exception was generated for all testcases in tracer. This was traced to Rule-Utility-Function lookup parameter handling in the pzGetFreshLabelForRUT decision table: because the Rule-Utility-Function was not able to fetch the label and the caller step in an activity, it was ending with a fail status and generating the errors. This has been resolved by correcting the Rule-Utility-Function calls in the decision table pzGetFreshLabelForRUT to ensure it has the correct parameters.