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 update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-B15685 · Issue 292401

Flexibility enhancement for mobile dropdown displays

Resolved in Pega Version 7.3

As a part of an enhancement for mobile apps, a checkbox for "Allow scrolling for more results" has been introduced in the property panel of the Autocomplete. By default its value will be unchecked, implying the old behavior which limits the "Dropdown" options on autocomplete to 8 for backward compatibility. If the checkbox is used, it will honor the "Max results displayed" setting used for list based autocomplete. If the max results value is not specified, using the checkbox will cause the dropdown to show all the results.

SR-B15749 · Issue 289752

Enhancement for capturing SOAP envelope of Async SOAP Service

Resolved in Pega Version 7.3

The SOAP service request envelope has been available for service activity using the 'pxRequestor.pxReqSOAPEnvelope' property in synchronous execution mode, but that envelope was not available in asynchronous execution mode due to asynchronous execution using a different requestor. In order to support this information in asynch mode, an enhancement has been added to allow the service activity to perform a look-up for the pxReqSOAPEnvelopeinformation in the parameter page.

SR-B15790 · Issue 285997

Handling added for dot in visible-when rule

Resolved in Pega Version 7.3

On click of the icon next to the visible-when rule in order to open the rule, the error "Unable to open the rule as Base Class Value is empty" was generated if the 'when' rule of the conditions included a dot. To correct this, the pega_openRuleSP logic has been modified to fall back to the section class from the PRXML when the value of baseClassValue is empty.

SR-B15831 · Issue 286160

Fixed enter actions for grid layout in overlay

Resolved in Pega Version 7.3

Enter Actions were not working properly on a Grid layout in Overlay. To correct this, a Keyup check has been added for grid keypress events in the GenerateControlAction RUF.

SR-B15831 · Issue 304223

Fixed enter actions for grid layout in overlay

Resolved in Pega Version 7.3

Enter Actions were not working properly on a Grid layout in Overlay. To correct this, a Keyup check has been added for grid keypress events in the GenerateControlAction RUF.

SR-B15831 · Issue 283045

Fixed enter actions for grid layout in overlay

Resolved in Pega Version 7.3

Enter Actions were not working properly on a Grid layout in Overlay. To correct this, a Keyup check has been added for grid keypress events in the GenerateControlAction RUF.

SR-B15858 · Issue 286667

Fixed Right align of header in repeating grid

Resolved in Pega Version 7.3

When a Repeating grid was included in a section and the header used apply alignment as Right, the results did not display as expected. This was due to missing styles corresponding to Header Label Align class, which have now been added.

SR-B15880 · Issue 289450

Enable/disable of "+" icon in mobile app fixed

Resolved in Pega Version 7.3

The enabling and disabling of the "+" icon was not happening in the Mobile Hybrid app even when disabling condition were met. This has been fixed.

SR-B15884 · Issue 288287

Page level error display honors KeepPageMessages value

Resolved in Pega Version 7.3

Page level error messages on the perform harness were flickering when a flow action was submitted. This was caused by the message only displaying for half a second, and has been corrected by correctly honoring the "pega.u.d.KeepPageMessages" value.

SR-B159 · Issue 272693

Wizard will halt if rules to be deleted are in locked rulesets

Resolved in Pega Version 7.3

After running the Connector and Metadata wizard using a WSDL metadata file and then locking the current ruleset version, running the same wizard again using the same WSDL file and selecting OverWrite in the OtherConflicts step caused the rules in the locked first ruleset to also be overwritten. To prevent this, the CompleteRuleGeneration activity will cause the wizard to halt if it encounters rules that would be deleted that are in locked rulesets. When the ruleset(s) are unlocked, the wizard will continue.

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