Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-D25972 · Issue 501483

Handling added for custom error message in post-authentication activity

Resolved in Pega Version 8.4

The error message in post authentication activity was always appearing as 'Login terminated because a post-authentication activity or policy failed' irrespective of the actual message being conditionally set in the activity based on post authentication logic. Investigation showed that the parameter page in the SSO post-authentication activity was not being passed to the 'pzShowAuthPolicyError' activity due to the post-authentication activity executing in authenticated context whereas the HTML fragment executed in the un-authenticated context. In order to support this use, post-authentication activity will set the error message on a predefined property and propagate that to the HTML fragment by appending the error message as a query parameter in the redirect exception URL post-authentication failure.

SR-D25972 · Issue 501482

Handling added for custom error message in post-authentication activity

Resolved in Pega Version 8.2.4

The error message in post authentication activity was always appearing as 'Login terminated because a post-authentication activity or policy failed' irrespective of the actual message being conditionally set in the activity based on post authentication logic. Investigation showed that the parameter page in the SSO post-authentication activity was not being passed to the 'pzShowAuthPolicyError' activity due to the post-authentication activity executing in authenticated context whereas the HTML fragment executed in the un-authenticated context. In order to support this use, post-authentication activity will set the error message on a predefined property and propagate that to the HTML fragment by appending the error message as a query parameter in the redirect exception URL post-authentication failure.

SR-D61860 · Issue 523584

Preflight Optimization styling now handlies right-to-left language packs

Resolved in Pega Version 8.4

When using Preflight Optimization on a generated app with the AR (Arabic) locale, Pages rendered in Right-to-Left (RTL) mode did not have the proper styling or placement for the radio button target and text. The same app rendered correctly when using an empty (default to EN - English) locale. Investigation showed that Preflight Optimization of CSS was failing when using Right-to-Left (RTL) languagebecause the use of preflight bypassed all other CSS processing. To resolve this, the handling of Preflight's CSS Optimization has been updated to handle cases using a Right-to-Left language (ex: Arabic).

SR-D45608 · Issue 519903

Correct service instance name passed for data flow in DSMStatus

Resolved in Pega Version 8.4

When using the Connect-HTTP service "DSMStatus" to provide the node and status information as seen on the various tabs of the Designer Studio > Decisioning > Infrastructure > Services landing page, using DataFlow as the service parameter for the HTTP service method resulted in an empty response when the expectation was to get the information regarding the cluster details of Dataflow node type. This was traced to the service instance name not being parsed correctly when used for Data Flow services, and has been resolved by ensuring the correct service instance name is passed for this use.

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.

INC-188080 · Issue 673783

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.

INC-188143 · Issue 674972

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.

INC-189477 · Issue 674034

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.

INC-200029 · Issue 690167

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.

SR-D18907 · Issue 488900

Property references now supported for label and checkbox captions

Resolved in Pega Version 8.1.6

An enhancement has been added to support the use of a property reference for labels and checkbox captions when using the DX API.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us