INC-183728 · Issue 665133
Oracle handling updated for primary key in upgrade DDL
Resolved in Pega Version 8.7
Previously, when a primary key of a table was created Oracle would automatically create a unique index with the same name as the primary key. However, with the introduction of Oracle 19, an optimization was added which will not do that if there is another unique index on the table which contains the column(s) of the primary key. This difference can cause updates to fail with the error "cannot drop index used for enforcement of unique/primary key". This has been resolved by updating the handling for primary key constraint and the corresponding index name.
INC-184427 · Issue 671861
Cross-site scripting security updated for rules
Resolved in Pega Version 8.7
Additional cross-site scripting protections have been added to Pega-RULES.
INC-184668 · Issue 665958
Check added for null mColumn values while estimating size
Resolved in Pega Version 8.7
A null pointer error indicating an issue with AbstractDataPageHandler.estimateDataSize was traced to missing handling for null values in mColumns while calculating size. This has been resolved with the addition of a null check.
INC-184699 · Issue 674683
Agent name validation added
Resolved in Pega Version 8.7
After creating an agent name that contained "/", the Agent API returned "Resource not found". This was due to the "/" character's incompatibility with the REST API, and has been resolved by adding agent name validation (pzvalidateagentname) to embed-rule-futurequeue to prevent the inclusion of "/" in an Agent name.
INC-185266 · Issue 676581
Index table correctly populates after migration
Resolved in Pega Version 8.7
After creating a product file with work instances, only some records were populating in the index-workpartyuri class through index rule. Investigation showed that if the IDs specified for the Work Range started with the same digits as were seen after the case prefix (e.g. W-1, W-1000, or W-22, W-2201) then only the indexes for cases that start with W-1 or W-22 were included in the export. This was traced to a step in AddPartyIndexWhenCondition where the EstimatedWorkPrefix local variable was calculated: the java step extracted anything that was the same from the start of the To and From range without taking into account the possibility that some digit characters after the "-" could be the same. To improve the accuracy of the prefix estimation, "-\d" will be used to make an educated guess.
INC-185614 · Issue 684847
Resolved access errors for external database class mapping generation
Resolved in Pega Version 8.7
After update, opening the Database Class Mappings landing page displayed all database tables linked to customer data schema as an exclamation mark with the error tooltip : "width = device-width". In addition, the error "Class: com.pega.pegarules.pub.PRRuntimeException Message: Error: You lack access required to execute Pega-Landing-DataModel-DBClassMappings.pzLPCheckDBMapRowCount" was logged. The application behaved normally despite the exceptions. This was traced to the the warning tool tip not loading correctly for the Exposed/Mapped column in Configure-Data Model->Class and properties->Database class mappings->select class category(Data)->for CustomerData, and has been resolved by updating the security settings to re-allow invocation from browser, require authentication, and set the correct privileges.
INC-185760 · Issue 668742
SQL queries modified to use qualified table references
Resolved in Pega Version 8.7
Portal launch in the development environment was taking an excessive amount of time, as were some standard reports. The PurgeAssemplyDatabaseCache agent activity also generated an error regarding "(internal.cache.RAPurge) ERROR - Purge, unexpected error in removeOldAppCentricCacheData". These issues were traced to SQL queries that contained pr_sys_app_hierarchy_flat without a schema qualifier, and have been resolved by changing to class qualified table references.
INC-186094 · Issue 683693
MQ jar handling updated to resolve initialization error
Resolved in Pega Version 8.7
After update, errors were seen indicating a NoClassDefFoundError relating to initializing com.ibm.mq.jms.MQQueue. This was traced to a difference in the handling of imported MQ jars, and has been resolved.
INC-186634 · Issue 672151
Expanded debug logging for requestors
Resolved in Pega Version 8.7
In order to assist with diagnosing issues, debug loggers have been added for requestor activation and validation.
INC-187553 · Issue 675429
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.7
While creating cases via email listener, the "From" address was not shown when using MSGraph. This was an issue with extracting the display name when MSGraph is used, and has been resolved by adding double quotes to display the name unconditionally.