Skip to main content
circle-square
Outline Circle
square-square
Little Circle
square-square
Little Circle

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 SR ID number in order to find the associated Support Request.

INC-143036 · Issue 599191

SurveyPage loads when ruleset is locked

Resolved in Pega Version 8.3.6

When the ruleset containing the survey rules was locked D_pzSurveyPage did not load and errors were generated. Investigation showed that if the flow was in a locked version, the PopulateShapeNodesFromFlowData activity did not call EvaluateConnectorState, causing the mapping of the transitions for connectors to fail in the activity MapBranchShapeConnectors. This has been resolved.

INC-153805 · Issue 627967

Mobile app language remains consistent after data sync

Resolved in Pega Version 8.3.6

When using a Field Service Mobile App where the locale of all workers was set to nl_NL, the UI was intermittently flipping from NL to EN and and back again. This was traced to the locale of the requestor (field worker) being lost during synchronization of the mobile app data to the server, causing the UI to fall back to the default value of EN. This has been resolved by ensuring the requestor always uses the chosen locale for the operator.

INC-155752 · Issue 622771

Hidden Question pages and answers will be saved to database

Resolved in Pega Version 8.3.6

After a question page was shown and some values were entered, going back to the question and reverting an option caused the question page to not be visible, but the answer values persisted in the clipboard and were eventually saved into the database. This was a missed use case for Question page smart shapes, and has been resolved by updating the pzSetQuestionPageParams data transform so that whenever a question page is evaluated to either to show/hide, when the question page visibility is set to false and the pyClearAnswerValuesWhenQPHidden 'when' rule is overridden, the corresponding values will be wiped from the clipboard and only the required values will be saved to the database. However, please note this is not supported for branching logic and visibility conditions should be used instead.

INC-157217 · Issue 631969

Field Service mobile refresh timing updated

Resolved in Pega Version 8.3.6

A configuration in the Field Service mobile app used to select and map data from a modal section to a wrapper section used "pega.fsm.mobileutil.reloadSection" to refresh the wrapper section and make the data visible after the mapping. If the refresh was performed after the initial login, the refresh was done on only a portion of the screen and resulted in incorrect data being shown to the user. However, continuing to fill in the section and then saving and reopening the task displayed the correct results. The issue was reproducible only on the first attempt after clearing cache/date: subsequent uses refreshed properly. This was traced to the timing of the configured actions, which caused the refreshSection action to be triggered before the runDataTransform action execution was completed. This has been resolved by adding code that will pause the action queue until the runDataTransform action completed.

INC-168935 · Issue 645393

CalendarGadget updated to display events in Saudi locale

Resolved in Pega Version 8.3.6

When using the pxCalendar section with the locale setting ar_SA, the calendar was correctly converted to a Saudi calendar but the events which were showing in the English version of the calendar were not showing up in in the Saudi Calendar. This was caused by the CalendarGadget page not populating properly due to the localized Hijri calendar failing a datetime check that was looking for a Gregorian calendar with time in GMT format, and has been resolved by updating the when rule "pzShouldDisplayEvent" to use the proper function for the localized calendar.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us