Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

INC-142589 · Issue 595489

Corrected tooltip evaluation for multiselect

Resolved in Pega Version 8.4.3

After adding help text for a multiselect help icon with overlay on hover field, the value was not being sourced. Changing to a different type of help text or control type worked as expected. This was due to an error in case sensitivity, using pyToolTip when it should have been pyTooltip, and has been corrected.

INC-142714 · Issue 596554

Recent Cases from different applications available to open

Resolved in Pega Version 8.4.3

An enhancement has been added which will allow opening other application assignments in the Recent Cases section of the current application when the user has access to multiple applications.

INC-143005 · Issue 596954

Fluid Overlay displays as expected in Firefox

Resolved in Pega Version 8.4.3

After upgrade, using the Overlay format "Fluid" to perform the screening matches task in CLM using Firefox had an overlay that covered the entire screen but was missing the scrollbar to manage the content. This has been resolved by adding changes to support dynamic content (with scrollbar) for center overlay.

SR-D32655 · Issue 510345

Enhancement added to hold Change Tracker values until UI is loaded

Resolved in Pega Version 8.4

Sporadically, an agent attempting to answer a queued call within 10 seconds received a loading screen. By the time the load completed, the next agent had already taken the call. This is a scenario where based on a change, the agent was trying to refresh something on the UI (a section or harness) which was not yet loaded/present on the UI. To address this use case, an enhancement has been added to hold the change tracked values and handle them once the UI is loaded. The new function pega.ui.ChangeTracker.prototype.handlePendingCTChanges in pzpega_ui_changetracker.js is used to handle the pending CT changes. A hook has been added in the pzpega_ui_doc_lifecycle js file to invoke the above function once the UI is loaded.

SR-D15395 · Issue 492053

Added DSS to handle BIX extracts under parse delimiter rules

Resolved in Pega Version 8.4

When parse delimiter rules were applied, the File Listener was not parsing the CSV manifest file generated from a BIX extract until the file was resaved. This was traced to a space after a comma in the extracted files, and has been resolved with the addition of a DSS which enables the use-specified delimiter to remove the space after the comma in the manifest files.

SR-D15872 · Issue 494476

Handling added for null result during BIX agent execution

Resolved in Pega Version 8.4

While executing one of the extract rules either manually from the Designer Studio or by using the back end BIX-Agent, an infinite loop caused agent rules to run indefinitely and create a server log size that impacted system performance. This was traced to reading a page from stream that was returned as null due to an exception, preventing the system from proceeding to the next result. To resolve this, the system has been updated to move to the next result if the current result throws an exception and returns as null.

SR-D17825 · Issue 494704

PreSaveAs updated to set the correct ruleset value when saved into a different ruleset

Resolved in Pega Version 8.4

When using a BIX Extract rule already configured with properties and filter criteria, attempting to update the filter criteria system resulted in an "invalid property error" and inability to save the updated rule. This was traced to the extract rule being created from another extract rule with 'save as', resulting in the new extract existing in a different ruleset. Because the pxBixReportPage.pyRuleset had the value of the original ruleset instead of rule set in which it had been saved, the system was attempting to find the filter properties in the original ruleset. To resolve this, the Presaveas activity in rule-admin-extract has been modified to check and set the correct value when both the rulesets are not equal.

SR-D21555 · Issue 501106

Resolved command line BIX/PRPCUtils creating unreachable nodes

Resolved in Pega Version 8.4

BIX and PRPCUtils scripts were creating nodes that showed as unreachable or that were never cleared. This was traced to a code change that resulted in nodes starting as stream nodes unless given a node type or DSS settings, and has been resolved by setting the asyncExecutor/enable setting value as false in the prconfig.xml. The BIX command line JVM argument should also be set to NodeType=BIX.

SR-D22075 · Issue 501345

Wild card character escape added for filtering data records

Resolved in Pega Version 8.4

It was not possible to export data type records which were filtered with either _ or % in the value. This was due to the characters being wild card characters in the SQL-like operator, and has been resolved by modifying the NativeSQLAPIResolver to add escapecharacter to the runtime value of the filter.

SR-D22468 · Issue 502037

Bix extract performance improved by only checking cipher type for encrypted properties

Resolved in Pega Version 8.4

Previously, if no cipher was configured in extract Rules the cipher type defaulted to null and wasn't cached. This caused performance issues when running against the database. In order to improve performance, the code has been modified to only check for cipher type if the property is encrypted. Performance issues were also seen when running a BIX extraction via the command line where the BIX extract was set to extract all properties, the BIX extract rule used Extract to XML, and DisableEpochDateTime and DisableEpochDate settings were not created and thus the default (false) value was used. This slowness was traced to the command line extract not caching the "miss" for the values of the Epoch settings and therefore repeatedly querying the pr_data_admin table for the date and datetime property for each record. Investigation showed that BIX was depending on DASS files that are not shipped out-of-the-box: since the DASSs were not present, the query to retrieve their value returned null and was not cached for future access. To resolve this, the system has been updated to pass default values for the two required DASSs if they are not present, ensuring a value will be cached and the DB query will not be fired unnecessarily.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us