SR-125894 · Issue 192175
Home button fixed for Microsoft Internet Explorer 8 user portals
Resolved in Pega Version 7.1.8
The Pega "home" button was not working in user portals with the Microsoft Internet Explorer 8 browser. This was a special use case in Microsoft Internet Explorer 8, where the inner tag had style set with display:none through CSS, hence was click firing on the tag instead of
element. This has been fixed by adjusting the 'processBehavior' function in the file 'pzpega_ui_events.js'.
SR-125895 · Issue 188735
Close button fixed for work elements with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
The Close button on work items in CaseWorker was not working in the Microsoft Internet Explorer 8 browser. This was due to 'document.getElementsByclassName' not being supported in Microsoft Internet Explorer 8, and it has been replaced it with the cross-browser jQuery class selector API to get the element with class name.
SR-125895 · Issue 189356
Close button fixed for work elements with Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
The Close button on work items in CaseWorker was not working in the Microsoft Internet Explorer 8 browser. This was due to 'document.getElementsByclassName' not being supported in Microsoft Internet Explorer 8, and it has been replaced it with the cross-browser jQuery class selector API to get the element with class name.
SR-125906 · Issue 192682
Work object locking improved for Advance Flow
Resolved in Pega Version 7.1.8
An Advance Flow call in SLA gave a 'lock not held' error on commit when it was used in subcases where the parent has a dependency (e.g. waiting for the child to resolve). This was a problem where the commit released the work object before the escalation action was executed, and has been resolved by modifying 'SpawnQueueItemForFlowDependency' to open and set the new transaction before and after the commit.
SR-125910 · Issue 194305
Corrected data population in report for exposed column
Resolved in Pega Version 7.1.8
Data was not being populated in a report for an exposed column when it was dragged and dropped from the data explorer of Report Editor. This was caused by the CreateColumnPage fieldName being hard-coded to Param.FieldName for embedded page properties, and has been changed to set FieldName conditionally.
SR-125913 · Issue 192447
Fixed file attachments in Mobile
Resolved in Pega Version 7.1.8
When using the AttachContent Control functionality in mobile, attaching a file popped up a window with the message 'File attached successfully', but no Action Sets associated with file attachments were actually run. Using the same functionality on desktop did not have any issues. This problem was traced to an error in the JavaScript code for the mobile control relating to the access group, and has been corrected.
SR-125929 · Issue 189682
Add Child navigation rule timing improved
Resolved in Pega Version 7.1.8
Attempting to set "Add Child" as a Navigation rule that performed an action on the selected row within a tree Grid using a modal dialog was generating a JavaScript error if used on the last row. When the "Add Child" action was selected, it attempted to add a child to the current row also set focus on the new entry, but at the time of the call to the selectRow function the Tree Grid has not yet been updated to include the additional child element. This caused the row variable to be evaluated as null. To correct this, a null check has been added that will correct the timing issues.
SR-125934 · Issue 190270
Adjusted modal dialog height functioning with repeating grid
Resolved in Pega Version 7.1.8
When using a repeat grid to open a modal dialog to add rows, the modal dialog height was getting increased by scroll adjustment always, which should be done only when its scrollHeight is greater than offsetHeight. Code changes have been made in the setModalDialogHeight function to correct this.
SR-125937 · Issue 190307
Aligned Connector lines in Process Modeler
Resolved in Pega Version 7.1.8
Upon opening a flow rule, the Connector lines in Process Modeler were rerouted inconsistently with what was the saved state of the rule. The root cause was traced to code defects that resulted in the incorrect display of an error message and the incorrect drawing of the connector lines when the process modeler is loaded. These have been corrected.
SR-125975 · Issue 194136
XMLTreeViewBuilder enhanced to support default value passing for XSD
Resolved in Pega Version 7.1.8
When running the Connector & Metadata Wizard, the generated XML Stream rule did not include the default value defined in XSD. To correct this, support has been added for default value in XMLTreeViewBuilder so it will be passed to XML stream and parse rules.