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-216162 · Issue 718923

GetNextWork uses correct tabname

Resolved in Pega Version 8.8

Clicking on Get Next was showing the tabname as "Next" instead of the caseid when using the handleMdcTabs function. This has been resolved by setting the correct tabName in case of getNextwork.

INC-216358 · Issue 712231

Auto Complete working in Mobile Browser configuration

Resolved in Pega Version 8.8

Autocomplete was not working in the mobile browser when logged in as a user and configured with display mode:"in-a-table" and "display as full screen in mobile" disabled. Autocomplete results will always display in List mode in the mobile browser, but with the configuration "in a table" selected and "Display results full screen on phone" unchecked, pzGetACData (which gets called for List mode) was not registered and returned a 403 response. To handle this, the conditions file ActionAssembly.java has been removed so pzGetACData will always be registered.

INC-216404 · Issue 721510

Table alignment corrected for PDF

Resolved in Pega Version 8.8

The align="center" styling was not getting applied whenever the Rich Text Editor was in readonly mode. To resolve this, the CSS style has been updated to correct table center alignment for readonly Rich Text Editor documents and paragraphs in the pzbase-gadgets-ckeditor and pzbase-div-layout CSS files respectively.

INC-216727 · Issue 730957

Inline error message consistent for currency field

Resolved in Pega Version 8.8

After update, an inline validation error triggered on a currency field inside of a text box disappeared when the page was scrolled back to the top. This was traced to the display_removeErrorImage function being called from validation_ValidateFieldOnEvent due to an “onBlur” event, and has been resolved by removing the onblur for a number of decimal type to prevent clearing the validation messages at field level on tab out.

INC-216927 · Issue 714496

Conditional handling added for perceived invalid valuelist reference in design time

Resolved in Pega Version 8.8

After adding a value list property '.pyDateTimeValue(2)' in a section configured in the view editor, the design time error "config issue" was shown. There were no errors at run time and the application's behavior was correct. Changing the subscript of the value list property to (1) ran without an error. In this scenario, the actual usecase configuration will populate .pyDateTimeValue(2), but the view editor believed there was an error in the section because there was no reference to pyDateTimeValue(1) first. This has been resolved by conditionally changing the pyValue to a template property in design time when a perceived invalid valuelist reference is provided as property in the panel.

INC-217304 · Issue 714589

Regex handling updated for non-empty inputs

Resolved in Pega Version 8.8

Expression evaluation for non-empty regex has been updated to include testing for unicode characters to align with recent updates made to CKEditor.

INC-217655 · Issue 723566

Resolved validation check freeze for Dynamic Layout Group

Resolved in Pega Version 8.8

After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.

INC-217680 · Issue 717605

Tab name displayed correctly in embedded mashup portal

Resolved in Pega Version 8.8

"Work Item" was given as as the tab header instead of the Case ID## when:a case link was clicked/opened in an application embedded in an external site (IAC). This was traced to the pega.desktop.support.doGadgetAction function not calling the regular handleGadgetLoad function in this scenario, and has been resolved by explicitly directing work items opened in a multi-doc mashup portal to use handleGadgetLoad.

INC-217821 · Issue 719168

Ensured data refresh for cascading dropdown controls

Resolved in Pega Version 8.8

When using two cascading dropdowns where the options within the second dropdown depended on the selection in the first dropdown, making both selections and then going back to change the selection in the first dropdown appeared to allow changing the selection in the second dependent dropdown, but autocomplete was still holding the previously selected value in memory even though the source property changed. This caused an unexpected behavior when the selections were submitted. Investigation showed that changing the value of the first dropdown triggered an API call to the Refresh assignment action that updated the value, but changing the first dropdown did not cause a refresh call to set the value back to blank in the second dropdown. This issue was seen when the dropdown values were hard-coded but did not occur if each dropdown used a data page. This has been resolved by ensuring the dependent property in a cascade is reset when the source property changes.

INC-218265 · Issue 720611

DoClose updated to resolve lock and context issues

Resolved in Pega Version 8.8

An interaction case was closing when intent tasks were closed from CSRecents. Investigation showed this was due to the doClose activity not being triggered in the right context, and has been resolved. An additional issue with locks not being correctly released after opening the new case Create stage and clicking Cancel in the modal was traced to a missing pyWorkPage in the safeURL params that was needed by the doClose activity, and this has been resolved by adding the primary page name.

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