SR-B3657 · Issue 285983
SAML authentication enhanced to detect encoded/decoded response
Resolved in Pega Version 7.3
Even though SAML authentication was working as expected, an error message was being logged when the system attempted to process the authentication response as encoded before falling back to process it as decoded. To remove confusion, Fallback has been removed and instead the system will intelligently identify the response as encoded/decoded and handle it appropriately without generating an unnecessary error.
SR-D42583 · Issue 514488
Label of a field is correctly rendered when a section is re-used with a visiblity condition
Resolved in Pega Version 8.1.7
The label of a field was not being rendered/visible when a section with a 'visible when' condition was re-used in different Page Contexts. The label was displayed correctly if 'Run visibility condition on client' was checked. As part of performance improvements made in a previous version, label generation was moved under the dlcellvisibility flag. Because of this, if a section was re-used at multiple places with different contexts and one place had visibility false and another had visibility true, the labels were not getting generated for the visible section. To resolve this, Label Generation has been moved out of dlcellVisibility to ensure label metadata will always be generated. Updated performance improvements have been made instead by way of a DSS setting (generateCellMetadata) so that when generateCellMetadata is true, the label generation will honor dlcellvisibility to generate the label metadata.
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-D39956 · Issue 511639
Corrected method IF use with shortcut function
Resolved in Pega Version 8.1.7
After upgrade, method IF was not working as expected when used in an expression like "@if(.totalorders_120days>0,(.remakeorders_120days/.totalorders_120days)<0.3,false)". This was caused by a missed use case for the combination of an exception-generating function in combination with a shortcut function (i.e. ternary, and, or), and has been resolved.
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.
SR-B13418 · Issue 283237
Attachments removed when work object withdrawn
Resolved in Pega Version 7.3
After adding an attachment and then withdrawing the case, the unneeded attachments were still being stored in the attachments section until a refresh was performed. This was traced to code in the UpdateAndDeleteAssignments activity that appended the target page rather than replacing. This has been modified to ensure attachments are eliminated when the status of a work object is moved to 'Withdraw'.