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-148375 · Issue 607796

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

Resolved in Pega Version 8.5.2

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.

SR-C91264 · Issue 433438

Localization fixed for dropdown sourced with pystate

Resolved in Pega Version 8.3

When pystate was used to source a dropdown, the options were all uppercase but in the review harness used lower case for IN and OR. This difference caused a failure in localization. This was caused by the Field value instance being defined in lowercase in PyCaption while the UI was treating the active value as an instance of pyCaption, leading to instances of both "in" and "IN" being present. This has been resolved by consolidating the field value to use a single case in the pega-eventprocessing ruleset.

INC-218145 · Issue 715680

DSS introduced to control DSM clipboard page serialization

Resolved in Pega Version 8.6.5

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.

SR-C97399 · Issue 439741

Button type added to allow grid expand in Edge

Resolved in Pega Version 8.3

When using an expand pane grid in a modal with the Edge browser, clicking on the expand icon using the enter key was throwing an error in new window. This was traced to an issue with a hidden non-auto-generated button in the pzModalHelp control not having a default type, and has been resolved by adding type="button" in the control so Edge will treat it as a submit button.

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.

INC-169545 · Issue 649519

Localization updated for decimal slider

Resolved in Pega Version 8.7

When using the Indonesian locale, selecting the range on a slider which allowed selection of a decimal / double value that was then displayed in another textbox caused the value to increase incrementally and the slider always showed the end max. Investigation showed that this was caused by the handling of the comma decimal separator used in Indonesia, and has been resolved by updating the handling to ensure the slider value is converted to the respective locale.

SR-C74652 · Issue 422901

Grid alignment and headers corrected for Opportunities screen in RTL locale

Resolved in Pega Version 8.3

When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages CSS attached to the enduser skin.

SR-C74650 · Issue 422907

Grid alignment and headers corrected for Opportunities screen in RTL locale

Resolved in Pega Version 8.3

When using the RTL locale, the Opportunity detail screen and search screen had grid alignment and header issues. This has been resolved by updating the py-portal-stages CSS attached to the enduser skin.

INC-213124 · Issue 724631

AWS file type added for S3 uploads

Resolved in Pega Version 8.6.5

The correct content type was not getting set when uploading images to S3 using the "pxPublishArtifacts" activity. This has been resolved by adding the content type for AWS files while uploading to S3.

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