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.
INC-205683 · Issue 702562
Data transform actions supported in offline app
Resolved in Pega Version 8.7.3
Support has been added for pre- and post-processing data transform functionality and validation in the local actions of the offline app.
INC-217655 · Issue 723565
Resolved validation check freeze for Dynamic Layout Group
Resolved in Pega Version 8.7.3
After creating a multi-step form where step 1 had a Dynamic Layout Group(tabbed) that used form fields configured with validations, clicking next with empty/invalid values in the form intermittently caused the screen to freeze and a javascript exception was logged. This was traced to a missed use case related to templates in the childNode, and has been resolved by adding the necessary safe checks in lgtemplate and lgcelltemplate.
INC-218855 · Issue 718834
DSS added to control section collapse on refresh
Resolved in Pega Version 8.7.3
After update from 8.5, using dynamic layouts that included certain controls (autocomplete/text/dropdown) configured with Refresh-Other Section -> Parent / Top Level Section such as a pyCaseActionArea with Event 'On Change' showed a different behavior: entering a value in the configured text/auto-complete field that leads to the refresh of the top level section will collapse all expanded sections if there is a refresh trigger within the embedded section or dynamic layout of the collapsible layouts. In order to control this behavior, a new DSS has been introduced. By default HonourExpandWhenOnRefresh (owning ruleset Pega-UIEngine) will be set to false to maintain the current behavior of collapse on refresh, while setting it to true will use the older behavior of maintaining expanded sections.
INC-223222 · Issue 723634
Corrected apiContext when using bulkActions
Resolved in Pega Version 8.7.3
Row selections in the multi-selection table were intermittently not working after opening a table with bulk actions enabled. Investigation showed that opening a table with bulkActions enabled and then navigating to a table where bulk actions are not available but multi-select is enabled led to functions like setSelectedRows and getSelectedRows still being available in apiContext. This has been resolved by correcting apiContext when bulkActions is enabled.
INC-225236 · Issue 725703
Corrected LiveDesignViewDisplay error handling
Resolved in Pega Version 8.7.3
When all rulesets were locked and a section was opened from Live UI in a portal, a "rule deleted" message appeared and it was confirmed the rule was deleted even though the rule was in locked ruleset. Investigation traced this to a pzLiveDesignViewDisplay call to pxChooseBestRuleSet which jumped to failure logic when "allow check out" was disabled, and this has been resolved by correcting the error handling in pzLiveDesignViewDisplay.