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.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

SR-C39546 · Issue 387806

Fixed Google Chrome report browser memory leak

Resolved in Pega Version 8.1

A memory leak was seen when toggling from the report browser to a different screen in Google Chrome. This was due to an event listener holding onto a window in pzpega_browser7, and has been fixed.

SR-C39588 · Issue 377514

Exception details and stack trace added to Bix -l

Resolved in Pega Version 8.1

When running BIX with the -I option, it failed with the message "( internal.access.ExtractImpl) INFO - Could not open file for reading " and nothing further. In order to improve diagnostics, the system will print the exception details and stack trace.

SR-C39676 · Issue 379470

Grid filtering "list only" option repaired

Resolved in Pega Version 8.1

The Grid filtering "List Only" option was not working on a grid that displays a list of claims on two different screens, the range for date properties did not show up in the filter box, and the "Apply" button on the filter appeared to be disabled. If there was another column set to Filtering: "Auto", then the filter could be applied. Once a separate filter was applied, the original "List Only" filter could then be applied. This has been resolved with the addition of a typeOf check while calling Displayerrors function in csvalid.js.

SR-C39690 · Issue 381877

New RUF added for deleting data type from CSV during import

Resolved in Pega Version 8.1

After upgrade, attempting to use the import CSV functionality to delete caused the wizard to hang and log the error 'PRRuntimeException: Can't continue with file upload. Can't read File'. This was caused by the system using the pxHasSingleKey RUF in pzDeleteRecords to check whether or not the class has a single key, which does not work for this use case. In order to support this method, a new RUF(pxHasSingleKeyAndExposed) has been created which will check the class for single key and also will check whether it is exposed or not. This will result in executeSQLForBatchDelete API being skipped and pzCreatePagesAndImportInBatch will get called instead.

SR-C39747 · Issue 383893

Added call to pyconvertedvalue to preserve number format in BIX extract filtering

Resolved in Pega Version 8.1

When creating a BIX extract rule with a filter of integer property on LHS and a constant integer value of RHS which is of 8-9 digits such as "filter : salary = 100000000" , saving the extract rule converted this RHS value to 100,000,000 and the filter showed as : "salary = 100,000,000" .In this scenario, running the extract rule generated an error in the log. This was traced to the system converting the filter value ( <pyfiltervalue> whose value is "100,000,000" ) to a number and causing a numberformat exception. This was a coding error that missed a call to supply <pyconvertedvalue>, and has been fixed.

SR-C39791 · Issue 379314

Group processing and StartDate issues resolved for Timeline controls

Resolved in Pega Version 8.1

Two issues were seen in the Timeline control:Issue 1: When a technician was selected who had no events, the Technician was not shown in Y-Axis (Groups were not being displayed). A blank screen was shown instead. This was caused by the a condition where an empty datasource caused createDataset to return without processing groups. This has been corrected by adding handling so the system will initialize dsArray with an empty value if needed to ensure the group related processing takes place. Issue 2: The start range for Timeline was not respecting the StartDate given for the Events display. In this case, if either the start or end time was not available then neither was set. To resolve this, If an end date is not specified then it will be marked as the current date.

SR-C39796 · Issue 383047

Enhancement added to switch tab name localization when locale switches

Resolved in Pega Version 8.1

When launching a Harness in a tab onclick of a link/button from a section, passing tab name as a localized field value was not working properly when switching between different locales. This was caused by the Tab name not getting updated on click on Launch harness, and has been corrected with the addition of a new parameter "bLocalize" for pzActionAppendValue to invoke getLocalizedTextForString if the parameter is true. This value will be passed as true when called from pzActionShowHarness newDocument case.

SR-C39815 · Issue 381813

Font files updated to support Turkish characters in VBD

Resolved in Pega Version 8.1

It was possible to use Turkish special characters in the labels of Business Issue and Groups, but VBD did not show these Turkish characters as in the screenshot. To enable this, a new set of font files with larger character sets has been added which includes the Latin-1 Supplement and Latin Extended A blocks to which the Turkish characters belong.

SR-C39879 · Issue 384006

Automations work using property with JSON string

Resolved in Pega Version 8.1

When using JSON to send complex data structures to an automation via a property, a special character ( ' ) used in the JSON string caused an error when trying to execute the automation from a flow action: "Uncaught SyntaxError: Unexpected end of JSON input". Analysis showed that if any relevant record had a single quote, the generated HTML of java tried to break the html data-automation-propData attribute, resulting in an exception. To fix this, the code has been updated to replace the single quote with ASCII HTML entity which will make the data-automation-propData attribute friendly.

SR-C3988 · Issue 358537

Launched portal remains open when navigating back to originating portal

Resolved in Pega Version 8.1

After logging into the 'Developer Portal' and then using the 'Launch' menu option to open the 'Manager' portal in a new tab, navigating to 'Manager' and changing the access role correctly caused the current tab to show the respective portal. However, after navigating back to the developer portal shown in first tab, the manager portal then closed and the developer portal was refreshed. This was a missed use case in the handling, and changes have been made in ApplicationSetup and RedirectAndRun activities to correct the issue.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us