SR-116899 · Issue 169326
Edit validation displays literal characters
Resolved in Pega Version 7.1.7
If a property with edit-validate defined on it is included in a section with the control TextArea used, an error message is shown on top of the property if the edit validate returns false. However, the error was not shown as literal but rather displayed the encoded characters and was difficult to understand. This was traced to double encoding of characters like ">" in the displayed string, and has been changed so the literal character will appear.
SR-116903 · Issue 167940
Recent Explorer item handling corrected
Resolved in Pega Version 7.1.7
When opening a Scheduled item from Recent Explorer, an incorrect flow was being called and the Review Harness buttons (which are based on flow parameters) were incorrect. This was traced to a missing TaskWrapper activity, and has been corrected. In addition, a process was added to check property as well as parameter in the Review Harness.
SR-116908 · Issue 168347
When rules now display all text fields for function aliases
Resolved in Pega Version 7.1.7
Creating a new Access When rule failed to show the text fields for most available function aliases when a condition was added to the rule. This was an error in the passing of the classname to the function, and has been fixed.
SR-116936 · Issue 167898
Discarded threads set to properly clear on refresh or tab close
Resolved in Pega Version 7.1.7
When the browser was refreshed or an inactive recent tab was closed on the client side, the discarded threads were not getting properly cleared at the server end. To remedy this, the JavaScript has been updated to cleanly remove the threads.
SR-116941 · Issue 168143
Improved performance for sending queued messages
Resolved in Pega Version 7.1.7
LogToSpecifiedAppender was experiencing poor performance in some situations caused by duplicating locking attempts while processing an appender to send queued messages. To improve this, code changes have been made to smooth locking and avoid searching appenders when dynamic appenders are configured.
SR-116950 · Issue 167458
Rule name validation checks relaxed for draft mode
Resolved in Pega Version 7.1.7
In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.
SR-116950 · Issue 168328
Rule name validation checks relaxed for draft mode
Resolved in Pega Version 7.1.7
In order to facilitate flow design, Decision shape properties will no longer require rule name validation when using Draft Mode.
SR-116989 · Issue 170784
XSS alert resolved for integer type property in Edit Data Table
Resolved in Pega Version 7.1.7
The presence of an integer type property in Edit Data Table was generating an XSS alert. This was caused by changes in the html- getMessagesAll that rendered the property value directly, and has been updated to an XSS-safe API.
SR-117020 · Issue 167867
Cookies only generated if IAC enabled
Resolved in Pega Version 7.1.7
IAC cookies were being generated in environments where IAC was not deployed, causing the application be flagged in a security audit due to missing Secure attributes. To correct this, the system has been updated to bypass cookie generation if IAC is not in use.
SR-117039 · Issue 169671
Standardized class display options for App Explorer
Resolved in Pega Version 7.1.7
Inconsistencies had appeared in how Application Explorer handled switching the display between name and label (short description) in the class hierarchy display. The App Explorer menu now shows the option to toggle between Class labels and Rule names, with a default setting of displaying Rule names. In addition, the short description display will not include the rule purpose.