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-131332 · Issue 204592

Resolved error on tab switching in DS portal

Resolved in Pega Version 7.1.9

After logging into Pega Designer Studio and launching a portal, performing a switch role/portal in the opened portal and then clicking on the Designer Studio tab closed the secondary portal tab. This was resolved, but an additional problem arose with an error being generated for the tab that was opened previously before switching applications when trying to save or modify the availability of already opened rules in the dev portal. This had to do with the API used to clean up the threads, and has been corrected.

SR-131825 · Issue 202123

Removed duplicate special character encoding on FieldValue validation

Resolved in Pega Version 7.1.9

A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.

SR-131911 · Issue 201388

Logic updated to handle dual-PR config in Repeating Tabs

Resolved in Pega Version 7.1.9

If a Repeat Tabbed Layout was present in a tab and the label on the tab was configured in the cell instead of the Tab Property Panel, submitting the form caused an endless busy indicator. This was caused by the Property Reference being configured on the separate control which is present in the Tab Header when the tab already had the support to configure property references. The child node logic has been modified to prevent this issue.

SR-131919 · Issue 200993

Corrected dropdown value reset following OnChange

Resolved in Pega Version 7.1.9

When a Clipboard page populated through an activity that retrieves data from an external table was used as a source for a drop-down, any validation errors would cause a return to the same screen but the selected value was not retained in the drop-down even though it appeared to be present on the clipboard. This was an issue with the drop-down option having leading/trailing spaces, and has been corrected.

SR-132050 · Issue 204734

Corrected dropdown value reset following OnChange

Resolved in Pega Version 7.1.9

When a Clipboard page populated through an activity that retrieves data from an external table was used as a source for a drop-down, any validation errors would cause a return to the same screen but the selected value was not retained in the drop-down even though it appeared to be present on the clipboard. This was an issue with the drop-down option having leading/trailing spaces, and has been corrected.

SR-132675 · Issue 201772

Removed quotes from dropdown placeholder FV

Resolved in Pega Version 7.1.9

Place holder text in a dropdown was being changed to a string and displaying with quotes even though a field value was selected. This has been resolved by adding logic to not add quotes when a valid field value is entered, and to handle single-escaped quotations.

SR-132720 · Issue 203636

Resolved stale transaction error on editing operator skills

Resolved in Pega Version 7.1.9

After creating a control that displayed a listview of operators in a side panel with a single click event on the list view to show a button, clicking the button was intended to open an out-of-the-box html rule "ShowSkills" which is used to show/update the skills of the operator. However, on the "ShowSkills" screen the error "This action is not allowed as it is outside the current transaction" was being generated when trying to update the operator skills. This was caused by a stale transaction error, and has been resolved by adding the type 'button' on the buttons in the ShowSkills HTML code.

SR-132804 · Issue 202829

Error messages displayed for read-only checkboxes

Resolved in Pega Version 7.1.9

When a validation rule was configured on a checkbox such that if it does not contain a true value it should display error message beside this checkbox when user clicks on submit button, the message was being displayed properly in edit mode but at runtime this error message was not displaying if set to 'read only'. This has been resolved by adding the correct error message generation for read-only configurations.

SR-132927 · Issue 206255

Information on iPad Safari focus issues

Resolved in Pega Version 7.1.9

An issue was found where the onScreen Keyboard disappeared on refresh of a focused input element when using Safari on an iPad. Unfortunately, iPad Safari has compatibility issues with programmatic focusing and this problem cannot be resolved in the PRPC software. The root cause is the browser security: even though focus is getting triggered (value can be set , focused element is the document.activeElement) on the targeted input element, focus behavior (like blue border highlighting, keyboard popping up) is not triggered when the focus in call stack comes from within a function and the first function in the call stack was triggered by a non-programmatic event. Instead, the security mechanism kicks in to prevent you from setting focus on the input. As this is not a PRPC issue, we cannot offer a resolution at this time.

SR-133040 · Issue 203518

Removed duplicate special character encoding on FieldValue validation

Resolved in Pega Version 7.1.9

A recent change was made to the "Validate" activity of the Rule-Obj-FieldValue class to improve security by performing a filterRichText (intended to remove unsafe tags like script tag). However, this broke a reported use case where field values used as the source for the controls dropdown, checkbox, or radio buttons displayed the encoded values of quotes due to double encoding. To fix this, the filterRichText step has been removed from Rule-Obj-FieldValue!validate activity.

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