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.

SR-B8495 · Issue 279313

SVG image support added

Resolved in Pega Version 7.3

Support has been added for previewing and searching for SVG type images.

SR-B8696 · Issue 279855

Support added for FCM GetNextWork

Resolved in Pega Version 7.3

When using Federated case management (FCM) to get next work, the work object pulled was not assigned to the operator. This was due to the implementation of FCMR not supporting the moving of workbasket assignments to worklist through get next work. To support this use, the following functions now accept extra parameters as last param: FCMRGetNextWork FCMRGetNextWorkItem FCMRProbeNextWorkItem This will enable distinguishing between normal GNW and federated GNW, and it is possible to override any py rule call MoveToWorklist.

SR-B8744 · Issue 279872

OnClick passes parameters to DT from inside a grid

Resolved in Pega Version 7.3

The OnClick event was not passing its parameters to a Data Transform or activity if it was inside a grid due to the property not being generated with its full reference. This has been fixed by modifying pzActionAppendValue to generate the complete property reference instead of just the property name.

SR-B8793 · Issue 278410

Flow warnings show consistently

Resolved in Pega Version 7.3

Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages

SR-B8793 · Issue 278405

Flow warnings show consistently

Resolved in Pega Version 7.3

Due to conflicting handling of temporary pages by two different processes within the Rule-Save function, warnings were only displaying intermittently as flow rules were saved, refreshed, or checked in. To ensure consistent handling, a single internal parameter has been added that will be used for creating/removing temporary pages

SR-B8847 · Issue 278000

FCM/FCMR documentation updated

Resolved in Pega Version 7.3

The documentation on the PDN for installing and configuring FCM 7.12 has been updated for FCM and FCMR.

SR-B8898 · Issue 279449

Reference to outdated property removed

Resolved in Pega Version 7.3

When building a system with WebSphere 8.5.5, DB2 10.5fp7 and Java 8, creating the environment and testing the connection on its datasource produced the warning: "DSRA8200W: DataSource Configuration: DSRA8020E: Warning: The property 'progressiveLocators' does not exist.". This was traced to a code fragment left after that property became unsupported which has now been removed.

SR-B9137 · Issue 278539

RD column context menu alignment fixed

Resolved in Pega Version 7.3

On a report definition with many columns, scrolling to the right caused the column context menu to not be aligned with the column. The menu alignment code calculations have been modified to correct this.

SR-B9137 · Issue 267865

RD column context menu alignment fixed

Resolved in Pega Version 7.3

On a report definition with many columns, scrolling to the right caused the column context menu to not be aligned with the column. The menu alignment code calculations have been modified to correct this.

SR-B9286 · Issue 278610

Enhancement to get work items from multiple workpools for mobile user

Resolved in Pega Version 7.3

An enhancement has been added to support multiple workpools belonging to same application for mobile users. The code will iterate through all workpools which are offline enabled for the operator and get the work items in pzDataSyncGetWorkList 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