INC-155469 · Issue 616912
Attach Documents Control updated for busy indicator timing
Resolved in Pega Version 8.4.4
When using the standard control - Attach content - to attach documents for processing in the application, selecting multiple files for upload and then clicking on the attach button before the busy indicator started resulted in not all files being uploaded. Investigation showed that the busy indicator was not set to display as soon as the attachments were added, giving an opportunity to click "Attach" before all the documents could be successfully added to the process. As part of the resolution for this issue, the busy indicator will be displayed immediately upon file selection.
INC-143461 · Issue 601842
Updated JSON DT nested page property handling
Resolved in Pega Version 8.4.4
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
INC-144978 · Issue 600591
Updated JSON DT nested page property handling
Resolved in Pega Version 8.4.4
In a JSON data transform, when using an "Update page" step on a single-page property, as a child step of an "Append and map to" step where a pagelist property is given, the pagelist was populated with only one result but the single-page property was treated like a pagelist and received multiple results. This has been resolved by updating the ClipboardJSONDeserializer implementation and downstream abstractions to support "clipboard only" relations as properties in nested PageLists.
SR-C74176 · Issue 419497
AdminUser login corrected for WebLogic
Resolved in Pega Version 8.1.3
After a successful deployment of Pega on WebLogic 12c Application Server, the server started up without problem and the login page appeared as expected. When attempting to login to the application using the administrator account, the login failed and displayed the error "java.lang.IllegalArgumentException: Header:Location Cannot contain CRLF Charcter" in the browser. This as traced to the URL not being generated correctly due to the padding in the encoding rejecting any CRLF character in the URL, and has been corrected.
INC-141387 · Issue 612826
Autocomplete/autopopulate in table works properly with keyboard
Resolved in Pega Version 8.4.4
When two autocompletes in a table (two separate columns) were sourced by different properties within the same data-page, clicking to select a “reason-code” in the first autocomplete column correctly populated the corresponding “reason description” in the second column autocomplete. However, when using configured keyboard presses on the auto complete with post value and data transform actions (enter-key, tab-key, and on change), selecting from the auto-complete list and pressing enter or tab to select the item populated the second column as expected but the first column auto-complete showed the selected code for a moment and then was cleared. This as traced to the associated property set value executing after all associated properties setvalue actions were completed, and has been resolved.
SR-C77625 · Issue 415580
Cassandra retry policy enanhancement
Resolved in Pega Version 8.1.3
When configuring the datastax client for Cassandra, it is possible to specify a retry policy. By default the DefaultRetryPolicy is used. While a retry was always attempted on client timeout with this retry policy, a retry on server timeout was only attempted in a limited set of circumstances. This code indicates that for a retry: - The number of received responses is at least the same as the number of required responses - The retry will be done to the same node, not a new node This use makes sense if consistency is set to QUORUM or higher, but it does not make sense for consistency ONE. To resolve this, a new retry policy has been added which will retry in this scenario a configurable number of times. The retry policy and the retry count will be controlled by prconfig settings: prconfig/dnode/cassandra_custom_retry_policy/default - True/False (default: False) prconfig/dnode/cassandra_custom_retry_policy/retryCount/default - >= 0 (default:1)
INC-148657 · Issue 607572
Check added for invalid operatorID set by autopopulate
Resolved in Pega Version 8.4.4
When an SLA rule attached email reminders, the Link-Attachment table saved the creating operator as System. Upon opening the case perform in Cosmos, all attachments were shown in the utility area and the system tried to show the user name using the pyUserDetails linked property, causing the assignment system to generate a "System is not valid operator" error and the case open failed. To resolve this, the system has been updated to avoid setting the error message on Datapage if an invalid operatorid is passed.
SR-C80050 · Issue 417604
Schema name made consistent for DDL generation
Resolved in Pega Version 8.1.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.
INC-125633 · Issue 589575
Oracle performance improvement
Resolved in Pega Version 8.4.4
Poor performance was seen when importing a RAP with schemas using Oracle. To resolve this, an update has been made which will set the Oracle tuning parameter at the session level by altering the setting "_OPTIMIZER_PUSH_PRED_COST_BASED"=false before the SMA query involving all_constraints. The setting will be returned to true after the execution of the SMA query. This is controlled through the prconfig setting '"database/performance/smaqueryperformanceenabled" which defaults to true so the setting and unsetting of the Oracle parameter is automatic.
INC-150633 · Issue 614512
Optimizing helper class enhanced to handle external databases
Resolved in Pega Version 8.4.4
Running a BIX extract that included a manifest for a target database was resulting in a null pointer exception for the manifest extraction. Attempting to generate the DDL for the manifest table also failed. This was traced to an issue with the helper class using a hardcoded default database for forming the queries, causing it to ignore the database config/DADN/prconfig for the Oracle database and form a query using the PegaRules' database credentials. This only occurred when trying to do external database operations on a different database platform; Oracle PegaRules worked as expected with an Oracle external database and Postgres Pegarules worked with a Postgres external database, but mixing Postgres PegaRules and an Oracle external database would result in the Null pointer exception. To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".