SR-131611 · Issue 201761
Currency field 'save draft' function updated
Resolved in Pega Version 7.1.8
Save Draft button when pressed caused a screen error for currency fields, identifying that they were not the proper "decimal value", though the actual flow worked as expected. This was caused by the Save Draft function passing the value in string format instead of decimal, and the API has bene updated to update the value to a number.
SR-118755 · Issue 177568
Enhanced logging for access group decisions
Resolved in Pega Version 7.1.8
In order to facilitate troubleshooting, logging has been added to track how the Core Engine decides what Access Group to assign to the running Agent. This lists the name/ruleset/ruleset version of the Data-Agent-Queue record being utilized, the Access Group specified by it, and any further steps that determine what AG gets used. If the DAQ gets rebuilt, it will show how it gets rebuilt from the Rule-Agent-Queue record.
SR-126361 · Issue 189663
Case Designer modified to counter Microsoft Internet Explorer 8 UI override
Resolved in Pega Version 7.1.8
While working in the Stages & Processes tab using the Microsoft Internet Explorer 8 browser, it was not possible to view or modify the step and details and some buttons were not working. This was due to the display of auto complete being overridden with the browser's UI styles z-index. To create the proper behavior, the Case-Designer-styles CSS has been modified to add a Pega-specific z-index for process entry in Microsoft Internet Explorer 8.
SR-129312 · Issue 198553
Corrected HTML display of characters in reply emails
Resolved in Pega Version 7.1.8
HTML characters were appear in the email body and subject for outbound reply messages. For example, if subject is test, the reply email would display the subject as RE: test<%gt; An HTML reply to an HTML email did not contain these entities/artifacts. Reply emails can now be configured to use HTML format, and the 'HTML' option has been added to the Message Type drop-down on the Response tab of Service Email rule.
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-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-122619 · Issue 188285
Ensured Excel reports contain fresh data
Resolved in Pega Version 7.1.8
A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.
SR-122982 · Issue 186898
Ensured Excel reports contain fresh data
Resolved in Pega Version 7.1.8
A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.
SR-122982 · Issue 185153
Ensured Excel reports contain fresh data
Resolved in Pega Version 7.1.8
A sporadic issue was found when running multiple reports and exporting them to Excel where new reports sometimes contained data from previously exported results. This was found to be an issue with stale data being left on the TmpExportResultsPageOrig because this page was not listed in the Page-Remove at the end of the RDExportWrapper activity. This has been corrected.
SR-124168 · Issue 186995
Application document support added for Word 2007
Resolved in Pega Version 7.1.8
When an Application Document was generated, Word 2007 launched a Microsoft Visual Basic window pop up with the message "Compile error in hidden module: clsPRSessionMgr". The root cause of this problem was a defect in the "Rule-File-Binary" rule WordMacroManagerDot.biw" that supports the 64-bit version of MS Word. This has been fixed.