SR-124868 · Issue 187837
Localization Wizard expanded to collect all applicable rulesets
Resolved in Pega Version 7.1.8
A large inconsistency was seen in the number of Strings Exported after selecting all Application rulesets and proceeding with the localization wizard depending on whether or not the top app RS were selected. The pyWorkPage.pyRuleSets page list is intended to be a list of ruleset names on which localization wizard to be executed, but only the selected first application ruleset was added. To correct this, the precondition in "GenerateRulesetList" activity has been updated to include all rulesets.
SR-124873 · Issue 187569
Updated accessibility for operator profile checkbox
Resolved in Pega Version 7.1.8
Focus was not moving to the checkbox "Operator is available to receive work" in the operator profile form when using tab control in accessibility mode. To enable this, the logic of inclusion of accessibility styles in the WorkformStyles HTML fragment has been enhanced.
SR-124875 · Issue 186361
Event firing fixed for blank Start and End values
Resolved in Pega Version 7.1.8
As a result of changes made to better handle cases when distributed search is enabled and "Work indexing" is enabled, events were no longer firing for existing and new events where there where Start and End dates were not set. This has been fixed.
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-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.