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-128961 · Issue 208349
Added check for naming conflicts when upgrading Oracle
Resolved in Pega Version 7.2
When attempting to upgrade a single schema on Oracle database, running the generateddl script failed with a NullPointerException. This was caused by database tables which had a column name called 'SYS_ID' as part of the primary key. Since Oracle uses system-generated names beginning with "SYS_" for implicitly generated schema objects and subobjects, Oracle discourages the use of this prefix in the names explicitly provided to the schema objects and subobjects in order to avoid possible conflicts in name resolution. To resolve this, a tester has been added to the system to check for this naming use and issue a warning.
SR-A2239 · Issue 205811
Documentation added on adding Tomcat-on-Oracle Rules resource
Resolved in Pega Version 7.2
The Tomcat-on-Oracle installation guides for Pega ML7 and ML8 did not contain instructions for adding a for jdbc/AdminPegaRULES. As such if the installer prepared a two-user (Base + Admin) setup in the database and allocated the Base user to jdbc/PegaRULES, the Pega platform was unable to run DDL to create new tables for new work types and new data types, as the installer has not configured the additional datasource to use the Admin user. The documentation has been updated to add the necessary step between Steps 1 and 2 of the "Create a JDBC Datasource" chapter (page 41 from the ML7 installation guide).
SR-A4171 · Issue 213701
Added keyword support for <current>
Resolved in Pega Version 7.2
Variations between system versions were causing a decision table containing some regexp functions to pass or fail validation depending on the version. To remedy this, support has been added for using the regular expression function as a keyword to ensure valid tables are properly handled.
SR-A5565 · Issue 217722
Added missing filename encoding for drag and drop
Resolved in Pega Version 7.2
An error was being generated when opening an attached file with "$" in the filename. This was due to missing encoding for cases attached with drag and drop, and has been corrected.