SR-C9013 · Issue 350132
Mobile JSON parsing performance improvements
Resolved in Pega Version 7.4
The mobile sync process was showing high memory utilization during JSON parsing due to the retrieval of each literal creating a new StringBuilder which was not promptly cleaned up. To improve performance, the system will now pass a StringBuilder to the JSONParser for use throughout the parsing process.
SR- · Issue 319555
ResponseObj page cleared after sync
Resolved in Pega Version 7.4
During initial logon after the sync process, the ResponseObj page remained on the clipboard and impacted performance for the offline sync package. Page-Remove of responseObj and reqPage has been added to pzStoreAndForwardProcessItems to fix this.
SR-B11713 · Issue 330837
Completed mobile cases accurately reflected in desktop
Resolved in Pega Version 7.4
When using an offline mobile app to run and complete a flow, the work object on the desktop was not showing a "Completed" status when opened but was instead stuck in one of the previous assignments. This was traced to an issue with the back processing of a case behaving differently in desktop and mobile when looping was present, and has been resolved with modifications to the pega_process_engine.js file.
SR-B67903 · Issue 329428
Fix for Data Transform when Clipboard Page not found.
Resolved in Pega Version 7.4
Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.
SR-B67903 · Issue 328792
Fix for Data Transform when Clipboard Page not found.
Resolved in Pega Version 7.4
Logic has been added to correct the scope references of the generated offline-Datatransform-JS when using AppendAndMapTo.
SR-B76736 · Issue 328823
Offline localization fixed for field values with trailing spaces
Resolved in Pega Version 7.4
Field values were not localized offline if they contained trailing spaces. These spaces caused the field value lookup to fail, resulting in a JS exception. To handle this, a call has been added to trim the spaces if the field value is a string.
SR-B76736 · Issue 327585
Offline localization fixed for field values with trailing spaces
Resolved in Pega Version 7.4
Field values were not localized offline if they contained trailing spaces. These spaces caused the field value lookup to fail, resulting in a JS exception. To handle this, a call has been added to trim the spaces if the field value is a string.
SR-B81862 · Issue 330666
Offline localization support added for survey header
Resolved in Pega Version 7.4
Localization was not being applied as expected to a header section that served as the top part of an offline survey app. This header section used a pyCurrentSurveyQuestion property that held the value of the Question that was displayed on the screen, then the property value to be localized corresponded with field values contained in an offline allow list. The lack of localization was traced to the header section not pushing the context (via pega.pushStackFrame) when there was no using page defined. This lack of push is fine for the template renderer, but caused the offline localization logic to not have the correct context. In order to support the intended use, the code has been modified so that if the pzPrimaryPage is empty in the section metadata, the system will push the currentContext reference via pega.pushStackFrame.
SR-B84636 · Issue 335909
Needed functions/function libraries ported into JS text rules for mobile validation
Resolved in Pega Version 7.4
A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.
SR-B84636 · Issue 335930
Needed functions/function libraries ported into JS text rules for mobile validation
Resolved in Pega Version 7.4
A validate rule with a simple string expressions attached to a flow action of an offline-enabled case failed to execute when the flow action was submitted in an Android app. This was traced to new handling for Validate rules usage in offline which relied on select Function rules ported to JavaScript functions, and the desired functions has not been ported. These functions/function libraries will now be ported into JS text rules.