SR-127035 · Issue 193206
Improved opening custom flow rules with Microsoft Internet Explorer 9
Resolved in Pega Version 7.1.8
Opening up a flow rule with many sub-process references was taking an excessive amount of time when using Microsoft Internet Explorer 9 due to general browser slowness and the system loading all referenced flow rules at that time. This has been resolved by tuning the JavaScript code to improve the performance of the viewer and to disable drilldown functionality from the server.
SR-127754 · Issue 192902
Modified TransferAssignment to pass SLA parameter with Reassign
Resolved in Pega Version 7.1.8
Assigning the work object configured with an SLA from workbasket to worklist using the out-of-the-box Transfer flow function before the Goal/deadline was reached caused the SLA escalation action to not be triggered when the deadline expired. This was due to the UpdateSLA parameter not being sent when Reassign was called as a post processing activity of the Transfer flow action. This flow action has been deprecated in later releases and replaced by the new flow action pyTransferAssignment, and the ReassignAssignment activity has now been modified to pass the updateSLA param while calling Reassign.
SR-127806 · Issue 195855
Sort by ID enhanced to handle custom ID formatting
Resolved in Pega Version 7.1.8
Sort by ID was not working correctly for workbasket/worklist if the workID was in the format String-Number-Number and not in expected format of either String-Number or String-Number-String. The Pega-RULES:compareWorkIDs function responsible for sorting the workID assumed the ID would be in this format because it used pxRefObjectInsName - an internal property that could not be overridden. However, it was possible to create another property in the "Assign-" class of a custom rule set that could be updated with the value of pxRefObjectInsName by iterating it through the list, and then it could be configured in a grid as sortable row which could further be sorted through a custom sort function. An enhancement has been added to the compareWorkIDs function to handle IDs in the String-Number-Number format with additional handling for 2 part vs. 3 part IDs.
SR-127809 · Issue 192785
Stage processing refined for casetype launch
Resolved in Pega Version 7.1.8
If SLA was configured for the case type (case wide SLA) it caused the exception "Reconcile inconsistency in stage processing" once the SLA was triggered. This error also occurred when the flow was run on a modal dialog. This was caused by the pxStageFlowID not being set on the pxFlow of the custom flow being called from the SLA. Any flow started backdoor -- via activity, SLA, subprocess, etc -- should not be considered part of the stage processing, and the code has been updated to ensure flows that are not started in the context of the casetype or stage are no longer logged as part of stage history and do not go into stage flow end processing.
SR-127820 · Issue 192785
Stage processing refined for casetype launch
Resolved in Pega Version 7.1.8
If SLA was configured for the case type (case wide SLA) it caused the exception "Reconcile inconsistency in stage processing" once the SLA was triggered. This error also occurred when the flow was run on a modal dialog. This was caused by the pxStageFlowID not being set on the pxFlow of the custom flow being called from the SLA. Any flow started backdoor -- via activity, SLA, subprocess, etc -- should not be considered part of the stage processing, and the code has been updated to ensure flows that are not started in the context of the casetype or stage are no longer logged as part of stage history and do not go into stage flow end processing.
SR-127961 · Issue 192637
Corrected reference name for doc attached to work object by CreateMergedWordDoc
Resolved in Pega Version 7.1.8
When using the CreateMergedWordDoc flow action to create a document and attach it to the Work Object, the display showed the label used in "pyNote" as the document name. However, opening the document opens it under the category name. This was caused by a mismatch in the handling and has been corrected.
SR-128433 · Issue 194694
Added template to handle certificate needed by Word MacroManager
Resolved in Pega Version 7.1.8
Because the Word macrocode must be signed with a current certificate, a Signed and timestamped template has been added.
SR-128580 · Issue 199345
Localization added for Audit screen
Resolved in Pega Version 7.1.8
Localization was missing from the 'Complete Task' section of the Audit screen. This has been added.
SR-128620 · Issue 193739
MapCases error resolved with blank page check
Resolved in Pega Version 7.1.8
The MapCases function was generating sporadic errors at a Wait Shape or after Updatestatus that required a logout/login before it was possible to proceed with the Case. MapCases runs tools.findPageByHandle(coverinskey) which can lead to an empty page being returned by the engine if one exists, leading to this error; a blank page check has been added that will then use the default work page if the cover key is empty.
SR-129211 · Issue 195705
Ensured expected deadline priority styling in workbasket
Resolved in Pega Version 7.1.8
The WorkBasket summary for the current WorkGroup on the Case Manager Portal was going straight from "normal" (green) styling to "urgent" (red) styling once one of the assignments in the WorkBasket went past Goal but had not yet passed Deadline. The intended behavior should show a "medium" styling until such time as one or more of the assignments is past Deadline. Once past Deadline, the styling should then be "urgent". The incorrect benavior was caused by an ordering problem in the Deadline and GoalTime columns, and code has been inserted to ensure proper behavior.