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-178148 · Issue 660925

Handling added for SSO servlet name

Resolved in Pega Version 8.6.2

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-188405 · Issue 673065

Handling added for SSO servlet name

Resolved in Pega Version 8.6.2

After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.

INC-174267 · Issue 669672

Wait action persists when using Urgency Adjustment

Resolved in Pega Version 8.6.2

When using the Urgency Adjustment (pyAdjustAssignmentsla standard local action), once a case reached the wait action and the goal and deadline were updated the previous pyWaitAction was not being stored. This has been resolved by ensuring the previous pyWaitAction will be stored and passed to the AddAssign activity.

INC-195519 · Issue 698498

Support added for using CFW when Pega server is unavailable

Resolved in Pega Version 8.6.4

Data synchronization changes have been added to allow Client for Windows to work in offline mode without an AppCache manifest.

INC-176112 · Issue 662449

When rule inside a loop correctly picked

Resolved in Pega Version 8.6.2

While using a 'when' rule inside a loop of a page list, the rule was not being picked during runtime. This has been resolved by adding an update to allow an assembly time class name to be passed into runtime.

INC-211018 · Issue 707524

Number control correct when IME is Japanese

Resolved in Pega Version 8.6.4

The Microsoft Windows Input Method Editor (IME) allows developers to enter complex characters in four different East Asian languages using the standard keyboard. When IME was in Japanese mode, entering a number resulted in the input happening twice with the result of an entry such as 12345 becoming 124512345. This has been resolved by updating the code to ensure there is no duplicate IME keyboard event.

INC-201633 · Issue 703799

Reload icon disappears when refresh is ready

Resolved in Pega Version 8.6.4

After updating the Field Service Mobile App from Pega 8.3 to Pega 8.6, the wait icon continued to be visible even after the refresh was completed. This has been resolved.

INC-204256 · Issue 701948

Helper Text displays for radio buttons with 'when' condition

Resolved in Pega Version 8.6.4

The helper text overlay was not displaying on radio button fields that were conditionally visible using a 'When' rule, though it displayed as expected if a visible expression had "Run visibility condition on client" checked. This has been resolved by adding support for a helper text overlay on radio button with visibility condition (when rule).

INC-180184 · Issue 665090

Assistance and diagnostics added for issue with opening imported 'when'

Resolved in Pega Version 8.6.2

After update, attempting to open rules that were developed on lower environments and then imported resulted in unknown errors. A workaround has been added to skip and log any corrupted property that might be interfering with the rule opening: enable Skip-Corrupt-Property to put this in place. To improve diagnostics, the new logger NBA-WME-DEBUG has been added. If the error continues after using Skip-Corrupt-Property, Skip-Corrupt-Property should be disabled and NBA-WME-DEBUG should be enabled and kept active until the issue occurs again.

INC-165992 · Issue 657693

Table Filter save uses correct harness

Resolved in Pega Version 8.6.2

After creating a new view for table and then relaunching the portal or switching between tabs, the created views were not visible. Investigation showed that the views were saved under the incorrect pycaseworker harness on initial load, causing them to not be visible when returning from the switch and using the correct pyCWPortalContent harness. This has been resolved with the addition of the new parameter innerHarnessName to get the harness name when creating a personalization instance.

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