SR-C45673 · Issue 391239
Behavior changed to use latest metrics when when decisioning metrics cannot consolidate them
Resolved in Pega Version 8.1
Component stats were not showing up on Select Designer Studio ->Decisioning ->Decisions -> Data Flows -> Real Time data flows. The shape metrics on a data flow run appeared to be reset and not processing any records anymore. The problem was that metrics from old nodes (which have become incompatible with the current data flow shapes) were merged in an indeterministic order which caused the old metrics to replace the new metrics on the data flow run progress page. This gave the impression that the data flow shapes were not processing any records anymore. The behavior has now been changed such that when the system merges metrics and cannot consolidate the metrics that are being merged, the latest updated metrics will prevail as opposed to the previous behavior of the 'second' metrics prevailing. In addition, whenever metrics are reset because the data flow has changed or metrics from old nodes cannot be added to the current metrics, a warning will be added to the run to explain the change in metrics of the shapes.
SR-C45786 · Issue 384511
WO details saved to D_pyUserWorkList when finishing assignment offline
Resolved in Pega Version 8.1
When using the mobile app in offline mode, creating a new case and submitting it while offline saved the details in the WO. However, when trying to display the cases which were submitted offline there were details that needed to be shown but that were not updated in the D_pyUserWorkList until after synchronization. This caused WorkList to not show the data updated in newAssignPage and pyWorkPage when moving to the worklist after finishing the case. Previously, the updateWorkJoinProperties method of AssignList_Utils was setting pyCompletedOffline to false by default when it was called from saveWorkAndAssignment method. To ensure the data needed is available, the system will put work and assignment properties into D_pyUSerWorkList item for every finishAssignment by calling updateWorkItemInAssignmentList from saveWorkAndAssignment.
SR-C45807 · Issue 384867
pyLabel will be truncated at 64 characters in the pyAttachApprovalEmail activity
Resolved in Pega Version 8.1
The pyAttachApprovalEmail activity was throwing the below error when trying to process an email response : "Trying to save an invalid page: page is not valid .pyLabel: "Incoming Email Message from [email protected]" is too long, maximum length allowed is 64"This was due to the maximum length restriction on the field pyLabel: in step 2 of activity, the pyLabel was set to ""Incoming Email Message from " + Param.EmailFrom", and the pyLabel restriction of 64 characters generated the error while saving the rule. To handle this case, the pyLabel value will be truncated at 64 characters before saving the Data-Corr-Email instance.
SR-C45809 · Issue 386541
Age calculation declare expression fires correctly the first time the input changes
Resolved in Pega Version 8.1
When using a Date control field with display mode as drop-down lists with a declare expression for calculating the age whenever input changes, the age was not being calculated the first time the field was changed. Subsequent changes worked as expected. If the display mode was textinput + calendar in that scenario, the declare expression fired every time. This was traced to the hidden input missing the onchange handler to trigger calculateExpressions, and has been corrected by attaching the validation function using validation_validateFromUIEvent in 2 methods: handleDPDropdowns and populateSubmitableField.
SR-C45846 · Issue 391842
Improved handling for parsing multiple formats of DateTime
Resolved in Pega Version 8.1
In order to further correct an issue with DateTime formats, the system will now use the parseAsDateTime and parseAsDate functions to properly handle the parsing of the date and date time values. The Pega format will be tried first, and if that doesn't work then the UTF formats will be used. If there is still an issue, the system will call back on the original parseAsXSDDateTime/Date which should catch all cases. An exception will no longer be thrown until after all parsing methods are tried.
SR-C46216 · Issue 390637
how Subcase checkbox behavior corrected
Resolved in Pega Version 8.1
When the Show Subcase checkbox in Audit tab was unchecked, the child case history was displayed when it should not have been. This was caused by the List view not being filtered out to remove sub case data when the checkbox was invoked; to correct it the system will call LV pyWorkAttachmentList to get attachments for the parent only in the initial load, then will call another LV pyCoverAllAttachmentList to get parent and child attachments if Show Subcase is checked.
SR-C46283 · Issue 385488
Documentation update to clarify schema names should be all lower case
Resolved in Pega Version 8.1
When installing onto a system with a PostgreSQL database, the install script failed if the schema names had capitals in them, showing "ERROR: schema "pegadata" does not exist". This was due to the mixed case schema name being altered to all lowercase, so calls to the database fail due to the mismatch. In order to clarify the input needed, the PostgreSQL topic in the documentation has been updated to say : “Enter the schema name in all lowercase letters. PostgreSQL requires that schema names are all lowercase. Enter the schema name only in lowercase letters without quotation marks, or the deployment might not be successful.”
SR-C46503 · Issue 386009
Added null value handling for Date/Time
Resolved in Pega Version 8.1
A null pointer exception when trying to Save an empty record into a Date/Time Field. To resolve this, empty string value handling has been added for the date/datetime/time property in both CSV and JSON files, and a more informative exception message has been added for situations when the date can not be parsed.
SR-C46720 · Issue 386889
Back button in mobile screen flow retains entered data
Resolved in Pega Version 8.1
When navigating to an earlier step using Back Button on ScreenFlow via Mobile App, data was lost.This was traced to a call mismatch: rather than using getElementsByName, the system was calling a function that used getElementByName. This caused an exception and resulted in the form not being properly merged with the work page, leading to data loss. To correct this, the getFormJSON method has been changed to properly use getElementsByName for this function.
SR-C46751 · Issue 389629
Cleanup added to DDS service shutdown
Resolved in Pega Version 8.1
When prpcUtils is executed it starts DSM services in client mode when a DSM node (DDS) in the cluster is running. However, DSM threads do not shut down when the utility class completes, causing the Import task to hang. To prevent this, cleanup implementation has been added to the DDS service shutdown.