INC-218001 · Issue 719922
Error text revised for parameterized data page used for token generation
Resolved in Pega Version 8.6.5
While trying to add a claim in the header of a Token Generation Profile instance, selecting Map From as "Clipboard" and trying to give any DataPage(parameterized) as the source property failed to be saved and the error "JWS Alias— Please provide correct algorithm key with correct key length." appeared. Changing the "Map From" to a Constant and giving a dummy value worked as expected. Tracer showed the error "declare page parameters not supported by PropertyReference", indicating the actual issue: at this time, the Token profile does not support using a parameterized data page. This has been addressed by ensuring an appropriate error message is shown on save of the token profile rule form when a parameterized data page reference is configured. The error will now read "The reference D_pzPreferenceStore[PreferenceOperatorID:"[email protected]"].pxObjClass is not valid. Reason: Parameterized data page reference is not supported." Support for a parameterized data page used with Map From will be taken as an enhancement for a future release.
INC-218340 · Issue 714663
Override added to delete records for a stream dataset after processing
Resolved in Pega Version 8.6.5
Kafka data was accumulating for a Stream data set due to huge volume of inbound calls. This has been resolved by adding support to override pyDeletedProcessed through a DASS in order to remove the records for a particular stream dataset (topic) as soon as they are processed by Pega.
INC-218909 · Issue 715282
Override added to delete records for a stream dataset after processing
Resolved in Pega Version 8.6.5
Kafka data was accumulating for a Stream data set due to huge volume of inbound calls. This has been resolved by adding support to override pyDeletedProcessed through a DASS in order to remove the records for a particular stream dataset (topic) as soon as they are processed by Pega.
INC-219566 · Issue 721290
Handling updated for CSRF in queue processor trace
Resolved in Pega Version 8.6.5
The field level audit on properties was intermittently not being shown on the Audit history table for the first time for some users. This has been resolved by modifying the queue processor trace to better handle CSRF tokens.
INC-225519 · Issue 724398
Improved handling for thread resolution issues
Resolved in Pega Version 8.6.5
Queue Processor/Dataflow was moving to STOPPED state due to failed records in its execution. Investigation showed there was a minor logic issue in the queue processor activity which allowed the Page-Remove step to be called even before the pages were actually created, and this has been resolved by improving the recovery from a cleared ThreadContainer which might cause thread resolution issues.
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-A9147 · Issue 220746
Documentation updated for command-line BIX extractions
Resolved in Pega Version 7.2
The documentation for "Using a stand-alone command-line BIX extract process" has been updated to refer to the BIX 7.1 User's Guide regarding configuring the necessary database connection properties set (prbootstrap, prconfig, etc.).
SR-A5258 · Issue 213386
Documentation updated to reflect change to read-only getProperty pages
Resolved in Pega Version 7.2
In recent versions of the system, getProperty() was modified to support the creation of a property on a read-only page. However, even though the property has been created, it is not possible to set its value. This was not clearly indicated in the documentation, and read-only exceptions were being generated when putString() or setValue() attempted to give a value for the property on a read-only page. The documentation has been updated to clarify this use case.
SR-A6768 · Issue 215093
JDBC connection URL documentation updated for JBOSS installation
Resolved in Pega Version 7.2
An error was found in the JBOSS installation document: the JDBC connection URL defined inside the standalone-full.xml should not have forward slash (/) before the database name, i.e. the format below is incorrect: jdbc:oracle:thin:@//localhost:1521/dbName Instead, the forward slash before data name should be changed to a colon (:), for example: jdbc:oracle:thin:@//localhost:1521:dbName This documentation issue has been resolved by adding a section clarifying the necessary connection information and the method for creating a connection string, along with updating all connection-url steps to either include this information or a pointer to the new section.