INC-154290 · Issue 613473
Signature capture exception resolved
Resolved in Pega Version 8.5.3
The signature capture control was throwing a JSON parse exception when the value was set and section was refreshed. This was caused by the signature for PIMC passing incorrect data which Preview could not parse, and has been resolved by ensuring the correct data for PIMC local store.
INC-155214 · Issue 617006
GetBinaryFilesRef updated for resolving wildcard
Resolved in Pega Version 8.5.3
After upgrading from 8.2 to 8.4, errors related to "Unable to serve file java.lang.IllegalArgumentException: Illegal characters detected in the path" appeared numerous times during full syncs, either on first time login or after cache clear. This was traced to normalizeRelativePath failing, and was caused by a resource declaration in pzGetBinaryFilesRef that encountered an issue where wilcarded URLs were not automatically resolved while packaging Static resources. This has been resolved.
INC-155752 · Issue 622772
Hidden Question pages and answers will be saved to database
Resolved in Pega Version 8.5.3
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-156211 · Issue 620193
Verbose comments removed from wrapper
Resolved in Pega Version 8.5.3
Comments with references to external links have been removed from some harness wrappers.
INC-157317 · Issue 620573
Signature Capture supported in RDL
Resolved in Pega Version 8.5.3
An enhancement has been added which supports using Signature Capture on forms in repeating dynamic layouts.
INC-157596 · Issue 624124
Mobile channel upgrade wizard correctly initiated
Resolved in Pega Version 8.5.3
After upgrade, the offline mobile app was not loading the correct portal. This was traced to missing properties needed to launch the upgrade wizard for channels upgrading from a previous release to v8.5, and has been resolved by setting those properties in upgrade activities.
INC-158468 · Issue 626380
RecordFieldValuesList page cleared
Resolved in Pega Version 8.5.3
Investigation o0f web node crashes traced the issue to a condition where the RecordFieldValuesList page was not cleared. This has been resolved.
INC-155640 · Issue 622978
Mobile logging updated for data page required parameters
Resolved in Pega Version 8.5.4
After upgrade, the number of warnings increased substantially in the mobile app log file for D_Pages, specifying "Required parameter X for data page X cannot be blank." This was traced to the forced logging related to missing required parameters for Parameterized DataPages during DeltaSyncs. In order to increase the value of the logging, the process has been moved from being called before packaging the Data Page to being printed later in packaging code and set to warn only about any unsupported data page configuration with required parameters.
INC-157217 · Issue 631970
Field Service mobile refresh timing updated
Resolved in Pega Version 8.5.4
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-157532 · Issue 631715
Corrected runtime name length check for custom fields to resolve logged error
Resolved in Pega Version 8.5.4
The error "Notification_MobilePush.Action ERROR - Can't parse JSON string to map" was being frequently logged. Investigation showed that in the Step8 activity in pySendNofication from Pega-Notification-MobilePush class, setting @String.length(customFields)>0 where customFields was a local value caused the runtime length check on customFields to fail. To resolve this, the Step8 activity in pySendNofication from Pega-Notification-MobilePush class has been modified from using @String.length(customFields)>0 to use @String.length(Local.customFields)>0.