INC-154680 · Issue 619027
Moment timezone library update
Resolved in Pega Version 8.4.4
In order to reflect updates such as Brazil discontinuing DST time, the moment timezone libraries have been updated to the latest available version.
INC-154855 · Issue 616002
Updated expression handling when not using client side validation
Resolved in Pega Version 8.4.4
After upgrade, a declare expression used to calculate the end date when creating a schedule case was not populating the result. This was traced to a missed use case for evaluating expressions when 'Enable client side validation' is unchecked, and has been resolved.
INC-156992 · Issue 619707
Show-stream/html repaired for custom portals
Resolved in Pega Version 8.4.4
After upgrade, show-stream/html in activity was not getting executed properly on custom portals. ShowDesktop was modified in 8.1 for AssociateRequestor implementation. As part of that, the custom portal step was moved to the new activity pzPopulateRequestor which is invoked from ShowDesktop. The JUMP condition in step is exiting the pzPopulateRequestor activity, but not ShowDesktop as was the case in the previous versions. To resolve this, the JUMP condition (.pyDesktopType=="Custom") has been added in ShowDesktop at the pzPopulateRequestor call step.
SR-B66795 · Issue 317118
ConvertAttachmentToPDF Activity deprecated as part of PDM removal
Resolved in Pega Version 8.1
As the Pega Distribution Manager is no longer offered as part of the Pega application, the "ConvertAttachmentToPDF" function previously offered as part of PDM 3.3.5 is now [Withdrawn,Deprecated] from 'Pega-ProCom' & 'Pega-ProcessEngine'
SR-B69359 · Issue 337302
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-B73087 · Issue 343814
Fixed incorrect number formatting application in Spanish locale
Resolved in Pega Version 8.1
Errors were seen for fields having pxCurrency and pxNumber control when using the Spanish locale (es_CR):1. After entering an amount like 917.25 on a field which is configured to refresh section on click/on change, clicking on the field caused the decimal to move and resulted in multiplying the amount by 100 (91725.00) 2. Fields did not allow entering a comma as a decimal delimiter or were stripping the comma. This has been fixed by modifying pzGenerateTextinput assembly to not apply formatting for numbers in some specific locales.
SR-B74459 · Issue 329573
Corrected additional Fork connector
Resolved in Pega Version 8.1
When using a Fork decision shape configured to skip assignment conditionally, an extra connector link appeared in the screen flow. This has been fixed.
SR-B77623 · Issue 346655
Handling added for empty queue in DeleteDeferred
Resolved in Pega Version 8.1
The DeleteDeferred method was setting a step status fail after trying to delete a non-existent queue item. A catch block has been added which will back out if the SLA queue deletion fails.
SR-B78077 · Issue 364120
Documentation updated to assist in fixing UnresolvedAssemblyErrors when resolving RUF rules
Resolved in Pega Version 8.1
To address UnresolvedAssemblyErrors resolving RUF rules, the following help topics have been updated: Selecting-import-file-tsk Importing-cli-tsk Importing-cli-web-tsk To include the following cautions: * Review the archive contents to better understand which rule sets are capped and to determine the relatives risks and benefits of running uncapped rule sets. * Do not import an archive into an active runtime instance of Pega Platform because the archive can overwrite rules in use.
SR-B79034 · Issue 333532
Flow breadcrumbs improved for temporary objects
Resolved in Pega Version 8.1
Issues were seen with navigating a screen flow properly when the work object was temporary. The screen flow contained sections with some required properties and “Allow errors” was checked to support navigating back and forth when there were errors; clicking the breadcrumb to go back in the flow worked, but clicking Next to go forward again did not proceed to the next flow action. This was due to missing validations, and changes have been made to the Complete Assignment function to handle the errors for Temporary and Non-Temporary Cases.