SR-A80436 · Issue 278967
Federated Case Management GetNextWork function resolved
Resolved in Pega Version 7.3
When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.
SR-A80436 · Issue 279629
Federated Case Management GetNextWork function resolved
Resolved in Pega Version 7.3
When an operator had Work Basket configured with Federated Case Management, the Get Next Work function generated an error. This was due to the GNW settings from the operator IDs of the 'remote' systems not being correctly respected, and has been resolved.
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.
SR-B13040 · Issue 293526
Null DPI check added for async page load
Resolved in Pega Version 7.3
A null pointer exception was being generated when a data page was being loaded from the asynchronous cache and some exception occurred while switching the access group or getting a definition. To avoid this, a check has been added for a null DPI.
SR-B13450 · Issue 284622
Null check added to joins of UserWorkList columns
Resolved in Pega Version 7.3
When attempting to join a pyUserWorkList Report definition with work class properties, blank values in the pyUserWorkList columns caused a Null Pointer exception on click of the filter icon for joined class properties/columns. This has been resolved by adding a null check.
SR-B34642 · Issue 298361
Fixed Guided Tours for IE
Resolved in Pega Version 7.3
"Guided Tour" in Internet Explorer was only running one page per an operator session, then logging a "Permission denied" error in the JS console for other times when it did not run. This was due to an exception while launching findAndClosePopOver and has been fixed.
SR-B35405 · Issue 292363
AddressMap properly rendered
Resolved in Pega Version 7.3
Using pxAddressMap control showed longitude and latitude values on the review harness and did not render the MAP until refreshed. This was due to the Address map being generated with one more 'if' condition around the editable condition. If this condition is present for the address map it may be marked as Editable control while its behavior is Action, causing the rendering issue. This has been fixed.
SR-B6575 · Issue 277285
Filter popup made more efficient for large number of parameters
Resolved in Pega Version 7.3
The filter pop-up was not fully loading when the grid source has a very large number of parameters. To resolve this, the request fired in the popover initiation has been changed to pass the paramList in postData and decode it while setting params in step 2 of pzGetPopOverData.