SR-C37540 · Issue 390176
Fixed Recent Work gadget display of work objects
Resolved in Pega Version 8.1
After upgrade, the work object in the Recent category was showing as Undefined when rendering the recent work gadget (Launch User/Manger portal, search for the Work ID). This has been resolved by defining the PegaWorkData JavaScript function in RecentWorkGadget non-auto control and using PegaWorkData instead of FormData.
SR-C37748 · Issue 379478
Connect-SOAP 'Request Only' call maps SOAP async call faults
Resolved in Pega Version 8.1
When a failure occurs on a Connect-SOAP configured as 'Request Only' with asynchronous processing, the failure was not logged or copied to the clipboard. This was standard behavior for Request-Only, but did not account for asynchronous calls where the status code was not correct for failed calls. This has been updated to correctly register the failed calls.
SR-C37763 · Issue 377796
UNIX JAR paths documentation correction
Resolved in Pega Version 8.1
The documentation for prconfig/compiler/defaultPaths has been corrected as follows: "For UNIX systems, separate the JAR files with a colon."
SR-C37810 · Issue 381739
Agent management made more resilient against DB connection errors
Resolved in Pega Version 8.1
Intermittently after a database interruption occurred, agents would end up in a state where they did not run. When viewed via SMA they appeared to be running, but the next runtime was blank and the agent did not execute. Attempts to stop/restart an affected agent yielded an error, but restarting the system put the agents back into a operable state. This was a corner case caused by a DB connectivity issue where agents were first being stopped and then attempts to instantiate AgentNotification() also failed due to the DB connectivity issue. To resolve this, AgentNotification will be instantiated during AgentQueue creation itself so it will remain available. All exceptions /errors in AgentNotification will be logged.
SR-C38054 · Issue 380396
Improved validation and handling for Cassandra data set flows
Resolved in Pega Version 8.1
When using a Data flow which read from a file and wrote to a Cassandra data set, the successful records were not written to the Data set if there were any errors. In addition, when all records failed the run stat's '# Failed records' displayed the number of batches, not the actual number of records. This was caused by a condition where if serialization fails it throws a single exception for the whole batch instead of a batch exception, and by default there was a maximum of 250 records per batch. This has been corrected by setting the system to keep the failure threshold to 100,000 and validate that all the failed number of records is correct, then re-process the failed records and check if the dataflow still shows all the failure records.
SR-C38059 · Issue 376811
Improved logging and resilience with S3 bucket configurations
Resolved in Pega Version 8.1
The S3 bucket configuration through DSS did not handle error conditions well, leading to a situation where the engine would not start if the S3 bucket is not configured correctly (e.g., permission setup on the AWS side). The code has now been updated to add better logging around running a repository with DSS System, and startup is no longer stopped if a repository fails to register.
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.