SR-B32618 · Issue 276417
Enhancement added to maintain blank properties when using History Snapshots
Resolved in Pega Version 7.3
In HistorySaver, using ClipboardProperty.setValue to save snapshot data for the previous version of the rule had the side effect of stripping blank properties from the clipboard page, and so any rules that rely on these properties would not be restored correctly. To resolve this, an enhancement has been added to specially handle instances History- class and its descendants to serialize blob with EmptyProperties.
SR-B3657 · Issue 274527
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-B3657 · Issue 280763
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-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-C62434 · Issue 410619
Optimize Schema Index Creation updated to use Admin Datasource when available
Resolved in Pega Version 8.1.2
When configured according to the Pega Installation Guide, the SQL Server base user did not have the ALTER privilege enabled on the data schema. The Optimize Schema Index Creation was using the base user datasource "jdbc/PegaRULES" instead of the admin datasource "jdbc/AdminPegaRULES" even though an admin connection was available. This was an oversight during development, and has been fixed by modifying NoDBAUtils.java to use an admin connection if one is available. In addition, a clarification has been added to the UI to alert the user that an optimization job has been scheduled rather than completed.
SR-C70757 · Issue 411814
Added null check to resolve error when using datapage as dropdown source
Resolved in Pega Version 8.1.2
The user application was hanging with the browser console error "Uncaught SyntaxError: Unexpected end of JSON input" when using Dropdown controls with Datapage as a source in conjunction with parameterized datapages to create a cascading second dropdown. This did not happen when using any other data sources for the same control dropdown. This has been resolved by adding a null check at the reloadcell response.
SR-C73131 · Issue 411758
SAML login rule form documentation updated to reflect usage with IDP
Resolved in Pega Version 8.1.2
SAML authentication was not working properly during login. This was traced to the assertion not being signed when SAML responses received from IDP require this, and was due to the check box under SP settings not being applied for POST binding. As a result, a local IDP configuration sent a signed response but not a signed assertion. To clarify this, the label message in the SAML rule form has been modified to read "Reject unsigned response and assertion" and the help documentation has been updated to reflect this usage.
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.
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'.