INC-189259 · Issue 692033
Big Decimal used while converting List to Page
Resolved in Pega Version 8.5.6
Previous work done to handle precision numbers in the JSON response that were being rounded or truncated when parsed for the DataSource page has been updated to also handle the case of mapping a list to a page.
INC-182959 · Issue 668735
SQL queries modified to use qualified table references
Resolved in Pega Version 8.5.6
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-185760 · Issue 668740
SQL queries modified to use qualified table references
Resolved in Pega Version 8.5.6
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-191779 · Issue 677519
Updated use of declarative processing during performance testing
Resolved in Pega Version 8.5.6
After update, the performance test script build was not working. A stack overflow indicated an issue with the load activity for the D_InteractionHistory data page referenced by expressions/properties. This has been resolved by disabling declarative processing during the estimation of data size.
INC-199749 · Issue 695536
Updated use of declarative processing during performance testing
Resolved in Pega Version 8.5.6
After update, the performance test script build was not working. A stack overflow indicated an issue with the load activity for the D_InteractionHistory data page referenced by expressions/properties. This has been resolved by disabling declarative processing during the estimation of data size.
INC-177737 · Issue 663140
Authentication requirement updated for CallConnector
Resolved in Pega Version 8.6.1
After update, invoking a REST API call during SSO login which eventually called pxCallConnector (Final Activity) in @baseclass Pega-RulesEngine failed at the CallConnector step. This was caused by a change in recent Pega versions which enabled authentication for this activity, and has been resolved by marking the activity as internal and disabling the authentication requirement.
INC-187553 · Issue 675428
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.5.6
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.
INC-188080 · Issue 673782
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.5.6
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.
INC-188143 · Issue 674971
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.5.6
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.
INC-200029 · Issue 690168
Service Email handling updated for MSGraph "From" address
Resolved in Pega Version 8.5.6
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.