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-A21835 · Issue 243872

Flow names can now be found when using duplicate search mechanism

Resolved in Pega Version 7.2.1

When using the duplicate search mechanism and trying to resolve a case as duplicate, an error appeared indicating that the flow name could not be found. This was a handling error, and has been fixed.

SR-A21844 · Issue 241153

VBD enhancements

Resolved in Pega Version 7.2.1

The following enhancements have been added to the Visual Business Director feature of PRPC Decisioning: - Support added for changes in field sizes after partitions load - Partitions will be loaded immediately on VBD server startup - Data expiration based on inactivity is disabled to reduce query latency - Timeout added to VBD queries to handle latency when Partitions initially load - Code that processed Actuals query JDBC resultset is optimized

SR-A21917 · Issue 243020

Added calendar conversion support for Thai locale

Resolved in Pega Version 7.2.1

With locale set to Thailand, the date/time returned caused a substitute operator to be selected. This was an issue with the action time being calculated in the Buddhist calendar used in Thailand whereas the goal time was calculated in the Gregorian calendar. The Buddhist calendar is 543 years ahead of Gregorian, so the isAvailable RUF will convert this date by subtracting the difference.

SR-A22107 · Issue 241929

Empty workbasket names localized

Resolved in Pega Version 7.2.1

In the dashboard of the Case Manager portal, the names of empty Workbaskets were not visible due to missing initialization in the localization. This has been fixed.

SR-A22200 · Issue 242371

Bulk actions filters refresh corrected

Resolved in Pega Version 7.2.1

The values entered into the right side column of the bulk processing filters were not getting submitted to the clipboard when default filter conditions were changed. The refresh action has been updated to correct this.

SR-A22298 · Issue 243924

Refresh corrected for tabbed screen flow perform harness

Resolved in Pega Version 7.2.1

When using the "TabbedScreenFlow7" perform harness, an incorrect refresh call caused the Actions menu on the work object to disappear from the screen. This has been resolved.

SR-A22615 · Issue 244189

Fixed positioning for Options lightbox

Resolved in Pega Version 7.2.1

The Options lightbox in the calendar was floating with the screen while scrolling due to absolute positioning, and has been fixed.

SR-A22750 · Issue 244061

Case Stages status updated by automated process

Resolved in Pega Version 7.2.1

Case stages that were completed by an automated process and not a person maintained their default "Future" status in the Case Stages data page instead of being marked "Past". The stage completion status is determined by value in "pxCompletedBy", but this field was empty due to the automation. A check has been added to resolve this.

SR-A22841 · Issue 245073

All Data Flow keys considered for filtering

Resolved in Pega Version 7.2.1

When a Data Flow containing a Filter was run , the filter step showed incorrect results in the "Successful records" column even though previewing it from the Data Flow rule it showed the correct result. The algorithm that queries a secondary source shape in the data flow was ignoring all but the first key, and has been updated to properly process all of the keys before displaying any results.

SR-A23035 · Issue 245109

Enabled bulk delete of ADM models

Resolved in Pega Version 7.2.1

In order to support the deletion of ADM models in bulk, an enhancement has been added to remove the unwanted models from the database provided a list of them is given as input. The activity pxDeleteModelsByCriteria has been created; "Used to delete ADM models in bulk. Models to be deleted are determined by the criteria selected by this Activity's parameters; a model is deleted if it matches all selected criteria." PLEASE NOTE: activity is not constrained by Application, only by the criteria provided as parameters. Therefore in most cases you will probably want to constrain by 'applies to' class in addition to the other criteria. Please see the tooltip / description of each parameter for more info on their usage. Integer output parameter 'NumberDeleted' returns the number of models that were successfully deleted."

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