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.

INC-168837 · Issue 646973

CSRF token updated for use with OKTA login

Resolved in Pega Version 8.5.4

An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.

INC-168837 · Issue 646974

CSRF token updated for use with OKTA login

Resolved in Pega Version 8.6.1

An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.

INC-168837 · Issue 646972

CSRF token updated for use with OKTA login

Resolved in Pega Version 8.7

An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.

SR-B84336 · Issue 332037

onOnlineDetected use matches documentation

Resolved in Pega Version 7.4

iOS11 was failing the first login attempt. Documentation for the addListener method in pzPega_offline_datasync rule lists 'onOnlineDetected' as optional, but when the listener was added without onOnlineDetected the console.error occurred. This was originally a documentation error where the rule was incorrectly given as optional even though the event handlers always assumed onOnlineDetected was defined, but as there are reasons to support this use the system has been updated this so onOnlineDetected is truly optional now.

INC-143036 · Issue 599192

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.4.4

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-143036 · Issue 599190

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.5.3

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-143036 · Issue 599189

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.6

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-143036 · Issue 599191

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.3.6

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-196414 · Issue 684238

OAuth token refreshed when revoked on source

Resolved in Pega Version 8.7

When an OAuth token was used to authorize the APIs in the system, revoking the token at the source, i.e. from the Service side, did not automatically refresh the token and a logoff/logon was required before a fresh token was generated. This has been resolved by adding an update to explicitly purge revoked tokens.

INC-196414 · Issue 684239

OAuth token refreshed when revoked on source

Resolved in Pega Version 8.6.3

When an OAuth token was used to authorize the APIs in the system, revoking the token at the source, i.e. from the Service side, did not automatically refresh the token and a logoff/logon was required before a fresh token was generated. This has been resolved by adding an update to explicitly purge revoked tokens.

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