SR-C80050 · Issue 417603
Schema name made consistent for DDL generation
Resolved in Pega Version 8.2
A platform upgrade failed if there were application schemas configured with a table configuration that specified a schema other than the rules schema. This was an issue caused by the generated DDL having the incorrect schema name for the table due to the name being hard-coded in the Data-Admin-DB-Table entry definition. The system was using this schema name to find the table and generate the correct changes, but the SQL statement used the table from the database connection instead of the override. When the XML that represents the difference between the "source" and "target" state is generated, the system is supposed to replace the schema name with the target schema name. However, if the source schema name is blank that step was skipped in order to defer to the connection for shipped tables. In order to ensure that the system can generate the correct DDL and complete the upgrade, the system will now always replace the schema name regardless of the source or target value.
SR-C79731 · Issue 417957
TestID remains unique in grids
Resolved in Pega Version 8.2
To support automated testing, testID will maintain unique IDs for grid rows and RDL rows.
SR-C81262 · Issue 418056
Failed delete instances now correctly logged
Resolved in Pega Version 8.2
After configuring rule-access-when on delete instances for a data class, the failed instances were not shown in the error log file. This has been resolved by correcting the path of the error CSV file in the pzDeleteRecords activity.
SR-C77145 · Issue 418196
REST endoint check added to correct Bulk check-in error
Resolved in Pega Version 8.2
After integrating Agile Studio into a development instance application, trying to perform a Bulk check-in of the rules without selecting a task ID in the "Work item to associate" drop down list failed and generated an error in the logs. This was caused by an incorrect condition validation before making the REST call, and has been addressed by checking whether the REST endpoint is blank or not.
SR-C81946 · Issue 418710
Maintenance function operator ID will not persist in the system
Resolved in Pega Version 8.2
After a hotfix maintenance activity, an audit revealed that an extra operator created for the purpose called CloudMaintenanceUser persisted in the system. The code has now been updated to bypass saving operator records marked with pzPersistOperator="false" on user initialization; the CloudMaintenanceUser will be created with this property set to false, and updating this operator will be skipped during unauthentication.
SR-C74967 · Issue 419159
Delete and change comparisons updated to support multi-tenant environments with shared classes
Resolved in Pega Version 8.2
When creating tenants in paex49, many of the rules did not actually complete importing into the tenant, and when creating new cases, some pages were getting instantiated as classless. This issue was seen only in multi-tenant environments when the same class was present in multiple tenants. Given a Pega class present in multiple tenants, making changes to that class for one tenant triggered invalidation of the dictionary cache that maintains a map with class name + tenant id as key and ClassInfo object as value because of the comparison method used. As a result, dictionary invalidation from one tenant could clear the entry of other tenant and cause the current tenant cache entry to become stale. To address this issue, the system has been updated to remove an entry for a class in tenant context based on key.
SR-C81857 · Issue 420239
Enhancement added to support dropdown with page list property
Resolved in Pega Version 8.2
To enable the use of a dropdown control with a property of type page list, an enhancement has been added to support a clipboard page for drop down and autocomplete.
SR-C86213 · Issue 411187
Corrected PRAuth URL handling for sessions on restarted nodes
Resolved in Pega Version 8.2
If a user session was in progress and the node restarted, attempting to refresh the session when the node came back up was not working. Launching a new browser session cleared the problem. A trace showed that the Authentication Selector screen was not loading because the PRAuth URL redirection was going into an infinite loop, and this has been corrected.
SR-C75496 · Issue 413924
50 count limitation removed from application list export
Resolved in Pega Version 8.2
Previously, using Designer Studio -> Application -> Distribution -> Export to export the list of applications limited the results to 50. This number was hardcoded in the page size count setting for the Report Definition. In order to better support complex installations, this limit has been lifted.
SR-C70943 · Issue 409363
Dropdown sourced from data pages or clipboard pages working for all browsers
Resolved in Pega Version 8.2
After working to resolve a dropdown issue with Edge browsers, some other dropdowns sourced from a data page or clipboard page were failing to load. This was caused by the dpparams parameter being encoded so that the proper JSON was not retrieved, and has been fixed by modifying the system to decode it before passing the postdata.