SR-A9198 · Issue 218533
Text retrieval for deprecated "Query" button updated for universal browser support
Resolved in Pega Version 7.2
The Firefox popup window provided by the Product rule when querying "Individual Instances to Include" failed to transpose the selected rule information back into the Product ruleform when the OK button was clicked. This was due to the use of the deprecated "Query" button, which does not have support for all browsers, to launch the ListView. To handle this, the node text retrieval method in DataInstancesQueryScript has been updated to use the 'textContent' function (compatible with all browsers) instead of the previous 'innerText'.
SR-A10839 · Issue 222017
Added handling for null rollback info in hotfix autocommit
Resolved in Pega Version 7.2
If AutoCommit was selected while installing a hotfix, the auto-commit would fail and leave the hotfix in an Uncommitted state if there were dependent hotfixes where changes were covered by the parent and the child was superseded after installing the parent. Manual commitment of the hotfix worked as expected. This was an edge case where the older hotfix did not get rollback information saved since its components were already installed or superseded, and AutoCommit has been updated to handle this missing information.
SR-A10327 · Issue 222830
Upgrade Assistant enhanced to better resume interrupted process
Resolved in Pega Version 7.2
If the system suffered a crash during upgrade, IUA was incorrectly identifying the DB as having completed the upgrade and would import outstanding rules based on the perceived Database BLOB version. This led to a storage-type mismatch between Prod and all lower environments, and BIX jobs would fail due to not being upgraded. An enhancement has been added to the Upgrade Assistant to correctly resume an interrupted upgrade process.
SR-A12287 · Issue 223279
Alter Script generates correct SQL for Oracle db
Resolved in Pega Version 7.2
During installation, an incorrect Alter Script was being generated while importing the JAR file due to a missing check on the 'required' XML attribute for dbtype Oracle to decide whether it should be null or not null. This has been corrected to honor the 'required' attribute and accordingly the generated SQL will be appended with null/not null string.
SR-A12687 · Issue 226506
Skimming logic corrected
Resolved in Pega Version 7.2
The skimming logic (PegaRULESMove_Skimming_Query) has been updated to correctly repopulate the query page in order to return a more accurate rules count.
SR-A2733 · Issue 220049
Migration process handles underlying varchar CHAR
Resolved in Pega Version 7.2
Handling for CHAR length semantics has been added for imports of rule schema to support Oracle varchar2 columns, and the import/export will correctly deal with the circumstanced columns of CASETYPEVERSION and PXREFOBJECTCLASS.
SR-C98068 · Issue 483991
Installer files updated with class loader conflict resolution assistance
Resolved in Pega Version 8.2.4
When sending emails with attachments, errors were observed relating to a loader constraint violation indicating that when resolving interface method, the class loader of the current class and the class loader for the method's defining class had different Class objects for the type used in the signature. The resolution for this requires user configuration of the app server, and the following files for the install guide have been updated with the appropriate information:Deployment-guides-dita/install.ditamap Deployment-guides-dita/Content/Topics/app-server-config/creating-jdbc-driver-module-jboss-tsk.dita Deployment-guides-dita/Content/Topics/app-server-config/delegating-javax-activation-to-JRE-loader-tsk.dita
SR-D28460 · Issue 509365
Added timeout handling for non-PRAuth servlets
Resolved in Pega Version 8.2.4
After logging in via external authentication service (SAML Single Sign On) and setting up a timeout in the access group RuleForm, when the user performed any action and the server identified the request to be timed-out, it was expected that a SAML request would be sent from the browser to the external Authentication Server (referred as IDP) and the flow would proceed from there. This worked as expected for a non-AJAX request. To resolve this, handling has been added for timeout when using non-PRAuth authentication services.
SR-D29127 · Issue 506863
SAML data pages restored after passivation
Resolved in Pega Version 8.2.4
If login used SAML SSO, resuming the session after passivation resulted in missing or empty data pages when using an SAP integration with Pega Cloud. This was traced to a security change that modified the D_SAMLAssertionDataPage and D_SamlSsoLoginInfo data pages as readonly, causing them to not be passivated under these conditions. To resolve this, the data pages have been made editable so they will be restored as expected. This change also resolves any difficulty with SAML logoff activities in conjunction with SAP and Pega Cloud.
SR-D37872 · Issue 507341
prproductmigration build.gradle updated for new mime4j asset name
Resolved in Pega Version 8.2.4
While running the getMigrationLog for ProductMigration script provided in the Pega 8.2.2 media files, errors appeared referencing "NoClassDefFoundErrors when running getLogs". This was caused by the referenced class not being found on the classpath: the version of the included jar did not include the class needed due to Praxiom's default version being updated to use a new version of mime4j that required an asset name change. To resolve this, the mime4j asset name in prproductmigration build.gradle has been updated to pick up the correct version of the dependency for Praxiom.