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-124938 · Issue 189679
Resolved NPE during Agent execution
Resolved in Pega Version 7.1.8
If the connection pool size for eis/PRAdapter (default 10) was too low for the work environment, all agents in few application nodes saw a NPE and were unable to process any messages un until the node was restarted. As part of resolving this issue, it is recommended to increase the pool as necessary and monitor. The system has been updated such that if an agent is unable to startup due to any reason, that agent will be skipped by MasterForNewAgents and the process will continue. Previously, if any agent failed during startup with an exception, all other agents were skipped as well. The exception will be logged.
SR-124944 · Issue 186362
Handling added for 'agentinfoupdate' map exceptions
Resolved in Pega Version 7.1.8
The function 'agentinfoupdate' updates a distributed map (provided by Hazelcast) for the purpose of an agent landing page. This distributed map was throwing exceptions which did not have proper handling, resulting in the agent scheduler being terminated and thereby stopping agent functionality. The required handling has been added to prevent this situation.
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-124989 · Issue 188104
Added error handling for passivated dashboard tab
Resolved in Pega Version 7.1.8
If the dashboard tab has been ide for 30 minutes or more, clicking on links on the tab generated 'not found' errors and NPE exceptions . This failure was traced to the passivation process, which does not save read-only pages and has been resolved by modifying change tracker logic to not send null values when read-only data page is not present.