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.
INC-182082 · Issue 694613
API added to handle digital signing from proxy layer
Resolved in Pega Version 8.5.6
When an email account was configured with a valid email account and keystore for message signing, it was possible to send emails with valid digital signatures. When the same email was used in case type email instantiation, no digital signatures were included in it. This was due to keyStoreInstance properties being read from the email account top level page when they need to be retrieved from pyEmbedSenderProtocol page when using SMTP. This has been resolved by adding an API to handle the signing logic from the JavaEmailClientProxy class.
INC-164308 · Issue 634409
UseNoCacheHeaders default expiration set to "0"
Resolved in Pega Version 8.6.1
When the prconfig/HTTP/UseNoCacheHeaders/default was set true it used the value "Expires: Thu, 01 Dec 1994 16:00:00 GMT". This has been updated to the more commonly used setting "0".
INC-145802 · Issue 636323
Oracle temporary space explicitly freed after writing LOBs
Resolved in Pega Version 8.6.1
Oracle temporary space used to write the LOB was not freed up after writing records to Log-Service-File when using OJDBC8 or OJDBC10 versions and the table involved had inline BLOB storage such as small blob tables like Log-service-file (2-4kB blobs). This did not occur when using OJDBC7, but investigation with Oracle could not determine why the older version did not have this issue. This issue has been resolved by explicitly freeing the LOB space with a call to free() / freeTemporary() , a utility for LOB objects that was introduced in JDBC 4.
INC-159244 · Issue 627863
Bulk actions check in preserves declare expression legacy setting
Resolved in Pega Version 8.7
When a declare expression was saved in legacy mode with "Whenever used" selected in change tracking, performing a bulk check-in of the rule caused the expression to default to the new forward chaining method. This did not occur when using a direct check-in. Investigation showed this was caused by the check-in page holding a legacy value before the step execution, and has been resolved by adding a pre-save activity before the validation activity that will restore the .pyIsLegacy value from .pyExpressionTypeSelector, if set.
INC-190380 · Issue 678643
CreateVersion rule updated for REST Integration Wizard
Resolved in Pega Version 8.7
When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.
INC-190380 · Issue 678642
CreateVersion rule updated for REST Integration Wizard
Resolved in Pega Version 8.5.6
When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.