SR-C45276 · Issue 383709
Placeholder set value shows in accessibility mode dropdown
Resolved in Pega Version 8.1
When a drop down was configured with a placeholder in accessibility mode, the set value was not working. This was an issue with the handling of the onchange event in the accessibility framework, and code has been added to resolve this.
SR-C45293 · Issue 386089
Improved XML security for POST request processing
Resolved in Pega Version 8.1
Updates have been made to resolve a potential security issue involving missing XML validation when processing a POST request.
SR-C45529 · Issue 387642
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.
SR-C45602 · Issue 384972
Avoid Generation flag will default to true for single case runs to avoid excessive data class hierarchy validation
Resolved in Pega Version 8.1
System slowness was traced to an excessive number of calls to the DDS service “getClusteState()” method. This issue was caused by an unusual usage of class hierarchy, where XXX-Data-Customer class had data flow and activity defined, then an activity instantiated a child class (e.g. XXX-Data-Customer-NBA) and tried to load an instance of this class using the data flow browse by keys operation. In this case, data flow had to do additional validation to make sure all data sets used in the data flow are compatible with the child class, and it was this validation that caused the reported issue. To better handle this use case, by default the avoid generation flag will be set to true for single case runs.
SR-C45610 · Issue 384507
Resolved screen flicker during busy indicator
Resolved in Pega Version 8.1
When using the column layout in CPMPerformIncludes, the contents flickered and shifted to the left while the busy indicator was displayed (performing actions like interaction switch, service case closure etc.). This was caused by the column layout main getting resized while the sidebar is hidden, and a check has been added to pzpega_ui_doc_lifecycle that will avoid resizing in case of a hidden element.
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.