SR-120518 · Issue 180099
Corrected error handing on"Post Action on Click Away"
Resolved in Pega Version 7.1.8
When an assignment in a screen flow was configured to use the "Post Action on Click Away" setting, it was not possible to go back if there were validation messages on the screen. Without the "Post Action on Click Away" setting, the click back worked and the validation message was cleared by the jumpToTask activity. This work flow issue has been fixed by clearing the page error messages before calling performflowaction.
SR-120566 · Issue 181231
Bulk Actions filtering error resolved
Resolved in Pega Version 7.1.8
In Bulk Actions, if a filter was renamed from "Assigned to Operator" to something else, ex "Application ID", the filter was not being applied. If the "Assigned to Operator" filter was deleted and a new one added, the filter was applied correctly. This was found to be an issue with the filters "Assigned to Operator" and "Assigned to Workbasket" setting the flag pyUsage = operator on the filter condition, causing a custom SQL to be generated. This has been corrected.
SR-120585 · Issue 182421
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.
SR-120586 · Issue 179198
Assignment dependencies with child cases now properly resolve
Resolved in Pega Version 7.1.8
Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.
SR-120586 · Issue 178686
Assignment dependencies with child cases now properly resolve
Resolved in Pega Version 7.1.8
Using a dependency on an assignment based on a child case can case an error. This was due to the obj class being wrongly populated, and has been resolved.
SR-120899 · Issue 183642
Work object history corrected for failed flow action submissions
Resolved in Pega Version 7.1.8
If a a flow action is submitted which encounters errors and generates Page-Messages, correcting the errors and re-submitting the flow action created duplicate entries in the work object history that included entries for the failed flowaction submission. This was caused by improper rollback of the addhistory when the commit of the WO is rolled back, and has been corrected.
SR-120977 · Issue 180096
File extension type now visible in the audit trail for attachments
Resolved in Pega Version 7.1.8
After files were uploaded and attached, it was seen that only the file name itself was found in the audit trail and there was no extension given. In order to pass the attachment file type extension, the pynote value will be passed as a parameter to the pyHistoryMemo FileAttached field value, and written to the audit.
SR-121112 · Issue 179088
Step names localized in Stage and Steps display
Resolved in Pega Version 7.1.8
Previously, Step names in the Stage and Steps display were not localized under the ButtonLabel Field Value rules in the same way as the Stage names. This was due to the title being derived from the control "StageProcessLink", which is a non-auto generated control being directly fetched in the HTML markup instead of querying the getLocalizedText method. This has been changed to allow Step names to be included in localization as expected.
SR-121135 · Issue 179497
Transfer and Reassign enhanced to work from embedded pages
Resolved in Pega Version 7.1.8
When a work flow is called from an embedded page, attempting to perform a transfer using the Out-Of-The-Box "Transfer" Flow Action was failing with the exception "The Flow Action post-processing activity Reassign failed: The reference .pyConfirmationNote is not valid. Reason: FUAInstance-NullMyStepPage". This was traced to the configuration not be prepared to work on an embedded page, and has been modified to direct the reassign activity to get the toplevel page if the step page is embedded.
SR-121471 · Issue 179231
Potential XSS vunerability eliminated
Resolved in Pega Version 7.1.8
The system has been modified to enhance security and eliminate a potential XSS vulnerability related to adding a file attachment.