SR-C38060 · Issue 385590
Timing resolved so pxDateTime control accepts Pega Date Time value on the first input
Resolved in Pega Version 8.1
In Pega Mobile android client, pxDateTime that was displayed within a dateTime field using a calendar selector was throwing an error on the first encounter if the field value was already filled using the Pega DateTime format of "yyyymmddThhmmss.SSS zzz". The console error from the templating engine was: "The specified value "20180605T103556.398 CDT" does not conform to the required format. The format is "yyyy-MM-ddThh:mm" followed by optional ":ss" or ":ss.SSS". " This was traced to the handleNativeDate function in pzpega_control_datePicker.js file executing "pega.u.d.CalendarUtil.fireClientEvents(hiddenInput);" two times. Before firing the first event "onchangehandler" returned null, so the 'if' condition executed to true and fireClientEvents was again getting executed. Because there was no delay in between these executions, the second event was getting executed while the first event was still in progress, causing the DOM value of the property to not be properly set before validation was getting triggered during the second invocation. This has been resolved.
SR-C38087 · Issue 386087
Join order fixed to improve Cache SQL Statement performance
Resolved in Pega Version 8.1
The Pega Cache SQL Statement was taking much longer than normal to run when SQLServer 2012 was used. DBA Analysis of the issue showed that Full INDEX Scans were occurring, doubling/tripling the amount of time to respond to the PRPC instance. This was caused by an incorrect join order, and has been fixed.
SR-C38293 · Issue 379308
Added explicit cleanup of non-serializable objects in the Connect-SOAP ParameterPage
Resolved in Pega Version 8.1
In investigating an application continuously logging error messages for Serialization, it was found that Connect-SOAP execution leaves non-serializable objects in the ParameterPage, which in-turn caused this the error logging upon requestor passivation. To resolve this, code has been added to remove the pyServiceClient, soapHdr, and activityParamPage parameters from the ParameterPage after use.
SR-C38299 · Issue 377521
Handling added for data flow thread hang
Resolved in Pega Version 8.1
If there were errors on some partitions, the data flow was hanging. Handling has now been added for system failures in inputSource so the flow will complete and report errors.
SR-C38355 · Issue 376510
"403 - Forbidden" error replaced with "404 - Not Found" for better security
Resolved in Pega Version 8.1
Previously, invalid path information sent for a static content request resulted in a "403 - Forbidden" response that revealed the existence of the directory, even though access is not allowed. For better security, a "404 - Not Found" response status code will be issued for a forbidden resource.
SR-C38450 · Issue 379292
StartupDelay parameter added to allow spacing threads to improve database performance
Resolved in Pega Version 8.1
When starting a data flow with DBDataSet as source shape, all data flow nodes (threads) started hitting the Database at the same time, overloading the system and causing delays for other requests. To resolve this, a new RunOption has been added; pyStartupDelay will add a delay between each thread starting. For example, when setting the delay to 2 seconds, thread 1 will start immediately, thread 2 will start after 2 seconds, thread 3 after 4 seconds etc. In this fashion only one thread at the time will start hitting the DB in a distributed context.
SR-C38510 · Issue 383350
Next >> buttons localized for French
Resolved in Pega Version 8.1
Next >> buttons were not getting translated when using the French locale. This has been corrected by updating the pyButtonLabel parameter.
SR-C38824 · Issue 383747
Fixed warning issue for opening a harness that's already open
Resolved in Pega Version 8.1
When launching the harness using Harness action, there was no warning displayed when trying to open the harness which is already open. This was caused by an incorrect parameter being passed to the "showConflictDialog" method call, and has been corrected by modifying the pzpega_ui_dynamiccontainer.js file "display" method to pass "viewHost" variable instead of "hostName" as the first parameter to the "showConflictDialog" method call.
SR-C38825 · Issue 374870
Corrected bulk actions 'select all' behavior
Resolved in Pega Version 8.1
BulkActions:"Select All" was not considering records in all of the pages. This has been corrected.
SR-C38825 · Issue 377452
Corrected bulk actions 'select all' behavior
Resolved in Pega Version 8.1
BulkActions:"Select All" was not considering records in all of the pages. This has been corrected.