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.

SR-118077 · Issue 170104

Excessive logging addressed in Pega Mobile 4.3

Resolved in Pega Version 7.1.7

In PegaMobile, the oLog debugging statements were generating excessive log files. This has been addressed in Pega Mobile 4.3.

SR-B15685 · Issue 317888

Mobile autocomplete dropdown selections fixed

Resolved in Pega Version 7.3.1

When the 'Enable lightweight autocomplete on phone' and 'Allow scrolling for more results' were enabled, the incorrect data was selected (e.g., using the autocomplete to select "John" from the list instead displayed "Mark"). This was due to a logic issue around the scroll feature for mobile list based autocomplete, and has been fixed.

SR-B71308 · Issue 319409

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.

SR-B71308 · Issue 320806

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

After upgrade, paragraph rules were not displaying as expected in the offline mobile app. Instead, the message 'Loading...' appeared in their place. This was traced to the records being returned correctly but not being properly packaged for display due to an error in the report definition. To correct this, a step has been added to the pzPackageLocalization activity to clear parameters which may mislead report execution.

SR-B54666 · Issue 320294

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

A paragraph rule that included a jsp reference tag for an integer type property did not display properly when tested in an offline mobile app, instead hanging at the "Loading..." message indicator. This was due to getLocalizedTextForString() failing for non-string values, and has been fixed with a check in template_paragraph.js

SR-B54666 · Issue 316346

Paragraphs load as expected in offline app

Resolved in Pega Version 7.3.1

A paragraph rule that included a jsp reference tag for an integer type property did not display properly when tested in an offline mobile app, instead hanging at the "Loading..." message indicator. This was due to getLocalizedTextForString() failing for non-string values, and has been fixed with a check in template_paragraph.js

SR-B57614 · Issue 322754

PegaMobile honors prompt for password check

Resolved in Pega Version 7.3.1

The Pega Mobile App option to 'Always prompt for password on start' was not saving the selected choice. This was caused by a conflict with "Do not save property data" in the persistence section of the property advanced settings, and has been fixed.

SR-B67236 · Issue 325268

Resolved infinite loop in offline app

Resolved in Pega Version 7.3.1

Pressing "Next" was causing an offline app to go into an infinite loop. This was found to be caused by two issues: there was a problem with back processing when deeply nested subprocesses were configured, and the handling was not working with a subprocess that had more than one 'from-connectors'. This has been addressed by modifying the implementation logic in process_flow.

SR-B69404 · Issue 320544

Map include enhanced with fallback "Show user location" function

Resolved in Pega Version 7.3.1

When Map was included in a section by checking the "Show user Location" option, the pxRequestor.latitude and pxRequestor.longitude options were empty in the clipboard. Also, in Microsoft Internet Explorer the user location was not shown and the default Boston location was given. This was traced to a null pum.GeolocationMarker.position in Microsoft Internet Explorer, and a fallback approach has been inserted to set the position from the existing previous value.

SR-B72669 · Issue 326687

FinishAssignment updated for offline mobile reports

Resolved in Pega Version 7.3.1

When a submitted report was saved in offline mode and then retrieved from the client store, the system seemed to only retrieve the N-1 version of the work object. Analysis showed that the call to open the object after being submitted only opened the first transaction and not the last transaction recorded for the case, and the issue was traced to Finish Assignment not saving the updated work-object to the client-store. To fix this, the system will call saveWorkAndAssignment in gotAFlow defined inside finishAssignment when "no next action".

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