SR-C93555 · Issue 431600
BulkMover updated to not treat Numerics as strings
Resolved in Pega Version 8.1.4
When attempting to update Pega platform 8.1.1 to 8.1.3 with Oracle on a Windows machine with German locale using the out-of-place upgrade of the rules schema, the migration failed at the migration step with the error message "ORA-01722: Ungültige Zahl". This was traced to BulkMover failing when trying to convert a string to a Numeric due to the locale using commas as the decimal separator, and has been resolved by updating BulkMover to not treat Numerics as strings.
SR-C94950 · Issue 433176
Rule lock is released after alternate approved operator rejects it
Resolved in Pega Version 8.1.4
When using the rule check-in approval process, if a rule check-in candidate was rejected by an approved operator other than the one who checked it in, the lock on the original rule was not released. This has been corrected so the lock is released after the rule is rejected in the case worker portal.
SR-C95232 · Issue 432328
Removed extranous tick mark on negative numbers in Excel export
Resolved in Pega Version 8.1.4
All negative amounts had an extra ( ‘ ) in front when report definition results were exported to Excel. This was a byproduct of a security update, and has been resolved.
SR-C96297 · Issue 433777
Enhancements added in support of AES/PDC integration
Resolved in Pega Version 8.1.4
The following enhancements have been added in support of AES/PDC integration: - QueueStatistics for Oracle and multi-tenant environments -Postgres statistics are reset after every push (this can be disabled by changing the DSS ResetTableStats) -Enabled Debug statements before all connect-rest/connect-soap calls -Handling for Listener Information issues -Elastic search updates -The connect timeout has been enhanced from 30 sec to 60 sec for all REST connectors. -Data pages can be used for picking the End point URL -Elastic Search Count details can be pushed to PDC
SR-C96362 · Issue 433333
XSS filter added to API form handling
Resolved in Pega Version 8.1.4
An XSS scripting filter has been added for properties that can be changed via API.
SR-C96760 · Issue 433394
Resolved system performance issues for clusters of >15 DF nodes
Resolved in Pega Version 8.1.4
The introduction of distributed event logging used to facilitate data flow troubleshooting in Pega 8.1 created a negative impact on performance for extremely large clusters (>15 DF nodes). To resolve this, the distributed logs have been removed and the system will save events in the database instead.
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().