INC-151716 · Issue 618440
Resolved Screenflow overflow
Resolved in Pega Version 8.4.4
Screenflow bread crumbs were overflowing out of the action area when more than 10 assignments were configured. An error in the console indicated the navigation.navigate function was not defined. This behavior was observed in general when a screenflow was called from another screenflow and 'enable navigation links' was set on all assignments in the screenflows, and the issue has been resolved by updating the implementation.
INC-143820 · Issue 603639
Handling added for App Studio Null pointer exception
Resolved in Pega Version 8.4.4
After adding a property as a relevant record so that it can be used in App Studio development, not all of the properties appeared in App studio. This was traced to an unhandled null pointed exception, and has been resolved.
INC-151858 · Issue 610351
Updated currency decimal precision
Resolved in Pega Version 8.4.4
Hungarian and Taiwanese currencies were previously hardcoded to use zero decimal precision. In order to be compliant with the current ISO-4217 standards, these currencies have been updated to be precise to two decimal places.
INC-146424 · Issue 602898
Keyboard users can select DSS records with enter key
Resolved in Pega Version 8.4.4
Keyboard accessible users were not able to select DSS records using the keyboard. This has been resolved by adding the action "Open selected item to the Enter event for the section pzViewInstances.
INC-142930 · Issue 600770
Email history will be stripped from case replies
Resolved in Pega Version 8.4.4
When sending an email reply to a case, the entire email history (all previous emails in the email chain) was attached to the case as part of the reply.To resolve this, updates have been made so the system will strip history only when it's a follow-up mail. In addition, an issue with duplicate attachments has been corrected, and attachments from trailing mail will not be copied to a new post.
INC-148237 · Issue 605848
Autocomplete markup handles control format style names with spaces
Resolved in Pega Version 8.4.4
After creating the format 'Standard Gray Background' in the skin rule to change the back-ground color for an auto_complete field and using it in a presentation tab for Control-format input, the field was not updated with the background color as expected. This was due to the Autocomplete control only replacing the first space in the control format name with underscore ( _ ), causing the formatting to not be accepted. While there was a workaround of providing a name without spaces or using a name with only a single space, this has now been resolved by modifying the autocomplete markup generation so all the spaces in a control format style name are replaced instead of only the first space.
INC-153415 · Issue 616711
On click outside grid record will be saved
Resolved in Pega Version 8.4.4
When a record was added by copying a previous record, the new record was not saved if there was a click outside the grid. This has been resolved.
SR-C80076 · Issue 419094
Added check before deleting pxObjClass to avoid agent runtime exceptions
Resolved in Pega Version 8.1.3
When the rule was not assembled, agents were failing with exceptions. During label control assembly execution, standard attributes for label assembly including pxObjClass are removed from the cell page. There is a catch for the exception during cell trimming for browser requests, but the customer agent was failing because UnmodifiablePropertyException is a runtime exception that sets the step status to fail. This has been fixed by adding a check when attempting to delete a property from Clipboard page: if the property is pxObjClass, it will not be deleted.
INC-135015 · Issue 591980
Handling added for overriding questions rules
Resolved in Pega Version 8.4.4
After overriding questions rules and then upgrading/validating Question Groups, questions were not shown. It was necessary to manually edit, save, and refresh for the questions to appear, affecting mainly Rule-PegaQ-QuestionGroup rules. This was traced to missing handling for this usecase. The commit was added in Revalidate and Save, which was committing different data because the upgraded data was not copied back to step page being used. Due to this, the commit in BulkValidateSave was overriding the changes done in the pzUpgradeSurveyInstance activity, and the survey upgrade was failing. To support this use, Page-Copy has been added to pzUpgradeSurveyInstance after the pzSaveSurveyInstance call step to copy the updated data to the step page which will later be committed by BulkValidateSave during revalidate and save.
SR-C77533 · Issue 416618
Added null check for ApprovalFlowName in pre-processing activity of "pzApprovalPreProcessing"
Resolved in Pega Version 8.1.3
When a "pyApproval" flow action was configured in one of the assignments of a case Type for Approval action by the manager, the error message "The Flow Action pre-processing activity pzApprovalPreProcessing failed: The reference .pxFlow().pyFlowParameters.pyApprovalSectionName is not valid. Reason: Empty subscripts are not valid for the element : pxFlow" appeared when the Approval section was displayed. To correct this, a null check has been added for an empty ApprovalFlowName in step 1's second property set and transition step.