SR-123127 · Issue 185219
Improve error handling for File Listener
Resolved in Pega Version 7.1.8
The File Listener not processing all files successfully when there was more than one file to be processed. This was caused by missing logic for the clearing of 'hasOnce' at the file level for the record type. Since 'hasonce' was not cleared at file level, once a file with an incorrect configuration is processed, others files were also getting processed as errors. This has been resolved by adding code to reset the 'hasonce' on a per file basis so File Listener is able to process multiple files.
SR-123130 · Issue 184202
Added apostrophe handling for navigation rule item names
Resolved in Pega Version 7.1.8
If an apostrophe (') was present in the label of Navigation rule item name, the onclick functionality of menu option was not working and threw a JavaScript error. In this JS file, the eval(strAction) function call failed because strAction text contains all the parameters enclosed in single quotes: if the label contains an apostrophe, that became an extra quote in this text. To avoid this, the functions pzMenuBarTranslator and pzActionShowHarness have been modified to handle extra apostrophes passed by the label.
SR-123136 · Issue 182969
Corrected Worklist filtering for dynamic Repeat Grids
Resolved in Pega Version 7.1.8
Worklist filtering was not working for columns added to the Repeat Grid dynamically using virtual report definition. This was a functionality gap in handling show/hide and filtering on dynamic columns virtual RD bound grid, and has been fixed.
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-123149 · Issue 184289
SOAPRequestEnvelope parameter added for custom Auth Activity
Resolved in Pega Version Pega Platform, 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-123152 · Issue 184296
Adjusted error handling of "Prebuild Conclusions" during upgrade
Resolved in Pega Version 7.1.8
The "Prebuild Conclusions" task of an upgrade was failing with the error 'ClassNotFoundException'. This was caused by a misconfiguration in the operating environment that led to the jar file that contains the class not being on the classpath during the upgrade. There was a workaround of setting the build.conclusions=false, but a check has been inserted that will skip these error entries and continue building the remaining conclusion entries.
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-123228 · Issue 184623
Charts code updated for resizing with new browsers
Resolved in Pega Version 7.1.8
After upgrade, summary view charts viewed with the latest version on Microsoft Internet Explorer were not reflecting any change of height even when the height was increased in the parameter tab or the cell. This was due to the parameters for the chart control not containing an expected trailing 'px' on the number that the browser required to know the expected unit of measure. Checks have now been inserted into the code to handle the conversion for the browser.