SR-117266 · Issue 173481
Prompt Select modified to properly handle XSS functions
Resolved in Pega Version 7.1.7
A selection made in Prompt Select was not retained after refresh when special characters were present in the selected value. This was caused by XSS filtering functions that compared an encrypted value with the prompt value and negated it when it wasn't equal. To fix this, PromptSelect has been modified to call the crossScriptingFilter API before appending strDefaultValue to the stream.
SR-133545 · Issue 206691
Closed potential vulnerability in (deprecated) pyNote attach function
Resolved in Pega Version 7.1.9
In order to close a potential vulnerability with pyNote executing a script that is embedded in the note, the handling has been replaced with 'richtext'. However, while the Notes feature is still included in the system for backwards compatibility, please note that Notes has been deprecated and replaced by Pulse.
SR-A3149 · Issue 209034
Added handling for Oracle functional indexes of length '1'
Resolved in Pega Version 7.1.9
The SchemaChangeUtils class was throwing a java.lang.StringIndexOutOfBoundsException when an administrator attempted to view the "Missing PRPC Shipped Schema" section of the "PRPC Schema Report" page after upgrade (System -> Release -> Upgrade -> PRPC Schema Report). This appeared to lead to the message "Can not render section" in the PRPC schema report UI. The StringIndexOutOfBoundsException was due to Oracle functional indexes of length '1' which were not handled while doing a substring in schemaChangeUtils class: this handling has now been added.
SR-A2860 · Issue 207205
Expand Collapse icon function corrected for repeating grid
Resolved in Pega Version 7.1.9
The Expand Collapse icon for expand pane repeat grid stopped working when configured with Expand / Collapse flow action and "Display multiple rows" unchecked. This was an issue with the comingfromadd flag not being reset correctly after deleting a row, and has been fixed.
SR-A3384 · Issue 212375
Added negation(!) handling for 'when' functions in icon control
Resolved in Pega Version 7.2
After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.
SR-A3384 · Issue 211149
Added negation(!) handling for 'when' functions in icon control
Resolved in Pega Version 7.2
After migration, the 'when' rule was not evaluating negation(!) correctly in the deprecated icon control. This was caused by changes in the assembly logic stream generation treating 'when' expressions differently when negation is present, and has been resolved by passing the compiled 'when' rule to the handleEvaluateWhen function.
SR-A23473 · Issue 246023
WordTextArea function tuned for Microsoft Internet Explorer 11
Resolved in Pega Version 7.2.1
The WordTextArea was displaying base64 encoded text in the IE11 browser. This was a compatibility problem, and the WordInclude.js ' after edit' functionality has been tuned.
SR-A22699 · Issue 248560
RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType Timer function corrected
Resolved in Pega Version 7.2.2
The Timer function used in the RuleServiceFile.parseRecordAtTime and RuleServiceFile.parseByRecordType functions was not properly halting when it encountered an exception, causing any subsequent invocation to these methods to start the Timer again. This created errors and incorrect results. The parseRecordAtTime and parseByRecordType methods have now been updated to enclose inbound mapping related stopTiming within a finally block for accuracy.
SR-B38980 · Issue 299227
createDateTimeCategories function modified to use operator time zone
Resolved in Pega Version 7.3
A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.
SR-B41652 · Issue 299895
createDateTimeCategories function modified to use operator time zone
Resolved in Pega Version 7.3
A report definition chart using the operator time zone of "Europe/London" and locale "en_US" displayed duplicate date columns. Updating the operator time zone to "America/New_York" removed the problem. This issue was caused by the system always parsing/formatting the date with the default local time zone, and has been resolved by modifying the parseDate/formatDate/createDateTimeCategories function to use the operator time zone instead.