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-A19986 · Issue 244104

getAppHashForApplication API updated

Resolved in Pega Version 7.2.1

When logged in from an end user portal, editing a decision table and clicking on the gear icon to add a function would show the Function's headers (Example, Activity, string, etc.), but the functions list would not be loaded. This was traced to a timeout resulting from having numerous functions running on the portal combined with a configuration that returned an unowned AppHash when calling a ruleset from the production layer rather than the application layer, and has been resolved by adding logic to write out the AppHash when the appInfo is created from opening the application.

SR-A20067 · Issue 243517

Fixed thread locking for authenticated SOAP

Resolved in Pega Version 7.2.1

Exception messages were being logged when the authenticated inbound SOAP service was called from a client application due to two threads simultaneously trying to load a data page at node level. The locking has been corrected to resolve this.

SR-A20162 · Issue 238035

Added validation to check for Agents run every *blank* days

Resolved in Pega Version 7.2.1

When configuring a Rule-Agent-Queue instance, the Pattern can be specified as "Recurring", which opens an "Advanced" button. The modal window that opens for the Advanced button allows specifying the recurring pattern, and it's possible to specify that an agent executes Daily, Every X days. If the Every X days option was selected, it allowed leaving the number field blank. However, doing this generated an invalid delay time error after the agent ran. To avoid this, validation will be performed on this field to ensure that a value is entered. Additional changes were also made to not allow a blank value in the field, numberOfMonths, numberOfDays, and numberOfYears as well.

SR-A20287 · Issue 235728

Corrected refresh results for filtered propositions

Resolved in Pega Version 7.2.1

A refresh error related to filtering performed with the propositions using a certain business issue & group in PegaMarketing caused a list refresh that automatically brought back all the propositions after selecting one. This has been fixed.

SR-A20450 · Issue 239606

Locale validation step added to match accepted formats

Resolved in Pega Version 7.2.1

It was noticed that if a locale was specified on the Operator rule using a hyphen rather than an underscore (such as en-GB vs en_GB), the operator defaulted to the US locale for date and time formats and no check or error would be generated. To ensure expected behavior, a step has been added to validate the format of locale to match either "blank", xx, or xx_XX.

SR-A20581 · Issue 242760

Added checks to pagelist indexes for processing and recovery

Resolved in Pega Version 7.2.1

Sporadically, work objects saved to the database generated the error "The Flow Action pre-processing activity pyPopulateCaseContentsWrapper failed: cannot be null or blank. page: . Details: Invalid value for aReference passed to com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getProperty(String, char)" This happened when changes to Indexes in pagelists were getting overridden with another pagelist index, causing data to be lost on database save. A check has now been added to identify whether the entry has been processed in the current encode, and a hard check has been inserted to prevent data loss of page lists.

SR-A20675 · Issue 243568

Repaired encrypted remote tracing

Resolved in Pega Version 7.2.1

Remote tracing was not working when URLEncryption was enabled due to an error calling SafeURL. This has been fixed.

SR-A20761 · Issue 247086

New test Suite ruleform display resolved

Resolved in Pega Version 7.2.1

When attempting to create a new unit test suite, no ruleform was presented. Instead, raw XML was displayed. To correct this, the TestSuite Rule Form has been autogenerated so that it is viewable and openable in 7.2 in supported browsers.

SR-A20835 · Issue 239814

Resolved class cast exception for Administrator

Resolved in Pega Version 7.2.1

A class cast exception originating with StreamBuilderTools during logging a debug message caused an error when the Administrator account attempted to display records. This has been fixed.

SR-A20982 · Issue 243968

Repeat grid clipboard index fixed

Resolved in Pega Version 7.2.1

On deleting a row from the repeat grid and proceeding, the deleted row was reappearing due to the improper resetting of a clipboard index when a grid has multiple references. The indexing has been fixed.

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