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-124103 · Issue 185048

Error logging smoothed for service activities-multi threading on multiple nodes

Resolved in Pega Version 7.1.8

When an item was processed by one node and then in the process of being dequeued by the same node, other nodes attempting to access the same instance and queue received a warning message indicating the item had failed to dequeue. This message was verbose, and was filling up logs. For Advance mode Agents, when item is not found in the Queue Engine it was logging the message with "warnForced". To prevent the logging issue, the log level has been changed from 'warnForced' to 'warn'.

SR-124139 · Issue 186636

Corrected date format error on Data Agents Schedule

Resolved in Pega Version 7.1.8

Post-upgrade in a UAT environment, the Master Agent [Daemon] was not creating the Data Agents Schedule for Rule Agent Queue. This was caused by a month name vs month number mismatch in the YearlyMonth calendar property, and has been corrected.

SR-124153 · Issue 187971

Revised max datetime value for validation

Resolved in Pega Version 7.1.8

Previously, a date property could have a max set value of 31-Dec-9999. This max date was not working in some time zones due to the input date being converted to GMT for internal operations. This meant that 31-Dec-9999 in some locales was getting converted to 1-Jan-10000GMT, which then failed validation. To correct this, the datetime validity logic has been changed to use "1st Jan 00:00:00.000 10000 GMT" for validation.

SR-124168 · Issue 186995

Application document support added for Word 2007

Resolved in Pega Version 7.1.8

When an Application Document was generated, Word 2007 launched a Microsoft Visual Basic window pop up with the message "Compile error in hidden module: clsPRSessionMgr". The root cause of this problem was a defect in the "Rule-File-Binary" rule WordMacroManagerDot.biw" that supports the 64-bit version of MS Word. This has been fixed.

SR-124269 · Issue 185473

Smoothed mode derivation for properties on adopted pages

Resolved in Pega Version 7.1.8

In certain situations, adopting a page onto a Light weight list row might fail if the adopted page had some dummy undefined page properties. To resolve this, while adopting properties from adopted page, the system will derive the mode from properties on adopted page if they are not defined.

SR-124290 · Issue 185890

Added check for error in LDAP logins

Resolved in Pega Version 7.1.8

When a user logged in as external authenticated user over LDAP, a null pointer exception was seen. This exception was generated by the ApplicationSetup activity because the system was missing a page due to the user not being fully identified at that point. To fix this, a null check has been inserted for this condition.

SR-124451 · Issue 185472

Event based subscription processes corrected

Resolved in Pega Version 7.1.8

After migration, "Event" based subscription processes were not firing. In this case, when distributed search was enabled (via following DSS - Pega-SearchEngine . indexing/distributed/index_enabled) and if "Work indexing" was enabled, Business events stopped working. This was due to an incorrect check on the enqueueLightWeight() function and has been corrected to use a blob based table if events fire.

SR-124763 · Issue 188692

UpgradeOnOpen style sheet handling corrected

Resolved in Pega Version 7.1.8

The UpgradeOnOpen activity was run each time a harness was opened on the Developer Portal. This was inefficient, but also caused some manual UI changes to revert on the refresh due to the style sheet being incorrectly reset by the UpgradeOnOpen activity. This has been corrected.

SR-124938 · Issue 189679

Resolved NPE during Agent execution

Resolved in Pega Version 7.1.8

If the connection pool size for eis/PRAdapter (default 10) was too low for the work environment, all agents in few application nodes saw a NPE and were unable to process any messages un until the node was restarted. As part of resolving this issue, it is recommended to increase the pool as necessary and monitor. The system has been updated such that if an agent is unable to startup due to any reason, that agent will be skipped by MasterForNewAgents and the process will continue. Previously, if any agent failed during startup with an exception, all other agents were skipped as well. The exception will be logged.

SR-124944 · Issue 186362

Handling added for 'agentinfoupdate' map exceptions

Resolved in Pega Version 7.1.8

The function 'agentinfoupdate' updates a distributed map (provided by Hazelcast) for the purpose of an agent landing page. This distributed map was throwing exceptions which did not have proper handling, resulting in the agent scheduler being terminated and thereby stopping agent functionality. The required handling has been added to prevent this situation.

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