INC-184271 · Issue 668412
Portal Header persists appropriately
Resolved in Pega Version 8.6.2
The Portal header was disappearing immediately after case attachments were opened from the right sidebar and did not reappear even after refresh. This was traced to the absence of pd(event), and has been resolved by adding pd(event) to the onclick attribute in the anchor tag in the attachment UIKit rules.
INC-184300 · Issue 666156
Deprecated status removed from StartCaseType
Resolved in Pega Version 8.6.2
After updating from Pega v8.4 to v8.6, guardrail warnings were seen for the deprecated pxStartCaseType flow rule. This occurred for old case types created prior to v8.5. A utility has already been provided to upgrade the case type to include create stage, but this warning has been resolved by removing the deprecated status on pxStartCaseType to allow processes to proceed without a guardrail warning.
INC-186654 · Issue 669114
GetStatusChanges performance improvements
Resolved in Pega Version 8.6.2
Performance issues were seen when running the GetStatusChanges report. This was traced to the filtering methods used, and has been resolved by updating the report definition and enhancing the filtering conditions.
SR-A4171 · Issue 213701
Added keyword support for <current>
Resolved in Pega Version 7.2
Variations between system versions were causing a decision table containing some regexp functions to pass or fail validation depending on the version. To remedy this, support has been added for using the regular expression function as a keyword to ensure valid tables are properly handled.
SR-A5565 · Issue 217722
Added missing filename encoding for drag and drop
Resolved in Pega Version 7.2
An error was being generated when opening an attached file with "$" in the filename. This was due to missing encoding for cases attached with drag and drop, and has been corrected.
SR-130442 · Issue 212468
Added support for localization of the 'Advanced' value of the When rule
Resolved in Pega Version 7.2
If the "Advanced" value was localized in the When rule form, it failed as it was trying to compare with localized text. To resolve this, WhenTabListener has been modified to use the ID attribute instead of text for comparison.
SR-A6520 · Issue 216004
Case Worker Portal harness error resolved
Resolved in Pega Version 7.2
When using the Case Worker Portal with the UI-Kit:03-01-01 ruleset, the first search for work returned the expected results, but opening a work object and then searching again caused the same (now incorrect) results to be returned. This was traced to a harness call and storage issue, and has been resolved.
SR-A7369 · Issue 217460
Clarified evaluation order for conditional Local Actions in GetNextWork
Resolved in Pega Version 7.2
If Local Actions were configured with 'when' rules on the stages tab of a case type rule, the 'when' rules were being evaluated before assignment via GetNextWork and the wrong local actions were presented. In order to ensure flow actions are evaluated in the proper order, GetNextWork will populate a flow action before moving it to the worklist.
SR-A8396 · Issue 210609
Corrected duplicate work object IDs
Resolved in Pega Version 7.2
The out-of-the-box section pyAssignmentListGadget was generating duplicate work object ids when pyAssignmentsLabel was used to display the case/Assignments label & ID in Case contents. This was caused by changes made in a previous version intending to enhance the displaying of labels, and has been modified to avoid duplicate work object IDs.
SR-A7590 · Issue 216110
Corrected parameter page used when Flowproblems restarts
Resolved in Pega Version 7.2
Restarting the problem flow was not taking the mandatory parameters defined in the flow, instead generating the error "Required parameter Parameter_name." To correct this, the flow method body has been modified to populate the parameter page from the pyFlowParameters page before checking for mandatory parameters.