SR-114819 · Issue 175544
Localization added for currency values using commas vs decimal points
Resolved in Pega Version 7.1.8
Excel within PRPC was not properly localizing for the use of decimal and comma as thousand and decimal separators for decimal/double currency property values, a use that is common in non-English installations. The records editor has been changed to support localization for properties of type double and decimal.
SR-115526 · Issue 178638
Epilog activity correctly executing for asynchronous queues
Resolved in Pega Version 7.1.8
When configuring a File Listener and Service-File for Asynchronous execution queue, the Epilog activity was not being executed. There was a workaround of switching to synchronous execution, but this issue was traced to a logic flaw that created a race condition between the processing of the file parsing (which occurs in one thread) and the row processing (which occurs in a separate thread) and has been resolved.
SR-117345 · Issue 179910
"Edit in Excel" handling corrected for delegated decision tables
Resolved in Pega Version 7.1.8
"Edit in Excel" was not working correctly on a decision table if it was delegated to a WorkManager portal from a traditional portal. After clicking on the edit button two pop ups appeared, and the Excel sheet was not visible after the pop ups were dismissed. This was traced to an issue with ActiveX where the server was not getting a fully-qualified URL in cases of open portal threads, and a check has been added to ensure proper handling.
SR-117931 · Issue 181714
Resolved clipboard conflict for obj-open-by-handle
Resolved in Pega Version 7.1.8
Doing an obj-open-by-handle or obj-open-by-handle/copy on work objects containing properties that reference data pages caused errors about non modifiable pxObjClass properties and non matching clipboard property modes. This was caused by a clipboard conflict, and has been addressed by handling the clipboard property as set value for feature property.
SR-118044 · Issue 178369
Corrections and enhancements made to Outlook meeting requests
Resolved in Pega Version 7.1.8
Using the function 'SendEmailMessage' to send an Outlook meeting request was only generating an email instead of the full meeting invitation. This was traced to unimplemented code and has been corrected. In addition, enhancements have been added to the FormatMeetingRequest RUD to set RSVP options for TO & CC recipients, and the PRODID flag value has been parameterized.
SR-118160 · Issue 175398
Email Listener performance improved
Resolved in Pega Version 7.1.8
A mismatch in time values was causing Email Listener to be extremely slow in some complex installations. This has been corrected to improve performance.
SR-118269 · Issue 174402
Eform wizard upload error resolved
Resolved in Pega Version 7.1.8
When attempting to upload a file using the EForm wizard, an error was generated stating "The Flow Action post-processing activity PopulateFileRule failed" and the file did not upload. The root cause of this ruleset problem was that the necessary class was not present in the JAR, and has been resolved.
SR-118440 · Issue 178175
Sorting fixed for RD Repeat Grids with joined properties
Resolved in Pega Version 7.1.8
When sorting a Repeat Grid based on a Report Definition, if the user tries to sort on a property from a join then it would fail with the error 'Cannot get property information for: Assign-Worklist..' This was caused by ObjClass being missing for few elements of page list, and has been fixed. In addition, a check has been added to ensure proper handling in cases where Obj class is missing.
SR-118474 · Issue 182925
Corrected time zone mismatch in Report Browser
Resolved in Pega Version 7.1.8
If a server and an operator had different time zones set, reports that were scheduled through the report browser to run and deliver notifications to a list of recipients would run immediately if the schedule was modified. To handle this time zone difference, "Pega-ScheduledTask.pzPostProcess" has been modified to use the time zone from calendar in the formatter.
SR-118474 · Issue 178295
Corrected time zone mismatch in Report Browser
Resolved in Pega Version 7.1.8
If a server and an operator had different time zones set, reports that were scheduled through the report browser to run and deliver notifications to a list of recipients would run immediately if the schedule was modified. To handle this time zone difference, "Pega-ScheduledTask.pzPostProcess" has been modified to use the time zone from calendar in the formatter.