SR-118486 · Issue 175139
XSS filtering improved for Host and Gateway
Resolved in Pega Version 7.1.8
For security, XSS filtering has been improved on hostconfig.jsp and GatewayAdminUtils.java .
SR-118602 · Issue 178489
Corrected flow action dropdown execution
Resolved in Pega Version 7.1.8
For certain work objects, selecting a flow action from the pyAction area resulted in an error message and the flow action did not execute. A sample error message might be "The FlowAction ... could not be added to this assignment." This was caused by a flaw in the code which assumed that simple integer IDs in the DOM are unique. The code that handles 'Take Action' input has been re-factored to be more robust.
SR-118615 · Issue 172704
Addressed XML handling for "Expand Java Pages"
Resolved in Pega Version 7.1.8
After upgrading, an IOException occurred while updating a work object if "Expand Java Pages" was unchecked in General options -> Tracer Settings. When the checkbox is enabled, the Javaobject wrapper uses its custom read/write methods to serialize the page. When unchecked, default serialization invoked the ParseXMLSAXRulWrapper.java which contained some properties which are not Serializable. In order to ensure proper XML handling, changes were made to XMLStream.java so the code flow is independent of the expand java pages option in tracer and always takes the custom serialization path.
SR-118735 · Issue 175180
Addressed ruleset integrations problems using Google Chrome
Resolved in Pega Version 7.1.8
When using Google Chrome and running the Integration > Tools > Rule-From-File wizard, the ruleset version was not displayed and it was not possible to proceed past the screen that requires values for rule name, ruleset, ruleset version and class name. This was due to there not being an input field for RuleSet Version, and the validation of that step in the wizard fails. This issue occurred due to Google Chrome not supporting the use of document.all in the HTML code, leading to an undefined value for the JavaScript. This has been resolved by changes to the HTML to make it browser code independent.
SR-118755 · Issue 177568
Enhanced logging for access group decisions
Resolved in Pega Version 7.1.8
In order to facilitate troubleshooting, logging has been added to track how the Core Engine decides what Access Group to assign to the running Agent. This lists the name/ruleset/ruleset version of the Data-Agent-Queue record being utilized, the Access Group specified by it, and any further steps that determine what AG gets used. If the DAQ gets rebuilt, it will show how it gets rebuilt from the Rule-Agent-Queue record.
SR-118795 · Issue 180517
MaxLength enforced for attached notes in properties
Resolved in Pega Version 7.1.8
If a MaxLength was given in the Advance tab for a pynote property from data-workattach-note class, it was still possible for attachments to exceed the MaxLength with no error generated. This was caused by a missing step, and the system will now check if there are any page set messages on Note page before saving.
SR-118827 · Issue 179258
Work object reloading added to SFA portals
Resolved in Pega Version 7.1.8
When a work object in an SFA default portal (such as SFA SalesManager and SFAAdministrator) was opened by multiple users, modifications made by one were not seen by the other unless the other completely logged out and back in again. This was a function of the way the work object was opened and held in a thread, and has been modified with an API to reload the work object each time it is opened so that any saved changes are immediately available.
SR-118902 · Issue 178085
Updated PDF conversion for latest versions of Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.
SR-119090 · Issue 179954
Progressive Paging Header Alignment Issue corrected
Resolved in Pega Version 7.1.8
On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.
SR-119090 · Issue 175018
Progressive Paging Header Alignment Issue corrected
Resolved in Pega Version 7.1.8
On page load, the column headers for repeat grid with expand details did not align with the data when using Progressive Pagination. The root cause of this problem was with the design of Repeat Grids with 'Pagination' and Expand Details involved: the headers for Repeat Grid were created as separate table which failed to synchronize size with the table containing the data. To resolve this, changes were made in the GenerateGridHTML Function.