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-190380 · Issue 678643

CreateVersion rule updated for REST Integration Wizard

Resolved in Pega Version 8.7

When using a JSON response in the Create REST Integration wizard to generate the rules, the wizard displayed a null pointer exception during the final generation. The error pop up message "Generation process has been canceled and all created records have been removed" was displayed on the screen. This was traced to the REST Integration Wizard putting data rules in the wrong ruleset version when the context of both the Integration Layer and the Data Layer were configured to use an existing ruleset and to create a new version of that ruleset, and has been resolved by modifying the pzCreateVersion rule to support this.

INC-145939 · Issue 606898

Updated handling for ID value change during REST connection creation

Resolved in Pega Version 8.4.4

When using the REST Connector Wizard to create a connector, if the ID was changed on the 4th (last) step of the Wizard and then the Create button was pressed, the screen would freeze and a display a javascript error. Investigation showed that when the ID was changed on the screen, the new value was not updated properly and subsequent function calls threw errors. This has been resolved.

INC-185255 · Issue 669441

More responsive attachment loading for interaction portal

Resolved in Pega Version 8.7

Attempting to view a large email attachment in the interaction portal was resulting in slow loading and page responsiveness issues. Investigation showed there were numerous unnecessary height calculations happening when checking the dom elements, and this has been resolved with an update which will use the property mapping js file to make the screen more responsive when highlighting.

INC-148375 · Issue 607798

"Today" will set date-time in the respective operator timezone

Resolved in Pega Version 8.4.4

When a Date was entered using the "Today" option in Datetime control, the Date set used the system date and Time was taken from Timezone specified for the operator. This created issues for a scenario such as operator being set to America/New_York/ EST while the application was accessed in another country such as India or Japan. This was a missed use case and has been resolved by adding code to get the date-time in the respective operator timezone and setting it on click of date-time controls.

INC-207593 · Issue 702428

Spell Check flag removed from Preview and Public Articles

Resolved in Pega Version 8.8

If the spell check button was used when editing a Knowledge Management article, flagged words that were not corrected or set to be ignored continued to display the red flag even when previewing or when the article was being viewed from a public help site. In order to support not showing the flags while previewing or viewing from the Knowledge Management help site, an addition has been made to sanitize underlined words before save or submit.

INC-218309 · Issue 722157

Helper text added to X icon in Theme Cosmos delegated rules

Resolved in Pega Version 8.8

There was no helper text on the X icon in delegated rules when using Theme-Cosmos. This has been resolved by updating the close icon in Rule-Obj-Class!pzDataTypeActionsnow with the text "Click to close".

INC-218145 · Issue 715679

DSS introduced to control DSM clipboard page serialization

Resolved in Pega Version 8.8

When using a Kafka dataset to consume a message from an external topic that had an attribute name with a special character contained in a page list structure, using a JSON data transform for the mapping in a realtime dataflow resulted in the error "Exception in stage: KafkaDS; LegacyModelAspectInvokableRuleContainer.invoke-Exception encountered a :java.lang.UnsupportedOperationException." To resolve this, a new DSS dataset/CLASS_NAME/DATASET_NAME/JSONDataTransform/deserialization/useDSMPage has been introduced. When the value is set to true, the process will follow the previous behavior of DSM clipboard pages being generated when Kafka records are deserialized using JSON data transform. When the value is set to false, the JSON data transform will generate regular clipboard pages and convert them later to DSM clipboard pages. This would avoid errors when a JSON data transform calls methods from the Clipboard API that are not implemented by DSM pages. This DSS is set per data set instance. CLASS_NAME and DATASET_NAME are placeholders which should be replaced by data set's pyClassName and pyPurpose property values. In addition, a similar DSS, dataset/CLASS_NAME/DATASET_NAME/JSONDataTransform/serialization/useDSMPage, has been introduced for serialization.

INC-150222 · Issue 612576

Custom client-side future date validation works on mobile

Resolved in Pega Version 8.4.4

After developing a custom client side validation based on documented examples that used jquery to locate two input fields (date pickers) and added an on-change function, the validation worked as expected on the desktop but gave a validation error for any future date when using the mobile app or browser. This was an issue with the name attribute handling on mobile, and has been resolved.

INC-164429 · Issue 633222

Map address control works in read only view

Resolved in Pega Version 8.7

The pyTrackingMap control was not showing position when used in read-only mode. This was traced to a missed use case, and was caused by the property handle being considered in order to get the value of the current address, but in the case of read-only the property handle was empty and the address field was considered. To resolve this, in case of a read-only track map, the addressproperty value will be considered instead of the property handle.

INC-178834 · Issue 660425

RDA support added for Citrix XenApp

Resolved in Pega Version 8.7

Robot Runtime was not working in a Citrix XenApp environment when using the JWT token generated by the D_pxRoboticJWTToken data page to identify the user. This has been resolved by updating the scope of the datapage D_pxRoboticJWTToken from node level to requestor, which will allow the user information in the JWT token to be passed to the routing service and support the use of RDA in Citrix environments.

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