SR-B69359 · Issue 337302
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-C11323 · Issue 352191
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-C16944 · Issue 364121
pxObjClass of StepPage retained when using adoptJSONObject
Resolved in Pega Version 8.1
When using the adoptJSONObject method in a REST Service activity, calling adoptJSONObject made the pxObjClass of StepPage null. However, the pxObjClass retained its correct value after calling the adoptJSONObject method if the tracer was running. In this scenario, when JSON was adopted on to a page which had pxObjClass set on it and JSON didn't have pxObjClass within it , the resulting page was becoming classless. This has been fixed by reading pxObjClass from the page and retaining it if it is not empty and if pxObjClass is not present in stream.
SR-C40010 · Issue 382499
Corrected URL formation problem when using Tomcat
Resolved in Pega Version 8.1
A blank screen was seen when trying to open Decision Table headers, and the color picker pop-up was blank when trying to choose a color for the skin. This was traced to an incorrect URL formed when using Tomcat, caused by the prweb/hash being appended twice in the URL. The root cause was unnecessary decoding of extURL in 'pzDisplayModalDialog' , and this has been fixed by adding the proper urlCrossScriptingFilter.
SR-C48072 · Issue 388475
Corrected URL formation problem when using Tomcat
Resolved in Pega Version 8.1
A blank screen was seen when trying to open Decision Table headers, and the color picker pop-up was blank when trying to choose a color for the skin. This was traced to an incorrect URL formed when using Tomcat, caused by the prweb/hash being appended twice in the URL. The root cause was unnecessary decoding of extURL in 'pzDisplayModalDialog' , and this has been fixed by adding the proper urlCrossScriptingFilter.
INC-170423 · Issue 648984
Added catch for SAML WebSSO duplicate key exception
Resolved in Pega Version 8.5.4
After logging in from SSO, closing the Pega window and opening it again resulted in the error "Unable to process the SAML WebSSO request : Violation of PRIMARY KEY constraint. Cannot insert duplicate key in object." This has been resolved by updating the session index handling and adding a catch for the duplicate key exception.
SR-C45673 · Issue 391239
Behavior changed to use latest metrics when when decisioning metrics cannot consolidate them
Resolved in Pega Version 8.1
Component stats were not showing up on Select Designer Studio ->Decisioning ->Decisions -> Data Flows -> Real Time data flows. The shape metrics on a data flow run appeared to be reset and not processing any records anymore. The problem was that metrics from old nodes (which have become incompatible with the current data flow shapes) were merged in an indeterministic order which caused the old metrics to replace the new metrics on the data flow run progress page. This gave the impression that the data flow shapes were not processing any records anymore. The behavior has now been changed such that when the system merges metrics and cannot consolidate the metrics that are being merged, the latest updated metrics will prevail as opposed to the previous behavior of the 'second' metrics prevailing. In addition, whenever metrics are reset because the data flow has changed or metrics from old nodes cannot be added to the current metrics, a warning will be added to the run to explain the change in metrics of the shapes.
INC-162434 · Issue 640052
LookUpList correctly executes during SSO login with model operator
Resolved in Pega Version 8.5.4
After configuring SSO to create operators on fly using a model operator, a new user logging in for the very first time had their operator ID created using the model operator, but after upgrade new users logging in to the system received the error "Only authenticated client may start this activity: RULE-OBJ-ACTIVITY @BASECLASS LOOKUPLIST". This was due to the methods used for additional security on the activity @baseclass LookUpList which allows it to only be run by authenticated users, and has been resolved.
SR-C38931 · Issue 382819
Corrected Listener open error when using ListenerManagement page
Resolved in Pega Version 8.1
When clicking on any Listener on the ListenerManagement landing page, it displayed the following error page: "Unable to open instance - Possible causes may be (1) Rule may no longer exist. (2) Availability of the rule may be set to No/Draft, Blocked or Withdrawn. (3) Circumstance of the rule may be preventing access. (4) Current date is not within the date range specified in the rule. (5) Access group or role may not have the appropriate privileges to open the rule." However, the same rule could be opened from Records Explorer. Analysis found that the .pyListenerInsName property used to open the listener rule was blank in the pyListenersList in ListenerManagementPage; initialization of the mListenerInsName field has been added to correct this issue.
INC-155878 · Issue 645364
Class list updated when using ActivateDocument in portal navigation
Resolved in Pega Version 8.5.4
Global search worked the first time it was used, but failed after another case was opened from the dashboard or there was a click on any landing page home, dashboard, or space. Investigation showed this was caused by the pySearchText being blank in the clipboard, which was traced to a harness context issue related to pega.desktop.activateDocument being used in pzPortalNavigation on DynamicLayout with Application Logo and Application label. To resolve this, an update has been made that will update the class list with the proper one when the data-harness-id is set.