SR-D33491 · Issue 511728
Code fragment removed to resolve CookieDisabledException
Resolved in Pega Version 8.4
After upgrade, a CookieDisabledException occurred after a post activity was invoked in the single sign-on (SSO) authentication service. This was traced to the site using the deprecated flag "redirectguests" as part of SSO-based login for mashup usecases. This flag was used to check if a cookiedisabled exception was thrown or not, and if there was no cookie, if a requestor was authenticated in first request. However, the flag has been removed as part of work done to omit the Cookie support check on Mobile App UAs. Code that supported the use of this flag remained after that work and led to the exception being generated, but has now been removed as well.
SR-D37980 · Issue 512436
Data page triggered from SLA reloads per interaction
Resolved in Pega Version 8.4
After configuring an SLA goal activity which takes one parameter from a thread-level data page with 'Reload once per interaction' checked and the source of the datapage was a data transform which used pyWorkPage.pyID to set a property value, goals were not updated as expected. If multiple cases reached their SLA goal at the same time, the first case ID was being sent as a parameter to the goal activity for all of the other case IDs. For example, if case 1, case 2, and case 3 reached their goal at the same time, the case 1 ID was passed as the goal activity parameter to case 2 and case 3. This was traced to multiple items that were getting processed in a single agent run picking up the stale data present in data page because it was not being cleared, and has been resolved by removing the Read-Only data pages after every item that is processed, ensuring that it will be reloaded the next time the data page is triggered.
SR-D38392 · Issue 510242
Daemon management agent count now includes startup agents
Resolved in Pega Version 8.4
A mismatch was observed in the agent counts given by daemon management and admin studio, with the daemon management API populating an agent count that was less than the agent count shown in admin studio. This was due to Daemon management considering only running agents excluding startup ( i.e, "Next Run Time" as not null). As startup agents and agents which have thrown exceptions do not hold any value for "Next Run Time", they were not considered. To make this count more consistent, the management Daemon will return the agent count of all running agents including startup agents.
SR-D41532 · Issue 512003
Handling added for padding character changes in StatiContent generation
Resolved in Pega Version 8.4
After upgrade, only 3 tenants were accessible in a MultiTenant environment with 52 tenants. A trace showed 500 and 403 errors, and the message "com.pega.pegarules.pub.context.PRSecurityException: Undefined tenant configuration". This was traced to a different padding character used in the StatiContent code that resulted in the tenant URL being encoded and decoded differently, and has been resolved by adding handling for better padding character compatibility.
SR-D41870 · Issue 507162
Quiesce strategy setting warning clarified
Resolved in Pega Version 8.4
Startup was failing when an incorrect quiesce strategy value was set in prconfig. In order to clarify the correct setting value, the formatting of the warning logged in this scenario has been updated to indicate the correct settings.
SR-D43403 · Issue 516528
Supported localization country codes can be 2 or 3 characters
Resolved in Pega Version 8.4
Attempting to localize the labels on the login screen for an unauthenticated user by using the Google Chrome Browser Settings -> Language worked for browser language Spanish - United States [es] but not for Spanish- Espanol [es_419]. This was traced to the use of LocaleServiceProvider <https://docs.oracle.com/javase/tutorial/i18n/locale/services.html>, a custom-developed plugin for the Java Runtime Environment (JRE) that enables the extension of the JRE's supported locale list beyond what is provided out of the box. Because of this, Google Chrome was using a locale list derived from Java 8's getAvailableLocales which are 3 characters when Pega was internally only using 2 character length country codes. Because the ISO3166 standards indicate country codes can be of 2 or 3 character length, the system has been updated to support this use.
SR-D43811 · Issue 511922
Code fragment removed to resolve CookieDisabledException
Resolved in Pega Version 8.4
After upgrade, a CookieDisabledException occurred after a post activity was invoked in the single sign-on (SSO) authentication service. This was traced to the site using the deprecated flag "redirectguests" as part of SSO-based login for mashup usecases. This flag was used to check if a cookiedisabled exception was thrown or not, and if there was no cookie, if a requestor was authenticated in first request. However, the flag has been removed as part of work done to omit the Cookie support check on Mobile App UAs. Code that supported the use of this flag remained after that work and led to the exception being generated, but has now been removed as well.
SR-D44041 · Issue 513919
Local UUID cache will be updated when merge event is detected
Resolved in Pega Version 8.4
Cluster-related issues were seen in multiple production clusters. For some nodes in the cluster the Cluster Management screen showed all expected nodes with valid Node IDs displayed, and on other nodes the Cluster Management screen showed the node ID of itself, SERVER@localhost:5701. On an impacted node displaying the wrong ID, the Node Information landing page did not work and displayed the error "Unable to execute job on ." Multiple advanced agents running on nodes in the affected clusters, both with correct and incorrect IDs, also failed with a similar error "Unable to execute job on <node's job id>". This was traced to a merge performed after a split brain. To resolve this, the code has been updated to handle merge events: when the node UUID is changed as part of a split brain recovery, the local UUID cache will be updated when the merge event is detected.
SR-D44834 · Issue 513641
Concurrent session count updated to avoid false blocks
Resolved in Pega Version 8.4
In multiple scenarios, Operators intermittently received the error "The current session is blocked, as the maximum number of active sessions for the current operator has been reached." Investigation showed that in some cases after the browser is closed and reconnected, there were parallel requests going to the server. While one request was updating a flag in requestor object after the Presence record (Cluster) was updated, the other request was checking the Concurrent session count. Because request 1 had already updated the record in Presence, the system noted the count check as an active session: to correct this, the system has been updated so the current session is excluded from the max sessions reached check.
SR-D4641 · Issue 501790
Max node discovery timeout configuration added
Resolved in Pega Version 8.4
When nodes were restarted, a few of the nodes formed a different cluster instead of joining the existing cluster. This was traced to slow start-ups timing out when Hazelcast was trying to cluster. An enhancement has now been added to allow local configuration for max node timeout on discovery.