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-B76216 · Issue 325540

Localization support added for Indonesian

Resolved in Pega Version 7.3.1

pyLanguage has been modified to add the new value in_ID in the prompt list that will provide localization support for Indonesian (Indonesia).

SR-B76880 · Issue 326010

Repeat grid filtering option fixed for Microsoft Internet Explorer 11

Resolved in Pega Version 7.3.1

The repeat grid populated when running report definition was prompting for the filter of the data properly in Microsoft Internet Explorer 11, but no action was performed when clicking on it. This was an issue with missing navigation rule changes, which have been added.

SR-B77544 · Issue 326629

Scroll bar issues fixed for freeze column pane

Resolved in Pega Version 7.3.1

A vertical scroll bar was displayed on the screen and the horizontal scroll was not working as expected when the freeze column pane option was selected in the repeating grid. This was traced to styles missing from the base-grids.css that were needed for fixed column configuration, and these have been added.

SR-B15150 · Issue 286741

Online help updated with current reindexing utility information

Resolved in Pega Version 7.3.1

The online help files have been updated to remove references to deprecated activities for reindexing declarative indexes. Information has been added for the currently supported utility, the column populator tool (prpcUtils or prpcServiceUtils) with expose option and 'expose.reindex=true', that specifically regenerates declarative index content.

SR-B57565 · Issue 316702

Fixed encoded special characters in 'Field values'

Resolved in Pega Version 7.3.1

Special characters in 'Field values' were being displayed as encoded in the grid. This was due to missing handling, and has been fixed in the generateCellContent RUF.

SR-B74088 · Issue 324942

Enhancement for Optimizing Packaging during full & delta sync

Resolved in Pega Version 7.3.1

As part of an enhancement for more contextual, optimistic packaging algorithm in certain conditions, packaging can be optimized based on a setting available at the case type. For example, most Field Service applications where offline capability is heavily used don't have or need the ability to instantiate or create new cases, but rather work on existing assignments routed to the agents. Some sites have the additional constraint where the case types or the flows within a case type may be large in number and dynamically created, which means the first full sync will just not be sufficient for the user to work on later created assignments. This has an adverse impact on the performance of the full sync and the first login time. The following changes have been introduced: - On delta sync - if a new work item ( of new case type which is not there during full sync packaging ) is added to work list. All the dependent rules of this new case type will be packaged and sent to HC. Added an checkbox in the case type rule "Only offline when in user's worklist" which will be visible only when "Enable Offline" is checked. - Provided a new when rule pyPackageAssignmentFlows which is set to false by default. When the true, all the case type with "Only offline when in user's worklist" will have selective flow packaging. - Create a class structure with a page group to hold full packaging and optimized packaging Application.pyOfflineCaseTypes("full") Application.pyOfflineCaseTypes("optimized") Above properties are populated in pzGetStartingFlows activity which is ran on delta sync and full sync. - Flows that are created in the case with "Only offline when in user's worklist" check are listed in pzDataSyncGetworkList which will be packaged during delta sync. The flows are listed for packaging if there is any Work Object created, flow is retrieved from the Assignment's pzInsKey key, and Flow key is built. Changes are made in the PackageRuntime.java to iterate the flow and perform packaging.

SR-B54277 · Issue 336406

Trimmed unneeded properties from doUIAction call

Resolved in Pega Version 7.4

Null pointer exceptions were generated when relaunching the manager portal after saving a work-object, and the error "Request-URL Too Large. The requested URL's length exceeds the capacity limit for this server" appeared. This was traced to the number of properties included in the doUIAction call; unnecessary parameters have been removed to resolve this issue.

SR-B66164 · Issue 325166

Handling improved for pzActiondropdown's Action label value

Resolved in Pega Version 7.4

When an alternate flow action was picked from LocalAction's list and then submitted, the presence of any page-set messages would cause the submission to fail and the flow remained on the same flow action. This was an issue with handling the changed value of the FlowAction label, and the pzActionDropdown control has been modified to get the correct pyDefaultActionIndex parameter value.

SR-B70422 · Issue 326897

Removed unnecessary add/delete history entries related to empty page properties

Resolved in Pega Version 7.4

The field level auditing configured for page group or list property types was creating multiple add and delete entries in the history of the case even though the pagelist/pagegroup had not been modified. This was traced to method used by the pagelist change audit process to compare current pages to the previous value of the pagelist pages: during pagetostring conversion, sometimes the empty properties in page are present in the String and sometimes they are not, resulting in a difference that generated the non-essential audit entries. This has been fixed by changing the getProperty references in getPageAsString function to use getIfPresent instead. Null checks have also been added.

SR-B70595 · Issue 328754

Out of box REST API creates Page Lists with pxObjClass

Resolved in Pega Version 7.4

Page-Merge-Into was implemented in such a way that the pxObjClass was added for a page but not for a Page List until the case was created. This interfered with validating pagelists and identifying problems with the message data that would allow the case to be rejected before creation. To allow for more flexibility, the pzCreateCaseInternal activity contains an added a property-set so that the pxObjClass is updated on embedded pages.

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