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-127803 · Issue 192265
Error information enhanced for Connector wizard working with external Teradata DB
Resolved in Pega Version 7.1.8
When using Teradata as an external DB, an exception was generated while using the SQL connector wizard and no rules were generated. This was caused by passing a date column that was not supported. The error has been addressed to make it more informative, but at this time the classes and properties for the fields and the mapping of the classes to the associated tables must be done manually. If the decision is made to use Date/Time properties that are mapped to Date fields, there may be time zone conversion issues. Further, mapping a Date property to the DATE column will allow the field to come across from a report definition but will not work as part of the filter (e.g. EFFT_DATE > "2014-12-01").
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-127811 · Issue 193487
Localization added to RTE tooltips
Resolved in Pega Version 7.1.8
Localization has been added for RTE tool tips.
SR-127829 · Issue 192723
Magnifying glass popup fixed for XML-stream element mapping data
Resolved in Pega Version 7.1.8
After importing XSD through the Connector and Metadata Wizard, double-clicking on an element-mapping to bring up the magnifying glass popup returned the error "Unable to open the rule as Base Class Value is empty". This was traced to a recent change that converted Ruleforms from form-based to harness-based, and OpenRuleAdvanced control has been modified to handle the XML stream information correctly.
SR-127853 · Issue 193472
Locking updated for hidden elements in Data Type records
Resolved in Pega Version 7.1.8
If Data Type records were being edited, the lock on the row being edited was not released unless a change was made. This led to locks being left over once the operator has closed the Data Type and other operators were prevented from editing those rows. The problem was that change tracking was not getting invoked for the hidden elements present in the section for each row, and this has been added.
SR-127853 · Issue 193468
Locking updated for hidden elements in Data Type records
Resolved in Pega Version 7.1.8
If Data Type records were being edited, the lock on the row being edited was not released unless a change was made. This led to locks being left over once the operator has closed the Data Type and other operators were prevented from editing those rows. The problem was that change tracking was not getting invoked for the hidden elements present in the section for each row, and this has been added.
SR-127880 · Issue 193696
Rest Connector wizard updated for custom naming conventions
Resolved in Pega Version 7.1.8
After migrating, a data model generated using the Rest wizard would fail when attempting to map a response using pxResults of Code-Pega-List. The mapping logic has been updated to better handle custom naming conventions.