SR-C35448 · Issue 377278
Disable condition correctly applies to checkboxes without captions
Resolved in Pega Version 8.1
When a disable condition was used on a checkbox in a table grid based on some property, the disable was not triggered even though the properties in the expression changed. This happened when a checkbox was configured without any caption: if it became disabled, the disable attribute was not getting appended to the hidden input fields. If the checkbox was configured with a caption, the disable worked as expected. In order to ensure the disable condition works consistently, the code has been modified so that the generation of checkboxes in nontemplate mode will appropriately append 'disabled' to the hidden input in the checkbox.
SR-C35518 · Issue 377458
Fixed add/delete rows issue for RDL inside master
Resolved in Pega Version 8.1
Attempting to add/delete rows in an RDL inside the master details was not working, and it was not possible to dismiss the master details after the attempt. This was due to the RDL being inside the masterdetails DIV of another RDL, and handling has been added for this scenario.
SR-C35518 · Issue 377478
Class and context refinements added for Master details flow action
Resolved in Pega Version 8.1
The Master details Flow Action was not rendered in the Repeating Dynamic layout when a row was clicked, and the error "FlowAction not available in cache" appeared. In the same RDL, opening Master details did not fetch the context. This issue was traced to the pxObjClass of the client cache page that was being added in the SolutionsUsed page list not being set. In offline, the data transform does not set the pxObjClass by itself. Additions were also made to ensure the flow action is being packaged in the correct context.
SR-C35530 · Issue 376970
OperatorID page now created at system level
Resolved in Pega Version 8.1
The Thread/Tab was missing the 'OperatorID' page when logged in using PRAuth. This was caused by the OperatorID page being created at the thread level instead of at the requestor level. To correct this, OperatorID has been modified to be created at system level.
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