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.
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.
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.
SR-B76526 · Issue 326533
Backwards compatibility enhancement for @when() validation
Resolved in Pega Version 7.3.1
After upgrade, a Strategy rule which referred a 'when' with the syntax @when(isOnlineApplication) was failing with design time validation saying that when rule was not found in the SR and instead it had to find it in the Customer/Applies to class. For the @when() issue, the root cause was that the validation context of @when() was switched from Applies-To class to the Step Page class due to a change in the core engine. The behavior of expression parsing for when rule calls was changed in release 7.2. It used to take the Apply-to class to validate the existence of the rule, but not it is taking the Step Page class. And Strategy rule doesn't push/pop stackframe due to performance reasons, thus StepPage on stack for Strategy is always the same as Primary page. For greater compatibility, the system will set the PageContextClass to the Apply To class so the expression parser can validate the setup which is expected at run-time.
INC-192464 · Issue 681751
PackageComponent updated for use with repositories
Resolved in Pega Version 8.7
Exporting a zip file created by the Component wizard to a repository resulted in an error, however the same process worked as expected when the zip file was created by the Product wizard. Investigation showed that pxPackageComponent was not kept up to date with new metadata requirements for Artifactory export. This has been resolved by modifying pxPackageComponent step 7 to set Param.ArtifactType to "component" and Param.ArtifactName to [component name]_[component version]. A privilege check has also been added to zipMoveExport.
SR-B68837 · Issue 318361
Bad 'when' fixed for ruleset translation
Resolved in Pega Version 7.3.1
Due to an error in a 'when' condition that caused incorrect overwriting, Spanish rulesets were being displayed for saving correspondence/paragraph rules irrespective of the language translations that had been imported. This has been fixed.