SR-C97873 · Issue 437280
Added check to maintain key value when using collapseAllMenu in child navigation menu
Resolved in Pega Version 8.3
After a navigation menu had a child added as reference navigation menu that used the function collapseAllMenus, the screen was freezing if a link was clicked in the added child navigation and a javascript error appeared on the console screen. This was traced to an improper key being set in sessionStorage object in setItem due to the nesting, and has been corrected by adding a check in sessionstorage setitem to maintain the proper key value.
SR-D15089 · Issue 485330
Handling added for single quotes in custom DateTime controls when using Export to Excel
Resolved in Pega Version 8.3
A previously resolved issue with the timezone not being appended to datetime when exporting to Excel if a custom control was used has been further updated to better handle single-quote strings in custom DateTime controls.
SR-C91220 · Issue 430362
Modified pzpega_ui_dynamiccontainer to resolve issue with editing the Operator rule form when using IE
Resolved in Pega Version 8.3
The Operator rule form was not opening a second time after being updated in IE. The form worked as expected with other browsers. This has been resolved by modifying the openRuleByKeys function in pzpega_ui_dynamiccontainer to pass a new cloned object to the JSON.stringify function instead of the embedded object.
INC-168837 · Issue 646974
CSRF token updated for use with OKTA login
Resolved in Pega Version 8.6.1
An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.
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-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.
INC-196414 · Issue 684238
OAuth token refreshed when revoked on source
Resolved in Pega Version 8.7
When an OAuth token was used to authorize the APIs in the system, revoking the token at the source, i.e. from the Service side, did not automatically refresh the token and a logoff/logon was required before a fresh token was generated. This has been resolved by adding an update to explicitly purge revoked tokens.
INC-178417 · Issue 670114
Flag reset added for grid with 'Expand When'
Resolved in Pega Version 8.7
A grid using an 'Expand When' condition worked as expected when the condition was true, but once expanded the grid did not collapse if the expand condition was changed to false even if a section/harness refresh was performed. This has been resolved by adding an update which will reset the flag when the result of 'Expand When' is false.
SR-B10076 · Issue 281632
Save and Cancel use case enabled
Resolved in Pega Version 7.3
When a button was configured with both the "Save" + "Cancel" out-of-the-box actions, the cancel action was performed but the data was not saved to the database. If the button was configured only as a Save action, the save worked as expected but the lock was not released. In order to support a CrossDomain windows use case of enabling an agent to save entered work but cancel out of the case so another another agent can pick up the case and continue with it, the Work-Autoclose function has been modified to write try catch blocks and call doClose when a button is configured with both the "Save" + "Cancel" out-of-the-box actions.
SR-B11600 · Issue 282715
Handling added for dot in visible-when rule
Resolved in Pega Version 7.3
On click of the icon next to the visible-when rule in order to open the rule, the error "Unable to open the rule as Base Class Value is empty" was generated if the 'when' rule of the conditions included a dot. To correct this, the pega_openRuleSP logic has been modified to fall back to the section class from the PRXML when the value of baseClassValue is empty.