With the Capture v1.42.6 release, a minor release, we are introducing some smaller new features and fixes to Capture. These go hand in hand with a number of changes in Manager and Designer, currently up to v41.24.
Capture v1.42.6 is available in stores now. Manager/Designer v41.24 is currently in production.
In these Release Notes, we will walk you through the following new features and improvements:
1. Location field
A new feature that Obzervr is proud to present is a new field type for configuration and use: Location.
The location field allows you to capture plant items/functional locations you have configured for your tenant against a Work Order. Setting a Work Template up with a Location field will automatically create a list of your plant items/functional locations in this field. You can set up the field to:
- Only show the plant items/functional locations in this Location field available to a team (based on your team configuration)
- Show all plant items/functional locations for the tenant
- To only have the Work Order's plant item/functional location and a list of the child plant items/functional locations related to that plant item/functional location.
Refer to this article for more information on how to set up and use this field type.
This is a new feature we activate for your tenant(s); this means that the Location field will not be usable by default. You can contact us via firstname.lastname@example.org to switch it on for your tenant.
2. Sync behaviour updates
A number of changes to the Capture synchronisation process to support new features and fixing earlier issues:
- Tenant switch in offline mode
It is now possible to switch between tenants (when you have access to multiple tenants as a user) when your device is offline (or out of range of networks), so you can access work orders on both tenants without having to find a network access point. It is recommended that you do sync both tenants whilst in range of a network before you "head out", to ensure that you have the latest information and work orders.
- First Time Sync to support new field types
With the creation of the new location field, we have updated sync to cater for this field as well as other new field types we may add in the future. To support this we had to force a user on a device to do a "First Time Sync", but not in the traditional sense, where the sync builds all the information the user needs when they log in for the very first time (which can take a bit of time). This First Time Sync is just to grab new configuration and at the same time do the normal "delta" sync (new work orders & documents) and will therefore not take any longer than your normal "delta" sync. Any other users on the same device, in the same tenant, will not get the First Time Sync, just the normal "delta" sync.
- Tenant based sync
In line with the above point, we have changed the rules around First Time Sync; new users will not get a First Time Sync if another user has logged in before them on the same tenant on the same device. This means that new users will only get a First Time Sync if they are the very first users logging in to a device for a tenant. First Time Sync has now become tenant dependent, not user-dependent. This will help reduce the time for users to start using Capture without having to wait for a First Time Sync.
- Switching tenants will always trigger a sync
In certain scenarios, we found that switching tenants would not always trigger sync and the teams from the previous tenant would still show in the Dashboard. We have fixed this issue by always triggering a "team refresh" and sync on the tenant switch. It will sync only when in the range of a network (see the first point).
3. Resolution of issues
A number of issues that our users have experienced over the last few weeks have been resolved in this release:
- Parent & Child group using the same group fragment - update issues
In specific cases where the same fragment for a parent and a child group in the same template was used, updating the fragment will update the parent group in the template, but not the child group. This is now resolved; both are now updated as expected.
- Updating cascading fields doesn't clear values in the second field
Where Work Orders use 2 cascading fields (where the selection in one field is filtered by another field), resetting and changing a value in the first field did not clear the second field (should update to “select value” but had the previously selected value instead). The second field now resets back to "select value" if you change or reset the first field.
- Improved text readability in Dark Mode
We have improved the readability of information text (pre and post text) for a field in Dark Mode. This text was appearing in a shade of grey that made it hard to read on the black background.
- Notes field issues
We have resolved issues relating to the notes field, where users had reported that they couldn't capture values in certain scenarios on specific versions on Android. Additionally, we have resolved an issue where the notes field was causing the app to crash in Android when scrolling fast through the form.
- Group name and Group Display Name
In v1.42.3 Capture isn't displaying the Group Display Name where it was defined, instead, it reverted to the Group Name for forms. This is now resolved.
- Exceptions raised by multiple users on the same field
Capture is now properly handling the scenario where multiple users raise (or remove) an exception on the same field in the same form. The Manager was inconsistently showing the exception in the overview, but not at the detailed field level.
- App crashes on using Instance Field History feature
We have resolved the issue related to the Field History feature, where users had reported app crashing when tapping on the tick icon to save captured values.
4. Known issues
There are known issues in the Obzervr products that we cannot all complete before releasing a new version of the software. Here are some of the issues that may impact the day to day use of the Obzervr system (Manager, Designer, Capture):
- Performance issues with certain "field spec" devices
Some Intrinsically Safe (IS) devices or rugged field devices like the ECOM and iSafe mobile devices have been seeing degraded performance after being used for more than one hour. Whilst we haven't had any reports of this happening in the last few weeks, this performance problem can still occur in certain scenarios.
Workaround: when running into degraded performance on the device, it's worth closing the app completely (not put it to background or resetting the app) and reopening the app. This "resets" the memory used by the app and you should see the app return to normal usage.
- Counts on the Work Order are not always updated in Split Screen mode
In particular scenarios and when using child groups, the progress counter and progress bars may not always update in the left portion of the screen.
Workaround: refresh the right panel by navigating forwards (through the Work Order) or backwards (to a listing page).
- Remaining issues Child Groups
Some issues remain in using child groups in certain scenarios. You may want to refrain from using these configuration options until resolved. If unsure please contact us via email@example.com.
- Using "Is Time Based" for Child groups in conjunction with Conditional Logic
- Using "Priority" for Child groups in conjunction with Conditional Logic
- Using multiple (more than 1) levels of child groups - may not count the groups correctly.
- No feedback when attempting to upload a large file
In Capture when uploading a large file which size exceeds the maximum size set in the tenant, the user is sent back to the upload manager without any indication that the file is too large. The file will not be uploaded.
Workaround: inform your users about your maximum file size setting.
- Tenant switch in offline mode freezes screen if switching to a tenant not yet synced
As per section 2, point 1, you can now switch tenants when you're offline, however, this only works when you've already synced this tenant at least once on your device. If you haven't synced that tenant before, Capture will show an error message, saying you should sync this tenant when you're back in range of a network. This is expected behaviour; Capture cannot present anything if a first-time sync for this tenant hasn't occurred yet. The issue presents itself after you've clicked OK on this message: the switch tenant screen has become unresponsive; you cannot switch to another tenant.
Workaround: click on the back button (top left) and try switching tenants again.