SR-C40145 · Issue 402928
Restarting the SVM training analysis checks for existing model request to continue
Resolved in Pega Version 8.1.1
When creating a predictive model there was an issue with completing the SVM training analysis either due to error or browser crash. In previous versions of Designer Studio the session would stay alive and continue to execute, however more recent versions of the decision analysis's portal expected the user to keep the session active in order for the model to complete even though for long-running model training it is not viable to keep a session open for many hours. This was caused by the model generation process being kicked off again when the wizard was relaunched, and has been resolved by adding a check to the relaunch that will look for an existing model generation request and continue with the same request if one is found.
SR-C42849 · Issue 402885
Validation corrected to honor Read-Only designations
Resolved in Pega Version 8.1.1
Validation was happening on Read-Only fields due to pyReadonlyValidation not being honored in all editable cases. This has been corrected.
SR-C46537 · Issue 402866
Code added to format location header for redirect response in IE
Resolved in Pega Version 8.1.1
When using Internet Explorer, authentication was working but the portal did not load. This was traced to IE mandating the presence of a location header in the response: an HTTP 303 "See Other Response" was being returned along with the initial portal HTML payload, but recent modifications to SAML 2.0 to use the PRAuth Servlet were missing this specific redirect case. To resolve this, generic code has been inserted that adds the location header in all redirect cases.
SR-C46793 · Issue 402870
Fixed single logout for Mashup applications and updated logging for pzAuthServiceSelector
Resolved in Pega Version 8.1.1
When the GOC (Global Operations Console) application was added as a mashup application to MSP (My Support Portal), logging off from MSP showed the GOC session in a disconnected state despite them using the same SSO application service. The issue was traced to homeurl not being stored properly in mashup use cases, and has been resolved by getting the property homeurl from pxRequestor page instead of pxThread page. In addition, the pzAuthServiceSelector activity was including an 'infoForced' log message. Although the redirect URI does not contain any confidential information, the 'state' parameter should not be visible in logs. This has been handled by changing oLog.infoForced to oLog.debug().
SR-C48056 · Issue 402881
RRChartDiv tries resize three times before exiting to prevent high CPU usage
Resolved in Pega Version 8.1.1
Very high CPU usage was reported when two or more tabs were open, even when there was not actual work being performed in the app. This was traced to a chart in Team Dashboard that was displayed with "No data to display"; because the toolbar height was always 0, the resize callback was going into an infinite loop. This has been fixed by modifying the logic in pzRRChartDiv to only try the resize three times to get the height of toolbar or slider before exiting.
SR-C49844 · Issue 402924
Added check for external Cassandra cluster to avoid unnecessary DDS pulse error logging
Resolved in Pega Version 8.1.1
After upgrade, DDS pulse errors were filling up the jvm.out logs. This was caused by a check in system_auth keyspace that was redundant for sites running their own Cassandra cluster (external). To fix this, DDS pulse operation will check If the Cassandra cluster is external; if it is, it will not check system_auth keyspace and will Omit DDS pulse operation actions except update logging.
SR-C50221 · Issue 402868
Authentication tools now synchronized to handle multiple simultaneous calls
Resolved in Pega Version 8.1.1
When testing an application that relies on SAMLAuth to create operators and map their data to specific fields it was seen that some users had errant information mapped to their various fields, mostly related to the .pyUserIdentifier and .pyLabel fields. The issue surfaced when multiple user sessions were simultaneously accessing the state of the parameter page, and was traced to an issue where the tools were not synchronized . during the authentication process. To correct this, the tools will be synchronized by storing their state in the parameter page. Context obj will remain constant while the parameter page will be passed in the authentication process.
SR-C50284 · Issue 402874
Top level activity steps are numbered correctly when child steps exist
Resolved in Pega Version 8.1.1
Top level activity steps were showing as being numbered incorrectly when child steps existed, but saving the rule or refreshing the rule corrected the numbering. This was caused by CSS that was added to the rule form harness to increment the step number; while expanding a top level node the reset happened and then the counter initialized the value. To address this, the code has been changed from CSS counter to CSS attr which will use the index attribute of the current row. Additional CSS cleanups were also done to remove IE9 and other browser-specific styling that is no longer needed.
SR-C50381 · Issue 402909
Save Parameters checkbox in Marketing AssociationCategory now disabled by default to resolve exception during campaign
Resolved in Pega Version 8.1.1
An exception was thrown in the logs if an access group had any categories added or deleted while running a campaign in the marketing framework. This was traced to the checkbox "Save parameters with this property for access on reopen" being enabled by default, which ended up adding empty category tags to the Access Group Rule while running. This checkbox in pyAssociationCategory property has now been unchecked by default.
SR-C51952 · Issue 402949
Admin user flag correctly passed from Dual user when falling back to the legacy connection manager
Resolved in Pega Version 8.1.1
When using Dual user configuration with the Base user running Pega, creating a Data Type with a Local Source and then changing the database to CustomerData resulted in an exception citing "insufficient privileges" while trying to save. This was traced to the flag indicating whether the request was coming from an admin user not being passed through ConnectionBrokerAdapter if the system has to fall back to use the legacy connection manager. This was a missed use case which has now been fixed.