SR-126907 · Issue 193779
Work objects in dynamic container corrected for the AES Manager portal.
Resolved in Pega Version 7.1.8
If a dynamic container is embedded in a section, the work objects opened through AES portal are opened in a dynamic container. When using the AES Manager portal with the Microsoft Internet Explorer 11 browser, work objects would open but then immediately the UI would scroll closed. This was a browser issue where harness tabs with IFRAME in production were not triggering the re-flow for DC tabs as they were for static tabs, and the system has been updated to perform this action correctly.
SR-127159 · Issue 192190
Handling added for declare expressions with null page directory
Resolved in Pega Version 7.1.8
The PropertyReferenceImpl.filter() API was an throwing exception if the directory was null for changes (the directory will be null if a copy of top level page is made). To resolve this, the API has been modified to use PRThread as directory if page directory is null.
SR-127161 · Issue 199350
Localization fixed for buttons with shortcut key options
Resolved in Pega Version 7.1.8
Localization was missing for labels on buttons with shortcut key options. This has been fixed.
SR-127180 · Issue 192478
Modified display of Listview filters to show action buttons
Resolved in Pega Version 7.1.8
After upgrading, Listviews used to generate reports that included filtering were not displaying the "Apply" and "Cancel" buttons in the drill-down pop up. To resolve this, the setscrollingDIVHeight API has been modified to properly display the content.
SR-127202 · Issue 192389
Join and Like filters tuned for Listview
Resolved in Pega Version 7.1.8
Listview join filters with LIKE operations were not performing optimal SQL queries, impacting system performance. This has been tuned to improve the system response.
SR-127210 · Issue 190272
Added table-based cataloging
Resolved in Pega Version 7.1.8
The Update Manager catalog has been updated to reside in the Pega database instead of in the file system. This will facilitate cataloging in a multi-node environment, allow for reporting and other visibility into the catalog itself, and improve performance of dependency checking.
SR-127231 · Issue 192212
Validation resolved for Class as property reference in Activity Name
Resolved in Pega Version 7.1.8
If the Class was given as the property reference, attempting to enter the Activity Name generated the validation error "Attempting to access the rule in Bad class name: .HARNESSCLASSNAME" and the rule could not be saved. This was traced to the Property reference not being supported for Activity Name, and that has been added.
SR-127237 · Issue 190840
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-127237 · Issue 189891
Time-related RUFs now use operator's time zone
Resolved in Pega Version 7.1.8
Date properties and Time properties were taking their reference from the server's default time zone, which created unexpected behaviors for operators in other time zones using start and end date functions. This has been resolved by updating the time-related RUFs to use the operator's defined time zone
SR-127256 · Issue 193682
Added trace to ensure system pulse syncs nodes after schemas added
Resolved in Pega Version 7.1.8
After editing a decision table on Node A, the Pulse/vtable on Node B was not invalidating the pulse entry, resulting in wrong rule getting picked up. This was caused by having two data schemas implemented, where the second one was put in place after the initial migration scripts were run. Therefore any rule change events were sent to the wrong schema. This has been corrected with an added vtable global trace.