SR-127091 · Issue 193209
Forward chaining commit error resolved
Resolved in Pega Version 7.1.8
A sporadic pyCommitError was observed when performing 'Action' during a 'Phone call' interaction for a specific user. During forward chaining, a malformed variable change that occurs when a page copy happens on a embedded page of a work page is recreated in order to not corrupt the fragment collection cache. Previously, this was done only while evaluating the declare expressions. The system has now been updated to do the same during evaluation of other declarative flavors during forward chaining.
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-128179 · Issue 197764
Pagination added for ruleset versions ruleform
Resolved in Pega Version 7.1.8
Opening the Developer ruleform to view a ruleset in an environment containing multiple rulesets with thousands of versions presented performance issues where rendering took multiple minutes and scrolling was impossible due to the very large file size. To improve performance, pagination has been enabled for the ruleset versions section.
SR-128192 · Issue 193639
Libraries updated to reflect ruleset versions
Resolved in Pega Version 7.1.8
New ruleset versions were not showing in the Library. This was caused by improper version population: when a version-resolved rule (such as property/section) was created, a a data page would hold the default ruleset version. When a library (which is non version-resolved) was created, the default ruleset version was not reset and it became associated to the library rule. A fix has been added to reset the value of pyRuleSetVersion.
SR-128228 · Issue 193947
Smoothed locking for cloud team logins
Resolved in Pega Version 7.1.8
In a large cloud team, a high number of simultaneous logins caused a requestor lock exception that required a system restart to resolve. This was caused by threads deadlocking while attempting to acquire a common resource during compilation. To resolve this, the locking has been modified to sync requests in order to ease congestion.
SR-128380 · Issue 194162
Refined Excel specifications import
Resolved in Pega Version 7.1.8
Importing specifications from Excel was registering unexpected characters. This was caused by the system mistakenly importing rPh tags from the "sharedStrings.xml" in the "xl" folder, and has been corrected.