SR-123149 · Issue 184289
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".
SR-123149 · Issue 186790
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version 7.1.8
In some cases, the SOAP request envelope content was not available to the authentication activity called by the auth service protocol. Since the operator ID is derived via a decision table from a different value in the SOAP request envelope, there was no way to use that value as an input to the new authentication activity. To correct this, SOAPRequestEnvelope is now made available on the parameter page of customAuth Activity with name "pxReqSOAPEnvelope".
SR-123209 · Issue 183265
Fixed validation Issue with Map eForm rule
Resolved in Pega Version 7.1.8
A validation error occurred when the system was not able to refer to property which was in a nested page group in Map eForm rule even though the property existed. To resolve this, code has been modified in the validation activity to correctly handle data with parentheses.
SR-123209 · Issue 181230
Fixed validation Issue with Map eForm rule
Resolved in Pega Version 7.1.8
A validation error occurred when the system was not able to refer to property which was in a nested page group in Map eForm rule even though the property existed. To resolve this, code has been modified in the validation activity to correctly handle data with parentheses.
SR-123233 · Issue 183081
Localization enabled for DisplayRFHarnessErrors in Rule-Obj-Flow
Resolved in Pega Version 7.1.8
Rule DisplayRFHarnessErrors is in two different classes, @baseclass and Rule-Obj-Flow. The localize check box was checked for rule under @baseclass and not for Rule-Obj-Flow. The DisplayRFHarnessErrors rule form has been made available for localization in both areas.
SR-123233 · Issue 180467
Localization enabled for DisplayRFHarnessErrors in Rule-Obj-Flow
Resolved in Pega Version 7.1.8
Rule DisplayRFHarnessErrors is in two different classes, @baseclass and Rule-Obj-Flow. The localize check box was checked for rule under @baseclass and not for Rule-Obj-Flow. The DisplayRFHarnessErrors rule form has been made available for localization in both areas.
SR-123234 · Issue 183083
Localization added for 'clear filter' tooltip
Resolved in Pega Version 7.1.8
"Clear filter" on a grid which has filtering enabled has a hovering tool tip that reads "Enter to clear filter". This value was not previously available for localization, but has been made available.
SR-123234 · Issue 180108
Localization added for 'clear filter' tooltip
Resolved in Pega Version 7.1.8
"Clear filter" on a grid which has filtering enabled has a hovering tool tip that reads "Enter to clear filter". This value was not previously available for localization, but has been made available.
SR-123238 · Issue 183084
Localized constant values in read-only format
Resolved in Pega Version 7.1.8
Constant values in read-only format in the formatted text control were not being picked up in the localization wizard. This was a defect in the GenerateFormat RUF, and has been fixed.
SR-123238 · Issue 178781
Localized constant values in read-only format
Resolved in Pega Version 7.1.8
Constant values in read-only format in the formatted text control were not being picked up in the localization wizard. This was a defect in the GenerateFormat RUF, and has been fixed.