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-B34134 · Issue 283868

Bulk upload logic improved for SAI contact creation

Resolved in Pega Version 7.3

While bulk uploading a Contact in Sales Automation for Insurance, if the Contact BU template had empty space in the pyID column. the Contact's Individual account and C2A link were not getting created. This was because the bulk upload column needed to be trimmed in the bulk upload process to take the pyID as empty or null, and the logic has been updated to check whether the provided id is empty or not.

SR-B34135 · Issue 291962

Existing Org Names used in new layer

Resolved in Pega Version 7.3

In the Advanced configuration section, existing Organization Names were not being used while creating a new framework on top of an existing framework/application. This was an issue with the framework ruleset prerequisite preparation logic incorrectly setting the ruleset version for the dependency of the framework integration ruleset, and has been fixed.

SR-B34642 · Issue 298361

Fixed Guided Tours for IE

Resolved in Pega Version 7.3

"Guided Tour" in Internet Explorer was only running one page per an operator session, then logging a "Permission denied" error in the JS console for other times when it did not run. This was due to an exception while launching findAndClosePopOver and has been fixed.

SR-B34666 · Issue 292398

Start/End calculation corrected in OutlookAddInCaller ActiveX DLL file

Resolved in Pega Version 7.3

The Start DateTime and End DateTime calculation in the Pega OutlookAddInCaller ActiveX DLL file has been corrected to ensure accurate detection of busy/available.

SR-B34978 · Issue 292494

Source Page context preserved

Resolved in Pega Version 7.3

In RuleDeclareUtil.determinePageContextClass, the pageContextClass is getting overridden by the class of the property mentioned in the pageContext property. This was an error in ensuring no null values were passed, and has been resolved with a check for the value in pageContextClass; if the value is already present, pageContext will not override the pagecontextclass value.

SR-B35050 · Issue 292342

Repaired BIX extract rule filters

Resolved in Pega Version 7.3

pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.

SR-B35050 · Issue 293637

Repaired BIX extract rule filters

Resolved in Pega Version 7.3

pyFilters that existed in rule XLM on check-out were being removed automatically after check-in, causing several runtime problems. This was an unintended consequence of an enhancement that added additional BIX SQL filtering capabilities that were more in line with the other platform modules such as ReportDefinition, and has been fixed.

SR-B35741 · Issue 292129

Corrected thread contention in BAC

Resolved in Pega Version 7.3

A thread contention condition was found in BAC due to the use of maccesscache. That function and the matching clearAccessCache() function are no longer used in Basic ApplicationContext and BasicApplicationContextImmutableimpl to resolve the issue.

SR-B35821 · Issue 296032

Extra space removed from "Filters: " in RD

Resolved in Pega Version 7.3

When a Report with a large number of columns was generated using Report Definition with enable add filters checked in the report definition rule, an unnecessary space appeared between the "Filters:" label and the filters. This has been removed.

SR-B3591 · Issue 277488

Unit Test Case for DataPage localized for comma decimal indicators

Resolved in Pega Version 7.3

When using Dutch language localization, the use of a comma in a decimal number caused a parsing error when creating a Unit Test Case for a DataPage. Proper handling has been added to handle this localization format.

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