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-122637 · Issue 183016
MaxFileLength property added to avoid truncating attachment names
Resolved in Pega Version 7.1.8
While adding the attachments to the case using drag and drop functionality, the file name and file description were being truncated. However, a new property named "pyMaxFileLength" is now available as an override in pyDefault Model to set a different name limit. If this property is not set, it will take the default value of 60 and proceed. Also for UI error messages, pyNote property in Data-WorkAttach-File and Embed-DragDropFile in the application ruleset must have the max length limitation removed from there or the MaxFileLength will be overridden by that setting.
SR-122641 · Issue 182813
Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.8
Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.
SR-122641 · Issue 181600
Edit filters repaired for Report Definition text fields with Microsoft Internet Explorer 9 & Microsoft Internet Explorer 11
Resolved in Pega Version 7.1.8
Using Microsoft Internet Explorer 9 and Microsoft Internet Explorer 11, all of the Report Definition text Fields (including auto complete) in the Edit Filters were disabled and would not accept input when trying to select the property using the mouse. To resolve this, the UI functions have been modified to handle range text native functions for these browsers.
SR-122689 · Issue 183471
Corrected display issue for tabbed Summary View charts
Resolved in Pega Version 7.1.8
When using Summary View charts in a Tabbed Section, the chart loaded correctly on the first viewing. However, on moving to a different tab and coming back to the same tab again, the Summary View was getting distorted (elongated). There was a local workaround on using RefreshWhenActive, but this has been resolved.
SR-122689 · Issue 183713
Corrected display issue for tabbed Summary View charts
Resolved in Pega Version 7.1.8
When using Summary View charts in a Tabbed Section, the chart loaded correctly on the first viewing. However, on moving to a different tab and coming back to the same tab again, the Summary View was getting distorted (elongated). There was a local workaround on using RefreshWhenActive, but this has been resolved.
SR-122757 · Issue 185151
Chinese filename issue with Microsoft Internet Explorer resolved
Resolved in Pega Version 7.1.8
When using the Chinese version of the Microsoft Internet Explorer browser and the out-of-the-box attachment gadget to attach files, dragging and dropping a file with Chinese characters in the file name caused the name to become corrupted. This issue was due to the encoding method, and has been resolved by removed the encoding for the filename.
SR-122761 · Issue 188488
Tuned logic for propagating shape flow actions
Resolved in Pega Version 7.1.8
When a work flow has moved from an assignment shape to an assignment service shape, the other actions menu was showing the flow action from the previous assignment. Work-.Connect activity invoked populateFlowActions function to populate the assignment local action. By the time this was invoked, the pxFlow() was not updated with the correct assignment details and the old assignments actions were being populated. This has been fixed by tuning the logic of invoking populateFlowActions.
SR-122809 · Issue 182677
Application Wizard updated to use long-form function name
Resolved in Pega Version 7.1.8
When using the Application Wizard in some environments, clicking 'Preview' or 'Create' on the Data Objects screen caused a refresh and no summary of the created rules was generated. This issue was traced to an error in the library/function rule resolution where the short-form reference to a function was finding more than one suitable rule resolution candidate if there was more than one version of a ruleset function with the same formal parameters and the function was called using the short form of the function name. In this particular scenario the PageListContains function was causing a problem as this function exists in both the PegaSurvey framework and the Pega-AppDefinition ruleset. There was a workaround of doing a private checkout of the CopyFrameworkClassGroup activity and changing the short function rule reference to the long function rule reference (specifying ruleset and library, but the Wizard has been updated to use long-form function name to prevent this issue.
SR-122839 · Issue 185954
Audit entries properly suppressed
Resolved in Pega Version 7.1.8
Audit entries were being added to the history even after suppressing the same in the DT "FilterHistory" of the respective interaction class. When the "RemoveAssignmentByTicket" function called the activity "AddWorkHistory", the parameter workPage was not being sent. Because the system skipped the call to the decision tree, it was returned as 'true' each time. To resolve this, the system now passes "WorkObjectPageName" to ensure proper evaluation.