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-185434 · Issue 674055

Page group property passed correctly for complex questions

Resolved in Pega Version 8.4.6

When the Pega Survey Smart shape was used to configure a list of complex set of questions using Question rules and invoked using the Survey shape, the reload system was not passing the subscript value for the Page group property pyQuestionnaire. This caused an Invalid Reference exception and displayed an error pop up for the end user. Investigation traced this to a call to RefreshList to load a section holding pyQuestionnaire(Subscript) page content which was in place as part of a legacy fix but which has since been made unnecessary due to infrastructure changes in the DOM utilities. To resolve this, the ComplexQuestionCheckboxTemplate and pzComplexQuestionCheckBoxTemplateRowDetails section rules have been updated to remove the RefreshList action on checkbox.

INC-152440 · Issue 614335

Compiler jars load as expected

Resolved in Pega Version 8.5.3

The system was not able to pick up the Default Paths and Default Classes arguments in Configure->System->Settings->Compiler tab when attempting to use a third-party custom jar file. This was an unintended consequence of work done to address performance issues when a requested DASS instance was missing, and has been resolved by ensuring that null values are not cached where are are lookup failures. In addition, enhanced logging has been added to SystemSettingsImpl.

INC-154311 · Issue 615684

Decryption updated for External assignment routed with DWA

Resolved in Pega Version 8.5.3

When an external assignment was routed to a user using DWA, the user was able to access the assignment but received the error "There has been an issue; please consult your system administrator" when submitting. Investigation showed this was caused by the system attempting to decrypt the External assignment with the requestor level key, causing the decryption to fail with a NumberFormatException. To resolve this, the system will check if the obfuscated string starts with Global encryption key prefix and then decrypt with the global encryption key by trimming out the prefix.

INC-154826 · Issue 614819

Enhanced handling for screen/non-screen/screen flow movement

Resolved in Pega Version 8.5.3

When using a screen flow where the last screen had a link to launch a section, a cancel button in the section that was configured with a data transform and a 'Finish Assignment' intended to move back to the screen flow did not work as expected. If a browser refresh was performed and then the cancel button was clicked, the Finish Assignment / return was triggered as expected. Because this configuration navigated to a non-screen flow, the attachOnLoad function did not load the parameter needed for maintaining error messages. This has been resolved by updating the navigation to handle this use.

INC-151421 · Issue 614596

Adaptive Model Save-as works With Predictor Type

Resolved in Pega Version 8.5.3

A predictor change which was accounted for in a previous adaptive model rule version did not work on future save-as. This was traced to a missed use case that when the value 'pyPrevPredTransformation' is empty, validation on that is unnecessary. This has been resolved by adding an 'if' condition in the validation activity.

INC-184311 · Issue 667471

Time value handling updated for IW locale

Resolved in Pega Version 8.4.6

The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.

INC-184443 · Issue 668438

Time value handling updated for IW locale

Resolved in Pega Version 8.4.6

The error -"0undefined/0undefinedundefinedundefinedundefinedundefined is not valid time of day value" appeared when using the 'IW' operator locale and the time field was changed. This was traced to a missed condition check for the IW locale while preparing the selected time value from the dateTimeFormatString, and has been resolved.

INC-144709 · Issue 608798

Removed unnecessary decoding from GetDropdownOptions

Resolved in Pega Version 8.5.3

When using a dropdown sourced by a data page with parameters in the section, passing multiple values as the parameters of the data page resulted in the error "pzGetDropdownOptions:Invalid JSON Stream for data page params" and the parameter values were not resolving at runtime. This was traced to unnecessary decoding in the process, and has been resolved.

INC-178024 · Issue 666418

Timeline correctly shows events in local time zone

Resolved in Pega Version 8.4.6

The DateTime value shown in the DateTime control and Timeline control were different from each other when using a locale setting. For example, a DateTime value which was within British Summer Time (BST) displayed as BST in the DateTime control correctly but displayed as GMT (one hour earlier) in the Timeline control. A site configured with the fr_FR locale in Europe/Paris time zone showed an incoming call interaction at 09:30 AM local Paris time while it appeared as 07:30 (GMT time) on the screen. Investigation traced this to the Pega date time formatter not being used when calculating event times, causing events to display in GMT and not in the local time zone. This has been resolved by ensuring the Pega date time formatter is added to the timeline component to display events in the local time zone.

INC-128406 · Issue 578888

Handling added for radio button with expandpane

Resolved in Pega Version 8.5.3

When given a radio button to select a row in a table (table with Edit Option as Master-Detail - Expand Pane), the first click on the radio button expanded the row but the radio button was not selected. On clicking again, the radio button was selected. The issue was observed in UI gallery as well, and changing the radio button to a checkbox worked as expected. This was traced to a difference in handling related to event infrastructure changes, and has been resolved by adding a timeout in grid specific code for use when there is a radio button with expandpane grid configuration.

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