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-B71423 · Issue 319981
Localization added to pyAccountSettings field labels
Resolved in Pega Version 7.4
Field label localization for the pyAccountSettings section rule has been added to the Pega-IntegrationArchitect ruleset.
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".
SR-B74088 · Issue 324942
Enhancement for Optimizing Packaging during full & delta sync
Resolved in Pega Version 7.3.1
As part of an enhancement for more contextual, optimistic packaging algorithm in certain conditions, packaging can be optimized based on a setting available at the case type. For example, most Field Service applications where offline capability is heavily used don't have or need the ability to instantiate or create new cases, but rather work on existing assignments routed to the agents. Some sites have the additional constraint where the case types or the flows within a case type may be large in number and dynamically created, which means the first full sync will just not be sufficient for the user to work on later created assignments. This has an adverse impact on the performance of the full sync and the first login time. The following changes have been introduced: - On delta sync - if a new work item ( of new case type which is not there during full sync packaging ) is added to work list. All the dependent rules of this new case type will be packaged and sent to HC. Added an checkbox in the case type rule "Only offline when in user's worklist" which will be visible only when "Enable Offline" is checked. - Provided a new when rule pyPackageAssignmentFlows which is set to false by default. When the true, all the case type with "Only offline when in user's worklist" will have selective flow packaging. - Create a class structure with a page group to hold full packaging and optimized packaging Application.pyOfflineCaseTypes("full") Application.pyOfflineCaseTypes("optimized") Above properties are populated in pzGetStartingFlows activity which is ran on delta sync and full sync. - Flows that are created in the case with "Only offline when in user's worklist" check are listed in pzDataSyncGetworkList which will be packaged during delta sync. The flows are listed for packaging if there is any Work Object created, flow is retrieved from the Assignment's pzInsKey key, and Flow key is built. Changes are made in the PackageRuntime.java to iterate the flow and perform packaging.
SR-B73542 · Issue 327654
JNDI Server field in Connect-JMS supports GRS
Resolved in Pega Version 7.4
Setting the value of the JNDI Server field in the Connect_JMS rule form using Global Resource Setting was only working when the JNDI Server rule instance was specified directly. In addition, attempting to use a GRS to set the value in the JNDI Server field itself resulted in the error "Could not find JNDI Server instance: =D_PegJMS.PegJNDIProp". This was due to the JNDIServerPage receiving the value of JNDIServerName but not being able to use it. To correct this, a local variable actualJNDIServerName has been added to carry the information and make it available to the API.