SR-123245 · Issue 185467
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.
SR-123245 · Issue 185150
Resolved frame stack error with Flow GenerateAndProcessRequirements
Resolved in Pega Version 7.1.8
Flow GenerateAndProcessRequirements had an error in step Utility2 that generated a Frame stack error. This was caused by the method used for ClipboardObjectImpl.getThread(): in the case when owning thread is from a different requestor, it is possible that two requestors are simultaneously executing on the owning thread. In this case, the PRStackFrame push pop calls from both the requestors (foreground browser requestor and background declare trigger activity requestor) interfered with each other and caused the error. This has been fixed. / UpdateOpenCoveredTasks was causing null pointer exception due to the trigger activity, 'Work-Cover-. UpdateOpenCoveredTasks' not being available to this activity - the trigger is defined to run in background. Exceptions are thrown because the system was checking for messages on tempWorkPage page and tempWorkPage was being deleted in few cases. To fix this, a condition has been added to check whether tempWorkPage exists before checking for messages on it.
SR-123249 · Issue 184707
Stale stage completion checkmarks cleaned up
Resolved in Pega Version 7.1.8
When using a Split-For-Each shape with "Join" field set to "Iterate" and the Harness set to "TreeNavigation7" on a sub process tabbed screen Flow, the green tick marks which appear after completion of every stage in screen flow were not resetting for new items in the page list. Closing the workobject by clicking on red (X) mark and then reopening the same work object reset it properly. This was caused by missing logic to check whether FlowData should be reused or not, and has been fixed.
SR-123303 · Issue 185053
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123303 · Issue 176110
Corrected Case match rule reporting
Resolved in Pega Version 7.1.8
The Case match rule was not reporting results that were greater than the cut off score. This has been corrected by changing the rule RunDuplicateCasesReport to check on InsKey instead of pyID as InsKey is available for all pages of different classes where pyID is not.
SR-123330 · Issue 188222
Resolved exceptions generated by empty property values
Resolved in Pega Version 7.1.8
Empty values passed to the java object were generating the exception "ProjectName.value is blank and the jar file expecting a value". This was an issue with a new code generation strategy on property set where the empty value set on a java property was not setting it on the wrapper. This has been corrected.
SR-123344 · Issue 185832
DeleteOrphanStaticContent activity modified to prevent CSS errors
Resolved in Pega Version 7.1.8
The DeleteOrphanStaticContent is used to delete any un-used assembled static contents, but it was sometimes deleting CSS files that were still in use by the system, causing 404 errors. This activity has been changed to use use the node statue query in order to ensure it clears items correctly.
SR-123344 · Issue 191091
DeleteOrphanStaticContent activity modified to prevent CSS errors
Resolved in Pega Version 7.1.8
The DeleteOrphanStaticContent is used to delete any un-used assembled static contents, but it was sometimes deleting CSS files that were still in use by the system, causing 404 errors. This activity has been changed to use use the node statue query in order to ensure it clears items correctly.
SR-123434 · Issue 183436
Smoothed post-upgrade ApplicationSetup that uses previously generated LDAP configs
Resolved in Pega Version 7.1.8
An LDAP configuration created under a previous version of the software was generating an NPE after upgrading. This was traced to step2 of the ApplicationSetup activity where the system was expecting a page which was missing at that point due to the user not yet being fully identified. To avoid this, a step has been added to check if the page is available and avoid the NPE.
SR-123444 · Issue 185535
DateTime conversion corrected for Excel
Resolved in Pega Version 7.1.8
When parsing an Excel file and extracting the values, the DateTime fields were being returned as a double value. This was an issue with the date to decimal conversion in the toLocal and toGMT functions, and has been corrected.