6.44 - Minor version release.
Important highlights from this release
- Ability for the Author to populate certain captured evidence types by defining a mailmerge field value in Content and Evidence Controls on a step.
- Extended the API to accept additional evidence types in order to populate content and evidence field type values on a step.
- Web and Mobile Stability Improvements.
- Improved push-notifications delivery wait period.
Improvements in this release
Fixes in this release
When stepping back to a step where audio file evidence (possibly audio recording as well) was captured, then transitioning again without specifying an audio file again the previously captured evidence does not save even though when stepping back the file name does display on the control.
When executing a flow in an offline state then the media files does not display when in execution.
On Mobile when expanding the user profile widget and selecting your default landing screen, then the selection is not saved. Even if you change it to the job list (dashboard) then when logging in again it still takes you to the launchpad.
When syncing down to the device, users were not given execute rights on non-directly executable flows. Visibility of flows on the launchpad were determined by this execute right being granted, therefore requiring how the visibility of flows and containers on the launchpad are determined to accommodate the correct syncing of permissions. Implicit view rights need to be assigned to all containers leading down to that flow.
When scheduling a job from the Job Dashboard, the job is moved to the Scheduled filter but the counter in the Sync Widget Icon at the top does not update to reflect the new job that needs to be synced. While the sync widget is expanded by clicking on the sync icon in the top left corner, and a job is then scheduled, the counters for 'new jobs not synced' and 'new edits not synced' is also not automatically updated until the sync widget is collapsed and opened again.
After you created a new job from the web portal which includes upload image, capture video, upload file, take a picture etc. Then, when viewing the Job history on mobile device, all the media evidence types displays 'no image uploaded' , 'no file attached' , 'no picture taken'. It should instead display 'Fetching File'.
When executing a job on mobile and capturing any media type evidence such as audio, photos, images etc., when the user steps back to the step where evidence is captured and recaptures evidence for those controls then the job history does not reflect these changes. The new media files also show on the history of the first step where evidence was captured instead of showing the first files that were captured.
In certain scenarios following does not display correctly in Job History:
A user has the appropriate execute permissions on a flow, and the execution works correctly on web portal. However, when syncing down to the device the flow template on the device does not have the correct permissions, therefore the transition to that flow is grayed out.
When you start a new job and for example reassign it to someone else, then the job does not appear underneath the in progress job filter. Only after a sync takes place, then the job appears under the correct filter. Also when in an offline state the exact same scenario mentioned occurs.
When leaving the application in the background for a while and then opening the app again and then signing out, the warning message appears.
Flow 1 includes two transitions - transition 1 goes to flow 2 - transition 2 goes to flow 3.
According to the rights, the user should not be able to press on transition 1 as they do not have any rights on the flow that it transitions to. And the transition should be grayed out.
We will not be held liable for any misrepresentation caused due to an unintentional copy error, typing error and/or omission that may occur on any of our material.