SR-A96096 · Issue 264802
Tenant hash preserved for SOAP to accommodate load balancer SSL termination
Resolved in Pega Version 7.2.2
With Cloud 2.1, there was a need to set prconfig settings in order to accommodate SSL termination at the load balancer side, but the SOAP messages between a client (tenant) and PDC were having their tenant hash stripped by the engine. This was due to SOAP requests made to a specific Tenant by a monitored node (client) of PDC(MT) being redirected to a Shared tenant in PDC. To resolve this, even when "initialization/contextrewriteenabled" is set to true, the value for "pxReqPathInfo" will be set by HttpRequestMapper.buildRequestorDataFromHttpRequest() in the Map returned by it.
SR-A87407 · Issue 265098
XML stream assembly handles parentheses
Resolved in Pega Version 7.2.2
XML stream assembly was not properly handling parentheses; this has been fixed.
SR-A99962 · Issue 266646
Wait enhanced to maintain case status for multiple children
Resolved in Pega Version 7.2.2
A Parent case that was configured to resume when the sub-case reached a particular status using "Pending-ParentCaseResume" was not working as expected if there were multiple child cases for a single parent. This was due to the Wait shape taking the current status of the activator (first child case resolved) instead of the dependency status for which the wait shape should be looking for (subsequent child case), and has been fixed by establishing a new property on the Activator page to hold the dependency status and rely on this while checking if the activator has crossed the desired status.
SR-A100503 · Issue 268474
Harness name field in flow accepts expression
Resolved in Pega Version 7.2.2
After upgrade, a harness issue was encountered where the generated flow was treating the pxFormName as String literal instead of Expression. This caused an error when trying to save a flow. To correct this, FlowFUA PopulateFlowActions function code used for Expression parsing in the harness has been updated.
SR-B1873 · Issue 271608
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-B238 · Issue 271610
Fork shape works with both when and percentage connectors
Resolved in Pega Version 7.2.2
An error was generated when trying to save a flow rule that contained both percentage connectors and When rules fork shapes. This was due to the 'ValidateModelProcess' activity getting all connectors in the flow and checking if there is at least one connector with Percentage, then iterating each decision shape by iterating the connectors and checking for percentage error scenarios. To fix this issue, the system will get the connectors from the decision shape in context and check if at least there is one percentage connector, then check for validation after that.
SR-B599 · Issue 270485
Flow Dependency queries performance improvements
Resolved in Pega Version 7.2.2
Case dependency queries executed by PEGA have been tuned to improve system performance when mid flow dependencies are getting fulfilled.
SR-A100811 · Issue 271627
Breadcrumbs display consistently
Resolved in Pega Version 7.2.2
Case stage breadcrumbs intermittently did not display when a work item was opened. This has been corrected by updating pxDisplayStages(Pega-EndUserUI rule set) to change from grid source to data page source and pass the the pzInsKey parameter.
SR-A93826 · Issue 264612
Corrected Field level audit issue
Resolved in Pega Version 7.2.2
Field level auditing was creating two extra "TrackSecurityChange_Change" entries when a new item was added to a Page List at the same time an existing item was removed. It was also updating audit incorrectly the item value was changed for one row at the same time another row was added. This has been fixed by modifying the Memo audit functions to update the values correctly on save when an entry or row is added/edited and other is removed.
SR-A102249 · Issue 270854
Lock warning correctly cleared after WO transfer
Resolved in Pega Version 7.2.2
If a work object opened by another user was transferred into a new workbasket, the expected lock warning showed up but refreshing the work object list caused a harness error. This was traced to incorrect clearing of the error message from the primary parameter page, and has been fixed.