SR-C8702 · Issue 349662
Fixed cataloging for framework hotfixes with non-java code
Resolved in Pega Version 7.4
The system was unable to catalog Strategic Application hotfixes that included non-java code instances (e.g. .xml or .properties files) due to Framework hotfixes using a different version format that caused validation failure. To correct this, the system will bypass redundant release version validation for Strategic Application hotfixes so that it can catalog non-java code instances.
SR-C8702 · Issue 344809
Fixed cataloging for framework hotfixes with non-java code
Resolved in Pega Version 7.4
The system was unable to catalog Strategic Application hotfixes that included non-java code instances (e.g. .xml or .properties files) due to Framework hotfixes using a different version format that caused validation failure. To correct this, the system will bypass redundant release version validation for Strategic Application hotfixes so that it can catalog non-java code instances.
SR-B47858 · Issue 304348
Access Group Guardrail warning removed from password change
Resolved in Pega Version 7.4
Changing the password for the '[email protected]' operator generated the warning: 'The same Access Group should not be shared by Operators and Requestor Types. Access group PRPC:Agents was also referenced by Requestor Type DATA-ADMIN-REQUESTOR PRPC!BATCH'. The password change did take effect as expected. This guardrail warning was shown if the Access group used by the [email protected] operator, i.e. PRPC:Agents, was specified in any of Data-Admin-Requestor instance, and has been resolved by removing the unnecessary check.
SR-B96972 · Issue 343423
Specification rule save-as loads requirements
Resolved in Pega Version 7.4
While doing 'Save As' of a Specification rule from a locked ruleset version to a higher unlocked version of the ruleset, the linked Requirements were not shown in the Requirements section under the Details tab. Sometimes a refresh would show the requirements, but intermittently an exception would be generated. This was traced to the system not auto-populating the requirements list on 'save as' of the specification, and code has been added to PostActionSaveAs of the 'Rule-Application-UseCase' class to populate the Requirements link on 'save as' of this rule.
SR-D48396 · Issue 520424
Hazelcast upgraded to resolve node startup issue
Resolved in Pega Version 8.1.8
Post data upgrade, the ADM tier failed to start and the error "java.lang.IllegalStateException: Node failed to start!" appeared. This was traced to a dormant bug in Hazelcast 3.11 that caused starting nodes to fail when the Hazelcast master node was shutting down, which was exposed by recent Pega changes made to enable parallel restarts of nodes in Cloud environments. Hazelcast delivered a fix for the parallel restart problem and the hotfixed jar has been merged into the platform.
SR-D52249 · Issue 515703
Resolved Oracle thread deadlock for Merge SQL
Resolved in Pega Version 8.1.8
After starting a large cluster and running it for a couple of days, Oracle Deadlocks started to appear due to resource contention during MERGE SQL execution on the PR_INDEX_REFERENCE database table. The "ORA-00060: deadlock detected while waiting for resource" ERROR occur continuously every 10 minutes during the "MasterForNewAgents" Daemon run. All JVMs are impacted by the ERROR/Deadlock. Investigation showed that even though the identified / problematic Data-Agent_queue instances were disabled for PegaAESRemote, the MERGE SQLs continued to fire. To resolve this, an update has been made so the system will skip the copy of rule reference property from RAQ, while creating DAQ.
SR-D55160 · Issue 520356
Namibia and Botswana added to Currency Symbol values
Resolved in Pega Version 8.1.8
Support has been added for the Namibia (en_NA) and Botswana (en_BW) locales in the default Currency Symbol values.
SR-D56527 · Issue 538302
DSS PegaAESREmote*ResetTableStats set to false
Resolved in Pega Version 8.1.8
In order to prevent an issue with resetting table stats that potentially impacts postgres in an unintended fashion, the DSS PegaAESREmote*ResetTableStats has been set to false.
SR-D57038 · Issue 519381
JobScheduler DST handling updated
Resolved in Pega Version 8.1.8
When the locale being used changed out of Daylight Savings Time, scheduled jobs did run at the same local time as before but instead ran an hour earlier than expected. Investigation showed that jobscheduler calculated the next runtime based on the time difference from the cluster reference time and current time in milliseconds, and this offset in milliseconds was added to next run time. Since the cluster was started in DST, the job was running on same time due to the time difference. To resolve this, the system will use a calculation offset and set hours/minutes to nextRunTime object so that calendar lib handles daylight savings.
SR-D58927 · Issue 522289
Added expiration for orphaned tracers
Resolved in Pega Version 8.1.8
After tracing a REST service, the tracer was persisting but not showing in the requestor list from Admin studio. The operator shown in the error did not have access to the system anymore, and other users were not able to trace the service rule. Trying to clear the requestors in all the nodes using API POST /nodes/{nodeID}/pools/requestor/clear also did not resolve the issue. To address this, a distributed rule watch expiration has been added.