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-120596 · Issue 183801
Resolved mapping issue for SOAP-connect with multirefs
Resolved in Pega Version 7.1.8
After upgrade, mapping the soap-connect response to page in activity was not working as expected. This was an issue with a Parse-XML rule, and has been corrected with added support for multirefs and SOAP arrays with multirefs.
SR-120701 · Issue 179702
Email listener error handling improved
Resolved in Pega Version 7.1.8
When an email arrived with a zero byte attachment, the email listener was failing to generate a work object. An error was seen in the log, and the listener marked the email as seen even though no WO was created. This has been fixed by suppressing the IOException that arises while processing a zero-size INLINE attachment, allowing the rest of the email message to be processed. An exception will be logged, but the attachment that caused the issue will not be added to the work object.
SR-120730 · Issue 178759
Fixed FCM access for remote work item attachments
Resolved in Pega Version 7.1.8
When using FCM to access remote work item via find by ID, attempting to open the history / attachments popup generated a green tick (success but no content) on the first attempt and the error "Failed to find a 'RULE-OBJ-ACTIVITY' with the name 'HISTORYANDATTACHMENTS' that applies to '@baseclass'" on subsequent attempts. "the operation completed successfully, but returned no content". The issue only happened when first logging on and searching for a work item and did not occur if the tab was closed and the same work item reopened. This was caused by the prgateway sending an HTTP request where the Pega thread name in the URL was stripped of a slash, triggering the creation of a brand new Pega thread where expected pages were missing. To resolve this, the code has been updated to correctly maintain slashes and add them if necessary.
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-121016 · Issue 179993
JMS handling enhanced for complex custom environments
Resolved in Pega Version 7.1.8
When a JMS message is created, a temporary JMS response queue is also created on the fly. The JMS response queue has a timeout parameter associated. After PRPC has consumed a message from the destination, it retrieves the response parameters from the message header and posts a JMS message to the temporary response queue to complete the cycle. In some complex custom environments, PRPC was not able to send a response message before the response queue timed out and an error was generated. In order to handle these situations, the JMS Listener has been modified to always close MDB response connection before continuing.
SR-121104 · Issue 184148
Enhanced security for SQL exceptions errors
Resolved in Pega Version 7.1.8
In order to avoid a potential security vulnerability, the error messages generated by database exceptions have been made consistent for DB2 and Oracle and do not display SQL information in the log.
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.