SR-C35569 · Issue 387727
Mobile login error message clarified for disabled operator
Resolved in Pega Version 8.1
Login on mobile failed with a "Failed to authenticate" message for disabled operators. This was confusing. The authentication of mobile applications employs "SnapStart", but this does not handle authentication failures due to "disabled operator" - at least not in a manner that enables handling and producing custom authentication messages that will inform the device user as to the specifics of the failed login. In order to remove confusion, handling has been added to ensure the proper http error code and message is returned from the server after a mobile login request from a disabled operator.
SR-C35827 · Issue 375732
FlowAction, Rule-File-Binary, and data transform using pre-loading so specification changes are maintained
Resolved in Pega Version 8.1
After adding specifications to a flow action from the specifications tab, refreshing the flow action rule resulted in the added specifications not being shown in the UI. If the rule was saved, the specification updates were lost. To resolve this, the specifications tab is now defer-loaded with the pre-loading activity pzGetAssociatedSpecifications used to load the specification links of the rule.The updated ruleforms using pre-loading are FlowAction, Rule-File-Binary, and data transform.
SR-C35969 · Issue 375783
Documentation updated to clarify how to use Tracer on Service Rules
Resolved in Pega Version 8.1
Due to an error in the documentation where the table of contents was pointing to an older version of the file, the information about configuring the Tracer to examine Service Rules was not clear. The document reference has been updated to point to the correct version which reads: Service rule tracing is only enabled in environments where the trace/cluster/ServiceRuleWatchMaxProductionLevel Dynamic System Settings is greater than or equal to the production level. By default, trace/cluster/ServiceRuleWatchMaxProductionLevel is set to 4, which means that the ability to trace service rules would not work in a production level 5 environment until trace/cluster/ServiceRuleWatchMaxProductionLevel is increased to 5.
SR-C35978 · Issue 375707
Non-standard JVM heap size argument removed and replaced with more generic max-mem
Resolved in Pega Version 8.1
The IBM JVM was not honoring the MaxHeapSize property, causing installs/upgrade on Java 8 with the IBM JVM to fail unless an alternate max memory was provided. To resolve this, the usage of a non-standard heap size argument has been removed and replaced with a more generic max-mem present within the master for all JVMs to take advantage of. At the same time, the default memory and space requirements have been reduced as prpcServiceUtils now needs less than it previously did.
SR-C35993 · Issue 385277
JAWS reads error messages only once
Resolved in Pega Version 8.1
Error messages were being read twice with JAWS due to the title attribute with the error message as value being added to the dynamic error div, resulting in JAWS reading both the title and the value. To fix this, the title attribute has been removed from the span element of the dynamic error div for a Dynamic-Layout so error messages are read only once for the field level errors.
SR-C36020 · Issue 376776
New px APIs added to support File Listener in Data Import Wizard
Resolved in Pega Version 8.1
In order to provide px API for Data Import Wizard to Support File Listener, the following parameters have been added:pzGetSourceHeaderList- to support delimiter pzImportRecords - to keep import file after import pzImportRecordsWrapper - to import synchronously pyKeepFileAfterImport - new property pyPerformImportSynchronously - new property
SR-C3603 · Issue 351594
Expand/collapse checkboxes read by JAWS
Resolved in Pega Version 8.1
JAWS now reads checkboxes used to expand and collapse rows.
SR-C36057 · Issue 387665
Required field error message appears under multiple controls when using multiple multiselect
Resolved in Pega Version 8.1
Error messages for multiple controls in a repeating dynamic layout displayed only for first control instead of the expected behavior of an error message displayed under all controls. The required error messages were not showing up when multiple multiselectlist control was being used due to a missing name attribute for multiselectlist control, and this has been added to correct the problem.
SR-C36091 · Issue 377696
Stuck run detection improved to give information and stop bad jobs
Resolved in Pega Version 8.1
When a run is in NEW state, attempting to trigger it caused the run to move into the INITIALIZING state and after some time back to the NEW state. Once that happens for the first time, it would continuously happen to the same run and force the creation of a new run. Investigation showed that in very specific situations a data flow run might take too long to initialize. That caused the system mechanism that detects runs stuck in a transitioning state to kick in and move it back to NEW state. Later that run would actually be initialized but its status would no longer be reported correctly, giving the impression that the run was always going from NEW->INTIALIZING->NEW. To prevent confusion, code has been to the stuck run detection that will add troubleshooting information and stop that run if it's in a state that was was not anticipated.
SR-C36306 · Issue 389694
Handling added for double-click on previous step in TreeNavigation7
Resolved in Pega Version 8.1
After configuring a screen flow navigation that utilized the TreeNavigation7 Section rule, double clicking on a previous step generated the error "Modal Dialog: Ajax Call Failure!".On double click, the onclick on <li> tag was executed and throwing the callback failure alert which was not expected, causing the system to skip the execution of the "nodeExpandCollapse" function in TreeNavigation section. This has been fixed.