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-120592 · Issue 183002
Corrected circumstanced list views called from within a section
Resolved in Pega Version 7.1.8
A circumstanced List view based on a property was not being properly called from within a section. Instead of passing the primary page which has the circumstance property details for the ruleset work flow, a new page was always created. Since the new page did not have the circumstance property details, the circumstanced list view was skipped. To correct this, the Rule-Obj-ListView.DisplayView rule has been modified to always pass the primary page instead of creating a new one.
SR-120673 · Issue 185098
Refresh behavior updated for sections with list views
Resolved in Pega Version 7.1.8
After configuring a refresh section on a control with a list view in the section, the refresh was happening only on the first iteration. This was an issue with loading "pega_tools_evaldomscripts.js" multiple time and the HTML has been updated to ensure the "ListViewHeader" rule uses the tag instead of tag.
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.
SR-121588 · Issue 181232
Updated PDF conversion for latest versions of Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.
SR-121588 · Issue 176641
Updated PDF conversion for latest versions of Microsoft Internet Explorer
Resolved in Pega Version 7.1.8
When using the Out-Of-The-Box Flow Action called "ConvertAttachmentToPDF", no error was generated at runtime but the new file attached to the case was not correctly converted. The root cause was the HTML rule called "ActionConvertAttachmentToPDF" which contained JavaScript code that was not fully compatible with the newest releases of the Microsoft Internet Explorer browser. This has been changed.