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 note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

SR-C85341 · Issue 423421

Dropdown sourced from data pages or clipboard pages working for all browsers

Resolved in Pega Version 8.1.4

After working to resolve a dropdown issue with Edge browsers, some other dropdowns sourced from a data page or clipboard page were failing to load. This was caused by the dpparams parameter being encoded so that the proper JSON was not retrieved, and has been fixed by modifying the system to decode it before passing the postdata.

SR-C85614 · Issue 427440

BIX extract connection leak repaired

Resolved in Pega Version 8.1.4

The first time that a BIX extract was run it failed with a timeout. Running it again immediately was successful. Investigation showed that if the BIX connection timed out, the connection was not being returned to the connection manager due to a failure to reset the autocommit for a connection that partially ran but was not properly closed. This has been resolved by adding handling that will return the connection to the pool and clear the map if there is an exception. Further refinements will be made for timeout issues in multi-tenant environments in a future release.

SR-C85752 · Issue 425074

New MaxFileSize extension point added for pyMaxFileSizeViolation

Resolved in Pega Version 8.1.4

A severe guardrail warning was raised when saving the activity pyMaxFileSizeViolation into a ruleset. This was traced to the CheckForWarnings Activity of Rule-Obj-Activity which checks if any activity referenced is an internal activity. Activity pyMaxFileSizeViolation was calling the internal pzGetCMMaxFileSize activity, and the warning appeared because the py activity was overridden in the application ruleset. To resolve this and add an extension point, pzGetCMMaxFileSize has been modified to a new data transform called pxGetCMMaxFileSize, which is called in pyMaxFileSizeViolation.

SR-C85853 · Issue 425289

Currency codes updated

Resolved in Pega Version 8.1.4

The list of Currency Codes has been updated with the latest ISO changes, including Venezuela and Sao Tome & Principe.

SR-C86133 · Issue 426388

Logic updated to resolve Strategy Parser error using dateTimeToBigDecimal

Resolved in Pega Version 8.1.4

After upgrade, a Strategy run was failing with a SemanticAnalysisException error indicating "Type Mismatch in node 'ILTernaryOperation': False branch does not equal return type (DECIMAL ==> DATETIME)". Upon investigation, the issue was traced to a property set component with an expression using the "DateTime•dateTimeToBigDecimal Pega-RULES:08-01-01" function. To resolve this, the logic has been modified to set the return type of ternary node from the Java type, and to check that True and False branches match this return type as well.

SR-C86138 · Issue 431777

Security updates for avatar upload function

Resolved in Pega Version 8.1.4

Updates have been made to enhance security around the avatar upload function.

SR-C86195 · Issue 423608

Logic added to map shorthand timezones to their official counterparts

Resolved in Pega Version 8.1.4

When the time zone in the operator profile record was a non-standard value and no timezone was selected in the operator profile, the date picked in the calendar was reduced by 1 day each time a section was refreshed. For example, if the timezone "IST" was used for India in the Pega operatorID record while the official timezone name is "Asia/Calcutta", the date selection was off by a day after refresh. To resolve this, logic has been added for mapping shorthand timezones to their standard timezones.

SR-C86213 · Issue 424585

Corrected PRAuth URL handling for sessions on restarted nodes

Resolved in Pega Version 8.1.4

If a user session was in progress and the node restarted, attempting to refresh the session when the node came back up was not working. Launching a new browser session cleared the problem. A trace showed that the Authentication Selector screen was not loading because the PRAuth URL redirection was going into an infinite loop, and this has been corrected.

SR-C86260 · Issue 424929

RecordsEditor Section- Parameters for HideDelete and HideAdd held on clipboard for use

Resolved in Pega Version 8.1.4

On initial load of a RecordsEditor section, the delete and add options were properly hidden from the user. After using any sort option on any column, the parameters were not persisted and the delete and add icons became visible. To resolve this, the implementation has been updated so that the pyHideDelete and pyHideAdd parameters will be read from myParamPage on the initial load and saved on a clipboard page for use.

SR-C86822 · Issue 424717

50 count limitation removed from application list export

Resolved in Pega Version 8.1.4

Previously, using Designer Studio -> Application -> Distribution -> Export to export the list of applications limited the results to 50. This number was hardcoded in the page size count setting for the Report Definition. In order to better support complex installations, this limit has been lifted.

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