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-A103203 · Issue 276928
SQL alias function getLastDayofYear repaired
Resolved in Pega Version 7.3
After upgrade, the SQL alias function getLastDayofYear generated an error. This was due to missing format conversion for the date value parameter, and has been corrected.
SR-A86522 · Issue 272062
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.
SR-A86522 · Issue 272065
Event Late triggers expanded
Resolved in Pega Version 7.3
If "Limit passed deadline events" was not set to any value and the enqueue item was still in defer-save and not committed to DB, 'Event Late' was not triggered. Code has been added to properly check and trigger the late notice based on this scenario.
SR-A91979 · Issue 261380
referencePropertyLink will be directly copied if autopopulate disabled
Resolved in Pega Version 7.3
A run-time failure occurred due to a reference to an AP property failing to copy properly during objOpenByHandle. This was because autopopulation is disabled in objOpenByHandle, causing the source property to be returned as null when page-copy lost the reference information. To resolve this, when autopopulation is disabled the referencePropertyLink will be directly copied from the source page to the target page without trying to resolve the reference property's source.
SR-B10051 · Issue 279714
Agent management detail corrected to show all nodes
Resolved in Pega Version 7.3
Drilling down to the agent detail from the Agent management page was showing only the current node when agents from the other nodes should have been displayed as well. This was caused by an error in the DataAgentIndex function, and has been corrected.
SR-B10051 · Issue 279523
Agent Management updated for long NodeNames
Resolved in Pega Version 7.3
Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.
SR-B10051 · Issue 279523
Agent Management updated for long NodeNames
Resolved in Pega Version 7.3
Drill down to the agent detail from the Agent management page was only showing the current node. This was traced to a failed join when a very long "pyNodeName" DB line was encountered in pr_index_data_agents, and has been fixed.