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-B36632 · Issue 292416
Improved logic for cloned operators and workpools
Resolved in Pega Version 7.3
The workpools available in a new application were not updating correctly due to a missed use case related to multiple cloned operators and the respective multiple cloned workpools being added to the built-on operator. To better handle this scenario, the following changes have been implemented: 1) If the workpool originally listed on the access group to be cloned derives from a class in the list of classes to be created, then the entry will be updated with the new work pool name. 2) If the workpool originally listed on the access group to be cloned does NOT derive from a class in the list of classes to be created, then the entry will be removed from the new access group. (for example, if the user selected no case types and the old access group had multiple work pools listed, then none of those workpools will be present on the new access group since those work pools were not cloned). 3) If an entry was previously marked as the default work pool, the newly cloned workpool will be marked as the default workpool. (This is a change in logic, as previously the access group always used the default work pool [Org-App-Work]). 4) If the previous default work pool was not cloned to the new application (based on case type selection), then the access group's default workpool will be the first in the list. 5) If there were no work pools present in the list, then the standard Org-App-Work classgroup that is always created as part of the new application process will be added and made the default.
SR-B36632 · Issue 294145
Improved logic for cloned operators and workpools
Resolved in Pega Version 7.3
The workpools available in a new application were not updating correctly due to a missed use case related to multiple cloned operators and the respective multiple cloned workpools being added to the built-on operator. To better handle this scenario, the following changes have been implemented: 1) If the workpool originally listed on the access group to be cloned derives from a class in the list of classes to be created, then the entry will be updated with the new work pool name. 2) If the workpool originally listed on the access group to be cloned does NOT derive from a class in the list of classes to be created, then the entry will be removed from the new access group. (for example, if the user selected no case types and the old access group had multiple work pools listed, then none of those workpools will be present on the new access group since those work pools were not cloned). 3) If an entry was previously marked as the default work pool, the newly cloned workpool will be marked as the default workpool. (This is a change in logic, as previously the access group always used the default work pool [Org-App-Work]). 4) If the previous default work pool was not cloned to the new application (based on case type selection), then the access group's default workpool will be the first in the list. 5) If there were no work pools present in the list, then the standard Org-App-Work classgroup that is always created as part of the new application process will be added and made the default.
SR-B36909 · Issue 301697
JSON API added
Resolved in Pega Version 7.3
An enhancement has been added via an API to create JSON from clipboard page. This API will get the JSON of the clipboard page, expand Autopopulate Properties, and return Dates and Times in ISO format.
SR-B36948 · Issue 296463
Dynamic UI supports repeating grid sourced from Page List
Resolved in Pega Version 7.3
After creating and running a case, clicking on the "Edit Details" option from Other Actions Menu did not display the section containing a repeating grid sourced from a Page List. This was due to the final rule activity "pzdynamicuisetupfields" not considering the case of Page List while configuring the dynamic UI, and it has been updated to properly propagate the values.
SR-B36948 · Issue 298094
Dynamic UI supports repeating grid sourced from Page List
Resolved in Pega Version 7.3
After creating and running a case, clicking on the "Edit Details" option from Other Actions Menu did not display the section containing a repeating grid sourced from a Page List. This was due to the final rule activity "pzdynamicuisetupfields" not considering the case of Page List while configuring the dynamic UI, and it has been updated to properly propagate the values.
SR-B37115 · Issue 293959
PegaUnits bulk testing updated
Resolved in Pega Version 7.3
AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.
SR-B37115 · Issue 286705
PegaUnits bulk testing updated
Resolved in Pega Version 7.3
AUT test cases were failing while running in bulk, though running a single unit worked as expected. This was found to be a conflict with the way a test case uses a current parameter page from the start of execution to end of execution and then passes it to the next test; if there are two data page test cases where one is configured to have a non-blank value for a given parameter while the second one has a blank value for same parameter, the second test unexpectedly encounters the non-blank value. To resolve this, the code has been modified to reset the value of only RUT params before set up is called, so that every test case behaves truly independently.