SR-D85111 · Issue 549198
Paging method updated for Select All in Broken Queue
Resolved in Pega Version 8.4.2
After clicking the 'Select All' box in Broken Queue In Admin Studio, scrolling up and down rapidly caused the checkboxes to be unselected. This was traced to the use of progressing paging in this scenario, and has been resolved by removing progressive paging and replacing it with the out of the box '1 of X' paging method.
SR-D90520 · Issue 552019
REST parameters updated for SauceLabs compatibility
Resolved in Pega Version 8.4.2
After configuring a call to SauceLabs testing through Deployment manager, the REST call was timing out. Investigation traced the issue to SauceLabs changing its parameter name from "browser" to "browsername", and the Pega parameter names have now been updated to reflect that change.
SR-D93181 · Issue 555469
Pega Org Structure Tools added
Resolved in Pega Version 8.4.2
An enhancement has been made available on Pega Marketplace to simplify working with large organizational structures with additional support for having more than 3,333 organizations. This allows choosing an Org, Div and Unit in the Operator ID and Application ruleforms using auto-completes rather than a tree, and can now handle up to 10,000 Organizations, 10,000 Divisions per organization, and 10,000 Units per Division. Installations exceeding those numbers will still be able to enter the name without validation problems, and a link to the Organization Chart landing page will be available for browsing that data in a tree.
SR-D95797 · Issue 556765
Branch Preference now considered for TestCase rule
Resolved in Pega Version 8.4.2
Setting branch preference from top right worked for all rule types and new rule dialog rightly set the branch, but when attempting to use this configuration for a test case, it only displayed the first branch in the app and did not follow the branch preference. This was due to the system using a separate save modal dialog for test case creation which did not consider this use, and has been resolved by implementing the branch preferences use case to show the direct preferred branch if present.
SR-D37415 · Issue 508969
Parameter page update added to improve backwards compatibility for ShowTestLibraryTab
Resolved in Pega Version 8.1.7
An error was observed on the first attempt to modify the 'when' rule "ShowTestLibraryTab" located in PegaProjectMgmt:08-01-01. Analysis showed the when rule (Always, Never) which was called from this rule was not found, which was an issue traced to the Rule-Obj-When function alias parameter name being changed from "strWhen" to "blockName" in the 8.1 release. Subsequent attempts to save the modified rule succeeded due to step#7 in the Embed-UserFunction.pzPopulateDropdownFBUIParameters activity upgrading the pyParameters page with the latest data. To resolve this backwards compatibility issue, the activity step#6 has been modified to upgrade the parameter name for the Rule-Obj-When function alias.
SR-D35734 · Issue 504477
Escalation updated to ensure assignee is notified of missed deadline
Resolved in Pega Version 8.1.7
The Passed Deadline SLA Actions to send email to the owner were not triggered as configured in SLA rule form. To correct that, pzMapEasyEscalationParams steps 3.4.10 and 3.4.11 have been modified to support "NotifyAssignee" for the passed deadline.
SR-D39547 · Issue 505859
Check added for backwards compatibility with Case Type when rules
Resolved in Pega Version 8.1.7
After upgrade, the When rules present on case type rules (used for skipping stages or showing/hiding stage-wide or case-wide actions) were not executing at run time. This was traced to the introduction of the pySkipOrAllowType property in recent versions, and was only reproducible when the ApplicationRuleset was locked and after upgrade irrespective of whether the condition for when was true or false. To resolve this and enhance backwards capability, a check has been added for the SkipOrAllowType property being empty.
SR-D42566 · Issue 512874
Security improvements for ApplicationInventory and Delete Class
Resolved in Pega Version 8.1.7
It was possible to call the activity "ApplicationInventory of class Rule-" by appending the activity name in the URL. To improve security, the ApplicationInventory activity and HTML rule have been removed from the system. In addition, it was possible to access the "delete class" screen and perform actions on top of it by directly appending the stream to the URL. This has been refactored so the screen will be presented only if the pzSystemOperationsAdministrator privilege is in the current access group.