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-A14336 · Issue 230881

Resolved NPE when @checkForSubstitute used

Resolved in Pega Version 7.2.1

If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.

SR-A11447 · Issue 243018

Importing an archive no longer fails when using DynaTrace

Resolved in Pega Version 7.2.1

Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.

SR-A12357 · Issue 230904

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.

SR-A12357 · Issue 231872

Corrected error handling logic when using KeepMessages

Resolved in Pega Version 7.2.1

Actions such as PostValue, RunActivity, Run DataTransform, and ShowMenu were clearing the error messages on the client even when the KeepMessages flag was set. There was also a clearing mismatch that left the error messages in the table even though the messages were cleared on the client. This happened when there was a click on a check box that "posts" value or when moving from one tab to another in tabbed layout with "refresh when active" enabled. This was an issue with the error handling logic for those functions and has been corrected.

SR-A14004 · Issue 231765

Flow designer XML fixed when using copy/paste

Resolved in Pega Version 7.2.1

Copy and paste are available in the Flow Designer, but tickets where the End shape was copy/pasted and a new ticket set created for the new End shape resulted in incorrect XML. To correct this, the flowmethodbody function will use pyTicketShapes instead of pyModifierRefs for java generation.

SR-D64566 · Issue 547513

Option added for redirect to SAML IDP on logout

Resolved in Pega Version 8.3.3

An enhancement has been added which provides a check box to choose to redirect to SAML IDP on logout from Pega.

SR-A21835 · Issue 243872

Flow names can now be found when using duplicate search mechanism

Resolved in Pega Version 7.2.1

When using the duplicate search mechanism and trying to resolve a case as duplicate, an error appeared indicating that the flow name could not be found. This was a handling error, and has been fixed.

SR-A18902 · Issue 237052

Updated tab generation for failed 'when'

Resolved in Pega Version 7.2.1

When visible 'whens' were configured on accordion, the content was not properly displayed below the header if the 'when' condition was false. This was caused by an error in the generation of defaultTab based on visible 'when's, and the GenerateTabbedSectionLayout RUF has been updated.

SR-D80539 · Issue 544793

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.3.3

Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.

SR-D88451 · Issue 550847

Testcases are not available for 'access when' rules

Resolved in Pega Version 8.3.3

Attempting to create test cases for access when rules resulted in guardrail warnings about the need to create a test case. Because Test Cases are not available for the Access When rule type as per Pega expected behavior, the guardrail warnings are not valid and have been removed.

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