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.
SR-B82031 · Issue 345364
Filter popup aligns with selected column
Resolved in Pega Version 8.1
When a wide grid was scrolled to the right and a column was filtered, the filter popup as not aligned with the column being filtered. Instead, it was shifted to the left of the column. This was due to the popover not being aligned properly with the target, and has been fixed.
SR-B84658 · Issue 345365
Popover visible for autocomplete on overlay
Resolved in Pega Version 8.1
The Popover was not visible for autocomplete on an overlay when the center overlay option was checked. This has been fixed by adding a scroll handler with an 'if' condition to the rootPopover when there is a child popover on it.
SR-B85840 · Issue 350669
Null check added for Grid content in a read-only RTE
Resolved in Pega Version 8.1
ui_grid.js was trying to initialize a grid from the markup of mail content. Since there were some missing attributes, script errors were thrown that resulted in an endless busy indicator. This is now fixed by adding the necessary null checks in Grid code.
SR-B86231 · Issue 360758
Error identification improved for Data Flow Errors landing page
Resolved in Pega Version 8.1
If a dataflow failed because of a particular input (row), the "Data Flow Errors" landing page was not showing which record was at fault. To correct this, the system will inspect the exception coming from the database layer to define which record failed the batch. If it's not possible to identify the actual record, a general exception will be generated.