SR-124877 · Issue 186909
Fix inserted for CaseWorker portals using Microsoft Internet Explorer 8
Resolved in Pega Version 7.1.8
CaseWorker portal links to open and interact with cases were not working in the Microsoft Internet Explorer 8 browser. This was caused by the method used to get the dynamic container not being supported by Microsoft Internet Explorer 8, and has been resolved by changing the querySelector to get the proper class names.
SR-124882 · Issue 186524
Cookies only generated if IAC enabled
Resolved in Pega Version 7.1.8
IAC cookies were being generated in environments where IAC was not deployed, causing the application to present the error "Browser cookies must be enabled for PRPC Internet Application Composer to function." This problem only occurred with the Google Chrome and Firefox browsers. To correct this, the system has been updated to bypass cookie generation if IAC is not in use, adding a condition to bypass the cookie detection logic in PegaCompositeGadgetMgr.js if pega.web.config.encrypt is set to false.
SR-124910 · Issue 192169
Parse XML handling added for blank page list data
Resolved in Pega Version 7.1.8
In some very specific data scenarios, the auto-generated multiple parse XML routine for rules off of a WSDL import failed in a manner that was silent to the application but was visible in the logs. This happened with nested page list parse XML configurations with an apply rule where the data of page list of first page was empty, causing the mappings of the page list in other pages to be skipped even though the data was there. If the page list data of the first page was not empty, there was no error. To resolve this, code has been added to check the resolved path in the XML content instead of the unresolved.
SR-124910 · Issue 192293
Parse XML handling added for blank page list data
Resolved in Pega Version 7.1.8
In some very specific data scenarios, the auto-generated multiple parse XML routine for rules off of a WSDL import failed in a manner that was silent to the application but was visible in the logs. This happened with nested page list parse XML configurations with an apply rule where the data of page list of first page was empty, causing the mappings of the page list in other pages to be skipped even though the data was there. If the page list data of the first page was not empty, there was no error. To resolve this, code has been added to check the resolved path in the XML content instead of the unresolved.
SR-124919 · Issue 188505
Handling added for invalid event object in Dynamic Select
Resolved in Pega Version 7.1.8
When there are two DynamicSelect controls in a section, the value selected in the first causes the list of choices in the second to be filtered. If there is an invalid but non-null event object, selecting a value in the first dropdown generated the JavaScript error "Member not found". This has been resolved by adding a condition in the reload API to handle the non-null invalid object.
SR-124930 · Issue 186906
Inserted validation for reversed availability dates
Resolved in Pega Version 7.1.8
In Developer portal-> administrator -> profile -> availability , entering UnavailableFrom and To dates for the schedule where the From date is in the future of the To date was submittable without triggering error messages. The root cause of the issue was a skipped activity step. The validation step is looped only for specific embedded pages, and was not being called in this case. This datetime error has been corrected.
SR-124952 · Issue 189563
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-124952 · Issue 189565
Resolved HTMLtoPDF font load error
Resolved in Pega Version 7.1.8
When using a Fonts directory during HTMLToPDF conversion, the StaticContent folder resolved to an incorrect properties file and generated an error that appeared to indicate the fonts had not correctly loaded even when they had indeed loaded. The error was traced to the function used to open the Static Content folder with the direct file handle, and this has been updated to resolve correctly.
SR-124971 · Issue 188628
Button type filter added to Report Browser
Resolved in Pega Version 7.1.8
After navigating to the Report Browser and then back to another tab, clicking on any input field and clicking enter caused the columns filtering pop-up to appear even if the user was not on the Report Browser tab. This issue only occurred with the FireFox browser due to FireFox treating elements as the 'default action' of the form and using them as submits, causing a press of the enter key to fire off the onclick event for those buttons. In order to correct this, the type='button' attribute has been added to the filter
SR-125028 · Issue 187645
List View filter corrected
Resolved in Pega Version 7.1.8
When enable filtering is turned on in the display fields, the ListView filter tab failed to retrieve the record. This was traced to the Keycode 32(space bar) being conditionally added in pega_ui_listview, and has been corrected.