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-172350 · Issue 658276

Removed duplicate Set-Cookie Secure Keyword

Resolved in Pega Version 8.5.5

Checking the headers of the login page showed the Cookie Pega-AAT duplicated the Secure keyword. This was traced to the PegaAATCookieWrapper extending the CookieWrapper class and causing the secure flag to be set in both the classes. This did not have a functional impact, but the secure flag set has been removed from the PegaAATCookieWrapper class to avoid duplication.

INC-172859 · Issue 661201

Invalid date handling added to Legacy Adapters

Resolved in Pega Version 8.5.5

Running the Job Scheduler activity failed with the error "not a valid date/time value". Investigation showed this was caused by LegacyPropertyAdapter.isEmpty being returned as true in case of properties having invalid values, and has been resolved by adding handling for an InvalidValueException in LegacyPropertyAdapter and LegacyPageAdapter.

INC-173392 · Issue 650243

Metadata space out of memory Healthcheck failure propagates correctly

Resolved in Pega Version 8.5.5

When an "OutOfMemoryError:MetaSpace" was generated from PRClassLoaderDB.loadClass, the exception was not propagated from its caller method. This has been resolved by adding the hook to call HealthMonitorService().processCriticalError in PRClassLoaderDB.loadClass(). HealthCheck will be set to 'UNHEALTHY' based on errors configured in GenericErrorAnalyzer, which includes an out of memory condition.

INC-173436 · Issue 648820

Performance improvement for Application Save: Node Level Data Pages

Resolved in Pega Version 8.5.5

As part of new functionality introduced in 8.3, data types defined in the application record will be turned into data objects on Application save. As part of this process node level pages are invalidated and reloaded and there is an explicit commit that marks the Application record as dirty and sends any calls for the application record to the database for fresh records. In a multi-node environment, the number of queries to get the application record being saved became exponentially higher and performance impacts were seen. This has been resolved by updating the system to skip eager loading of the data page definition when an access rule or application definition is saved.

INC-173895 · Issue 655914

ZMW added to currency codes

Resolved in Pega Version 8.5.5

The Zambian Kwacha, "ZMW", has been added to the currencies code list in ENCurriencies.xml .

INC-174243 · Issue 655885

Links to specifications persist appropriately

Resolved in Pega Version 8.5.5

When linking Rules to Specifications, check-ins of some unrelated rules deleted the link. Investigation showed the deletion happened in the pzHandleLinksPostCheckIn activity, and was caused by an empty parameter page name that caused pcInsKey to not have a value, so all links returned by "Obj-Browse" were later deleted. To resolve this, an update has been made to insure the "Pass current parameter page" option in step 2 of the Connect REST PostCheckIn activity is enabled so that the downstream activity pzHandleLinksPostCheckIn behaves as expected.

INC-174612 · Issue 659251

Queue Processor threads explicitly cleared before new interaction

Resolved in Pega Version 8.5.5

Queue Processor was not clearing already evaluated freshness caches before running an activity, potentially causing a stale data page to be processed. This has been resolved by explicitly clearing the thread on a new interaction by invoking ((IPRThread) thread).clearOnNewInteraction.

INC-174694 · Issue 650780

Check added to ensure read locks are released

Resolved in Pega Version 8.5.5

Read locks were not being properly released if a thread was holding a read lock and the system encountered an issue such as an out of memory condition. To resolve this, an update has been made to DeclarativePageDefinitionCacheImpl which will check whether a thread holds any read lock before trying to acquire a write lock, and if so release all the read locks held by that thread.

INC-175343 · Issue 655351

Invalid date handling added to Legacy Adapters

Resolved in Pega Version 8.5.5

Running the Job Scheduler activity failed with the error "not a valid date/time value". Investigation showed this was caused by LegacyPropertyAdapter.isEmpty being returned as true in case of properties having invalid values, and has been resolved by adding handling for an InvalidValueException in LegacyPropertyAdapter and LegacyPageAdapter.

INC-176112 · Issue 656971

When rule inside a loop correctly picked

Resolved in Pega Version 8.5.5

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.

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