INC-192159 · Issue 691022
Handling added for designtime page used in runtime
Resolved in Pega Version 8.7
After creating a survey with branch Create survey cases routed to different actors, some cases missed the assignments and were left idle with no access to progress. Survey cases (with branches) having the 'when' conditions in flow connectors experienced this intermittently in production. This was traced to the use of D_pzSurveyPage data page called from the ProcessUpdate data transform while creating the survey: this data page is for design time and should not be used at runtime as it requires design time pages like CaseTypePage which will not be available at runtime. To resolve this issue for runtime, in Step 3 of pzGetAllConnectors, pyClassName will be copied from the step page and set for pzGetConnectorsForDecision.
SR-A89074 · Issue 258503
Resolved upgrade issues with ConnectSOAP using MTOM
Resolved in Pega Version 7.2.2
After upgrading, Connect SOAP request messages were failing on the back end server with the error "xop 3.2.2.a: xop:Include must be the sole child of element" . Analysis showed the base64binary was not being substituted correctly with the expected "XOP Include" element. Axis uses Axiom to write Multipart messages and multiple XOP writers are involved in writing and encoding the message. When the writer stream is flushed , it depends on SimpleNsStreamWriter to write the bytes. SimpleNsStreamWriter is currently packaged as part of WStx-2.3-asl.jar and webservices-rt.jar, but this was not true in previous versions. As a result after upgrade, Webservices-rt classes is taking precedence over wstx-asl classes, which was generating the XOP:include elements with inline content. For better backwards compatibility, the WS-TX jar references have been removed from the webservices-rt.jar so that now it will rely on wstx-asl-3.2.3.jar which is already shipped with the product.
SR-A24719 · Issue 252331
Correct Bulk processing status when no transfer occurs
Resolved in Pega Version 7.2.2
Searching by Work bulk processing was not transferring items when there were multiple assignments yet was showing a Transferred status and not displaying an error. This was traced to a missing 'when' condition check in the handling, and has been fixed.
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-A93295 · Issue 260100
Page-Copy given 'when' rule for assembler switch
Resolved in Pega Version 7.2.2
Performance issues relating to XML stream assembly were identified as an assembler switch problem in the Page-Copy Activity Method step. To improve response, a 'when' rule has been instituted to control switching between the old assembly Action aspect or the Model aspect in a scoped way, but can be overridden in the parse XML rule applies-to class.
SR-A24793 · Issue 252731
Expandable When parameter handling updated for repeating layouts
Resolved in Pega Version 7.2.2
In a dynamic layout, the "Expandable When" parameter was checking the first of the several "pxResults" pages but was not checking that condition for all the pxresults (pages). This was due to a situation where once the when condition evaluated to true, all the results below the when condition were not checked. The expanded parameter handling has been updated to correct this.
SR-A76831 · Issue 255486
Grid headers show "Required" when PegaWAI enabled
Resolved in Pega Version 7.2.2
With PegaWAI enabled, grid headers marked as required were displaying the noncompliant '*' label instead of the accessibility-enabled 'required' label. This was due to missing styles for table headers and has been corrected.
SR-B82049 · Issue 341054
pxCoverInsKey set in audit history when childcase created
Resolved in Pega Version 7.4
On adding an audit note during the creation of the child case, the audit history did not contain the reference to the parent case. Eventually, when the case was referenced, the pxCoverInsKey was populated in the history table. This was caused by an ordering error in the logic and the system has been updated to correct it.
SR-B65131 · Issue 330322
Fixed 'when' rules for showing privileged escalation buttons
Resolved in Pega Version 7.4
Privileged escalation was displayed for a user with access to manager reports due to missing 'when' rules for hiding the Add report/Add category buttons. This has been fixed.