SR-117827 · Issue 186000
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-117827 · Issue 183888
Improved condition handling for complex harnesses
Resolved in Pega Version 7.1.8
If a Review Harness had multiple embedded tab sections with includes, a read-only condition in the parent section was not being honored in a sub-section if the 'when' condition became false. This happened when a SectionIncludeInCell RUF passed an unquoted null value as a 3rd argument while invoking stream reference, and has been resolved.
SR-118213 · Issue 184519
Refresh When' behavior fixed for portal tabs
Resolved in Pega Version 7.1.8
When a 'Refresh When' was active on a portal tab, the system would become unresponsive while trying to refresh it. This was caused by an incorrect element call resulting in a JavaScript error and has been corrected.
SR-118283 · Issue 180166
Create New Work functionality smoothed for flows across multiple windows
Resolved in Pega Version 7.1.8
The Create New Work functionality in IAC was intermittently rendering incorrect data when opening a workflow in multiple windows. This was found to be a problem with PostDataId generated duplicate IDs for the different requests and has been changed to generate unique IDs.
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-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.