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.
SR-127884 · Issue 195662
Conditional visibility updated for two-column dynamic layout
Resolved in Pega Version 7.1.8
When using a Two-Column Layout inside a section where each column has a Dynamic Layout with a single label in it, the left column was also hidden if the right column had visibility set to Never. To correct this, CSS selectors have been added to maintain the visibility of the left sidebar column when the main column is empty or missing and the left column is not marked as hidden.
SR-127915 · Issue 198737
Added handling for client-side encrypted data being passed to server encryption
Resolved in Pega Version 7.1.8
A Rule Not Found exception was being generated when using urlencryption and SubmitObfuscatedURL. This was an issue where the system was not prepared to handle URL encryption encoding/decoding that had already been performed on the client side instead of the server side. The Control Generation Logic of pzActionOpenURLInWindow has been updated to handle this scenario.
SR-127922 · Issue 196912
Fixed child validation in repeating tree grid
Resolved in Pega Version 7.1.8
The required validation was not firing in a repeating tree grid for a child item but was working for the parent Item. This was a problem with the Clientvalidation parameter not being set when the child nodes were expanded, and the proper parameters are now being sent for client validation.