SR-D28538 · Issue 502058
Corrected requestor status flag for direct map
Resolved in Pega Version 8.4
Numerous "Unable to create requestor" alerts were logged. This was traced to an error in HttpAPI where after retrieving the requestor from the internal requestor map directly, the requestor creation status flag was not set properly. This caused last action to post that alert instead of the correct notice of "existing requestor retrieved". This has been resolved so the flag reflects the correct status.
SR-D31066 · Issue 502254
Improved performance for "Show-HTML" in a grid with numerous controls
Resolved in Pega Version 8.4
‘Show-HTML’ was taking an excessive amount of time to render a UI for grid with a large number of controls. This was traced to the handling for generating and clearing markup creating an exponential growth situation, and has been resolved by modifying the system to remove redundant copies of a string in the markup string buffer.
SR-D31259 · Issue 502024
Passivation restoration will not continually re-queue on failure
Resolved in Pega Version 8.4
When an operator record was passivated with the Access Groups it had at that time, during restoration it attempted to validate it even if it had been removed. In this case, an Access Group with RuleSets and the Rule-Application to match was created and added to an operator record, then changes were made and the access group was removed from the operator record. The requestor was passivated and saved to the pr_sys_context table, and when the system tried to restore the requestor (the connected browser was left open), it started throwing exceptions because the access group it was trying to use no longer existed. The system continued to retry until a new session was started or the row was deleted from the pr_sys_context and the pr_page_store manually to remove the offending requestor that was now invalid. To resolve this, a layer has been added within the Passivation Daemon to better handle this failure case. NodeRequestorMgt has been updated to catch the PRRuntimeException explicitly and not re-queue activations that fail due to their root cause being an invalid configuration exception. By targeting only PRRuntimeExceptions which wrap InvalidConfigurationExceptions, this will fix this specific issue without impact to other cases.
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.