INC-175897 · Issue 655466
LookUpList correctly executes during SSO login with model operator
Resolved in Pega Version 8.7
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.
INC-200299 · Issue 689561
LookUpList correctly executes during SSO login with model operator
Resolved in Pega Version 8.7
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-D38492 · Issue 505489
Batching now enabled when using IH Summary shape in substrategies
Resolved in Pega Version 8.2.4
Batching was not being enabled when using IH Summary shape in substrategies. This was traced to the IH_SUMMARY_CACHE field not automatically being passed to sub-strategies, and has been corrected.
SR-D39003 · Issue 505997
Threads will be updated to maintain assembly context when using Static Assembler
Resolved in Pega Version 8.2.4
When running the Static Assembler utility from UI, the assembler process completed successfully but the PegaRULES.log was flooded with the FATAL exception "Usage error - next Executable not based on current". This error was generated from com.pega.pegarules.session.internal.mgmt.Executable constructor, and indicated an issue with the thread context being different from the assembly context. To resolve this, the system has been modified to update the context of thread to what is expected as assembly context.
SR-B52773 · Issue 312408
Improved null/blank parameter handling when using Microsoft Internet Explorer.
Resolved in Pega Version 7.3.1
After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.
SR-B52773 · Issue 312968
Improved null/blank parameter handling when using Microsoft Internet Explorer.
Resolved in Pega Version 7.3.1
After upgrade, opening an assignment in Microsoft Internet Explorer, clicking the save button, and then hitting Function F5 (PF5) caused a null pointer exception on the screen. When OK was clicked in the exception popup it displayed a blank case content screen. This issue was caused by some null parameters on the stored parameter page, and has been resolved by updating the API to better handle null and undefined parameters.
SR-C67397 · Issue 416252
Added check for missing rule data when using abstract class in CSS
Resolved in Pega Version 8.1.3
Including CSS optimization with abstract class in the Advanced tab of the 'Add Optimization' Screen resulted in a Null pointer exception error. This has been resolved by adding a check for missing data from a rule to make the system more resilient in its handling of a corrupt flow-action clipboard page.
INC-168837 · Issue 646972
CSRF token updated for use with OKTA login
Resolved in Pega Version 8.7
An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.
INC-130677 · Issue 570040
When rule accepted in column header
Resolved in Pega Version 8.1.9
A grid was not rendering if it contained a 'when' rule on a column header. This was a missed use case and has been resolved.
SR-B67688 · Issue 320076
Fixed use of FieldValue for templatization
Resolved in Pega Version 7.3.1
When templatization was turned on, a FieldValue containing property references that was set as a Label control value was not getting evaluated properly. This is due to the evaluated FieldValue is being set for pyLabelValue in the metadata of the label when the FieldValue actually needs to be evaluated at client side in templating. To resolve this, the property reference will be used directly instead of FieldValue.