SR-123209 · Issue 181230
Fixed validation Issue with Map eForm rule
Resolved in Pega Version 7.1.8
A validation error occurred when the system was not able to refer to property which was in a nested page group in Map eForm rule even though the property existed. To resolve this, code has been modified in the validation activity to correctly handle data with parentheses.
SR-123235 · Issue 183263
Additional localization for attachments functions
Resolved in Pega Version 7.1.8
Localization has been added in the attachments section for the "Attachment" link, "Attach URL", 'Add new party" in the work parties modal, and the "Save Draft" button.
SR-123242 · Issue 183215
Stage names now incuded in localization wizard
Resolved in Pega Version 7.1.8
Previously, Stage names were not picked up by the localization wizard unless each Case Type was saved in the application. An enhancement has been added to allow them to be localized more efficiently.
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-123492 · Issue 184136
Page properties cannot be configured in remote case types
Resolved in Pega Version 7.1.8
The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.
SR-123492 · Issue 183606
Page properties cannot be configured in remote case types
Resolved in Pega Version 7.1.8
The implementation of the Case Type advanced tab allowing page properties to be referenced under 'publish as a remote case type' was sometimes generating a validation error. As this is a complex issue, the abilty to configure Page properties in remote case types has been removed at this time.