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-184798 · Issue 703269

PRconfig added for JVM user/password

Resolved in Pega Version 8.7.1

The setting Dcom.sun.management.jmxremote.local.only=true has been added for use when JMX authentication is enabled by providing jmxuser/password through prconfig.

INC-194348 · Issue 703374

Resolved multiple copies of Pega0050 alerts

Resolved in Pega Version 8.7.1

The PDC alert Pega0050 was seen multiple times for the standard pxgetoperatordetails activity, step 6.This has been fixed by removing the pagecopy and updating the data page properties.

INC-195580 · Issue 684492

Delay Factor updated to allow values < 1.0

Resolved in Pega Version 8.7.1

After modifying the "Delay factor" parameter on a queue processor rule and and clicking the "Save" button, refreshing the page caused the value of the "Delay factor" parameter to change. This has been resolved by updating the delay calculation strategy to support factors < 1.0.

INC-196478 · Issue 683130

CORS policy updated for GET streams

Resolved in Pega Version 8.7.1

CORS (Access-Control-Allow-Origin) support has been added to handle Stream calls during GET requests.

INC-163791 · Issue 704029

Simplified default reference time calculations

Resolved in Pega Version 8.7.1

After a job scheduler was configured to run at Start time = 21:00:00 for Time zone = Europe/London, the scheduler determined 20:00:00 as the next start time. This was due to the calculation for the next start time using the time zone offset calculation pattern for the date and time stored in System-Runtime-Context.pxCreateDateTime, which had difficulty with changes to the time zone definition implemented in the time between the given date and today (meaning the current time) such as daylight savings time. To resolve this, the default reference time from System Runtime Context will be 'now' instead of Date(0).

INC-192649 · Issue 706134

Basereference context available for attach content control

Resolved in Pega Version 8.6.4

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

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-195601 · Issue 685771

Basereference context available for attach content control

Resolved in Pega Version 8.6.4

An "undefined" error occurred when attaching a file using the attach content control in the mobile harness. To resolve this, support has been added to run attachcontent in basereference context. This can be enabled by setting pega.attachToCtxPage to true.

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-206049 · Issue 703468

Resolved activity registration error for Scan Barcode/QR Code

Resolved in Pega Version 8.6.4

Attempting to add the action 'Scan Barcode/QR Code' to a button generated the warning "Unauthorized request detected : Unregistered request encountered with params pyActivity:pzRunActionWrapper pySubAction:runAct pzActivity:pzScanCode". Investigation showed this was due to the pzScanCode activity referred to in pzpega_control_actions_scanCode.js file not being registered, and has been resolved by adding code to register the necessary events for both button and navigation.

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