SR-C80050 · Issue 417605
Schema name made consistent for DDL generation
Resolved in Pega Version 8.3
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-C74677 · Issue 418338
ADM pulse timing changed to inprove performance on very large clusters
Resolved in Pega Version 8.3
ADM uses a pulse that checks if any models need to be updated. This uses a Cassandra query which has no "where" clause, causing poor performance for very large clusters. For immediate relief of this issue, the pulse configuration has been updated to increase the timing from 30 to 300 seconds so it fires less often. Model updates typically happen every x hours and often the pulse will not detect any models that would need to be updated. Further improvements in this process will be available in a future release.
SR-C76995 · Issue 418701
CSV import for delete date values will be formatted before row processing
Resolved in Pega Version 8.3
In order to support using CSV import for delete purposes, date/time class keys will be formatted before processing the row.
SR-C75205 · Issue 418808
Invalid text entry in Date control field now returns current timestamp
Resolved in Pega Version 8.3
Inconsistent behavior was seen between entering an invalid date in numeric vs text format. Entering an invalid date in number format resulted in the system replacing the entered value with the text “Invalid date”. Entering an invalid date in text format caused the system to retain the value and not show a validation error. This has been corrected by modifying the date/time formatting for both text and numerical input to return the timestamp in case the entered value is incorrect.
SR-C80076 · Issue 419093
Added check before deleting pxObjClass to avoid agent runtime exceptions
Resolved in Pega Version 8.3
When the rule was not assembled, agents were failing with exceptions. During label control assembly execution, standard attributes for label assembly including pxObjClass are removed from the cell page. There is a catch for the exception during cell trimming for browser requests, but the customer agent was failing because UnmodifiablePropertyException is a runtime exception that sets the step status to fail. This has been fixed by adding a check when attempting to delete a property from Clipboard page: if the property is pxObjClass, it will not be deleted.
SR-C66675 · Issue 419142
5 cross-site scripting security added to Multiselect controls
Resolved in Pega Version 8.3
Multiselect controls have been updated for greater cross-site scripting security.
SR-C80958 · Issue 419199
Added check for appname to avoid HarnessFail execution error on Mashup reload
Resolved in Pega Version 8.3
A HarnessFail execution error was occurring on Mashup reload. This was caused by the appname being appended twice during the reload, and has been resolved by adding a check to the _finalizeNavURL method in the PegaCompositeGadgetMgr.js file to remove appName if it is present in the URL to prevent duplication.
SR-C63789 · Issue 419236
Corrected double call to defer load activity on composite
Resolved in Pega Version 8.3
When specifying a pre-activity in defer load, the pre-activity was getting called twice when that dynamic layout was in a Layout group. This has been corrected.
SR-C75823 · Issue 419474
DSS added to handle Amazon S3 socket timeout exception
Resolved in Pega Version 8.3
In Amazon S3, a timeout exception occurs when the socket is idle more than the default timeout value (50 seconds). In order to compensate for this, an enhancement has been added which provides a DSS “repository/s3sockettimeout” where the s3 socket timeout can be specified in milliseconds. When a value is provided to this DSS, it will override the default value of 50 seconds.
SR-C29160 · Issue 419494
Performance improvements made on bulk actions
Resolved in Pega Version 8.3
Latency was observed when performing transfer Bulk Action on cases. Investigation showed that the "Select Action" button in pzBulkProcessingActionSection contained a refresh other section action for the pzBulkProcessingCheckbox section that executed on each row of the grid rendered. This refresh is not needed as the "Post value" action will take care of posting the selected checkbox data to clipboard, so it has been removed to resolve the performance issue.