There is a new version of FieldTask available in the google play store. This has some cool new features.

Relevance and Constraint work inside a page

This long awaited feature has been added by the ODKCollect community. It means that you can now put multiple questions on one page of the screen using the “field-list” appearance and make some of the questions visible depending on answers to other questions on the same page.

A simple example is a text question for “other”. This can now appear automatically under the select question when the “other” choice is selected.

Track changes to answers while a survey is being completed

This takes auditing to a whole new level.   Changes are written to a csv file.

In the example above the user initially entered a value of “Tom” as the answer to question 1. They then went back and changed that value to “Neil”. Note the Duration column. This was added by taking the difference between the start (in milli seconds) and the finish and then dividing by 1000.

You can download the above CSV file using the API: https://sg.smap.com.au/api/v1/audit/log/s193_1778/uuid:9fcf9bf7-d780-4397-8781-b4ba0bbe0cb8

Logon with username “api” and password “api”

To enable logging of question changes

In the online editor select the “File” menu and then “Settings”. Select the checkboxes “Timing Data” and “Audit Changes to Questions”.

This can also be enabled from an xlsForm by specifying “yes” as the value in the timing_data and track_changes columns in the settings worksheet.

Viewing the Audit Log

The log has to be downloaded using the audit API. Here are some links to get you started:

Documentation: http://www.smap.com.au/apiAudit.shtml

Getting the URL that will retrieve your data:

1. Get a list of data end points: https://sg.smap.com.au/api/v1/data/
2. Select the URL for the survey for which you want the log file
3. Select the URL labeled “audit_log” for the submission that you want to review

You should change the above URL to point to your Smap server and you can log in with your username and password to see your surveys. If you just want to see the demo csv file then log on to the sg server using api:api

New Features

1. Added reminders for tasks. These reminders are specified as a type of “notification”. You can set the time after a task has been accepted for a reminder email or SMS to be sent to the user who accepted it, or to someone else. So for example you could have a reminder after 2 days for the assigned user to “Get on with it!”. You could also set another reminder that if the task is not completed within 5 days a reminder is sent to a supervisor that includes a link to the task so that the supervisor can complete it. You can specify the reminder interval in hours or minutes as well as days, I’d like to think that “minutes” is there mainly so I can demonstrate the feature, however it may prove useful in fast moving problem domains.
2. Allow URLs of images to be set as dynamic defaults for image questions. For example you could use cascading selects to select a schematic from thousands of available images. This schematic can then be annotated by the user and submitted with the completed form. This feature is now available in Webforms and in fieldTask 6.21. Here is an example form that gets the images from Wikipedia. Commonly however you will want to retrieve the images from the same Smap server that you are using to complete the form. By getting the images from the same server you won’t be blocked by CORS. Wikipedia does not enforce CORS but sites that require authentication, such as other Smap servers, would.
3. Added dynamic defaults to webforms. A dynamic default is specified in the “calculation” attribute of a question. Hence you can set the initial answer to a question based on the answer to a preceding question. Allowing images to be used as dynamic default values as described above is a special case of this new feature. This feature is already available in fieldTask.
4. Customise the appearance of the web site for an organisation by setting the colour of the menu bars and by specifying the main picture on the home page. You can specify these themes in the Organisations tab of the user management page.
5. Add support for “track changes”. This is a feature from the ODK community that audits every change to a question answer while a form is being completed. So it adds to the existing audit capability that allows you to record the total time spent in each question and the GPS coordinates when it was finally answered. You can enable “track changes” in the settings dialog of the online editor. However you will need the soon to be released fieldTask 6.21 in order to use it.

The big change in this release is the addition of GPS coordinates to named locations.

Named Locations

When you add or edit a task you can set the GPS coordinates, an NFC identifier or both to specify where the task should take place. This is what we call an anonymous location since you are not using a “Named Location”.

However you can now also enter the name of a “location” that has the NFC UID and/or the GPS coordinates pre-defined. To do this Select the group name first and then the location name. (This change addresses issue #468).

Named locations are shown in the “Shared Resources” page. Select the Admin module then “Shared Resources” , then select the “Locations” tab to view them. Click on the “Download” button to get the current locations in an excel file, or an empty template if you have not specified any locations.

Loading Named Locations from an Excel file

Locations are organised into groups and each group is shown in a separate tab of the excel file. Create new tabs giving each one a unique group name. Then for each group create locations. You can specify:

• UID: The identifier of an NFC chip at the location
• name: The name of the location
• lat:  The latitude in GPS coordinates
• lon: The longitude

The location name must be unique within the group. When the file is ready select “Add Files” and then “Upload”.

Updating a location when editing a task

After selecting a location you may adjust the GPS coordinates or change the NFC UID. You then have the option of:

• Continuing with an anonymous location
• Updating the location with the new coordinates / NFC UIC
• Saving a new named location

Other changes

• Added “auto” as a parameter option in the online editor to automatically start camera, barcodes and NFC reader when the user swipes to that question. The auto start is only applied when swiping forwards, there is not already a value recorded for the question and the question is the first one on the page. (This update implements issue #475)
• Drastically reduced the memory required when importing data from an excel spreadsheet. This was tested importing 80,000 rows each with 500 columns without any problem. This new version is also much faster than the previous import.
• API changes
  • New API to get a list of projects
  • Add option to return links to additional data views when calling the data api
  • New API to list submissions
• In PDFs allow the colour of a marker showing position to be configured using an appearance setting for the geopoint question
• Fixed issue #433. The advanced filter was not working correctly with wildcards.

New Features

Its all about Tasks in this release.  Lots of great new features.

• Auto start of external applications in fieldTask. (requires fieldTask 6.10). An external application will be automatically launched if you set the parameter “auto=yes”.
• Geofencing for tasks. A “Show Distance” can be set on a task so that it will only be shown to the user if they are within that distance of the task location. In addition a “download distance” can be set on a task group. Tasks in that group will only be downloaded when the user is closer that that distance from the average center of all the tasks in the task group.
• Set initial data for a task.
• Tasks API.

Geofences

Show Distance

This is for tasks that have been downloaded to fieldTask. The app will show and hide them as the user moves in and out of the geofence.

There are two geofence capabilities added in this release.

1. “Show Distance”. The tasks are downloaded to the phone but only shown to the user when they are close enough to the task location. This distance is set per task.
2. “Download Distance”. Tasks are only downloaded to the device when the user is close enough. This distance is set on a task group.

Set Initial Data for a Task

Amazingly this was not previously possible.  You could set a task to update an existing record however now you can also create a brand new submission but initialise it with some arbitrary data.  When creating tasks from existing data you can select one of the following 3 options:

No initial data means that your form will open empty. “Pre-populate form with existing data” is the new option, the data will be taken from the existing record and mapped to compatible questions in the new form that you want completed and the original data will not be updated. The third choice “Update Existing Results” continues to allow you to update an existing record. The data for that record will be shown in the form that you are going to complete.

You can’t yet add initial data when you add an ad-hoc task via the user interface. However you can do this via the new tasks API (see below).

Tasks API

A tasks API is slowly emerging. This is documented on the Smap website at http://www.smap.com.au/apiTasks.shtml.

• Get task groups for a project
• Get tasks
• Get task details
• Get initial data for a task
• Create a task

New Features

1. Including data from linked surveys into a PDF
2. New XLSX report on the task management page that will list all tasks in all task groups. Exports to XLSX for tasks in the current task groups are still available.
3. Manage a password policy for fieldTask.
4. Add support for the ODK setting “guidance_hint” when loading xlsForms
5. Add support for the ODK setting “body::intent” when loading xlsForms
6. Add a tasks API to return tasks in geojson format
7. Add an audit API to return geoJson data on location and duration of each question asked in the survey
8. Add the user identifier as a valid value for use in an advanced filter
9. Record the PDF template for a survey in the surveys change log so that previous versions can be referenced
10. Add ability to delete meta questions in the online editor as well as add the pdf_no appearance to them so that they are not included in PDF exports

Including data from linked surveys in PDFs

Smap allows you to combine Surveys to make “Systems“, where data in one survey can be linked to data in another. For example a survey recording the delivery of aid may include the identifier of the beneficiary. You can analyse this data taking account of the links between them by extracting the data into external tools like Power BI. However inside Smap itself we haven’t provided any capabilities to join data from different surveys during analysis. This new feature is the first step on that path.

When you create a PDF containing data from a single survey submission you can optionally specify:

• Include reference data
• Only include data from surveys launched from the current survey

The first option requires you to have specified a child subform as being launched from the survey you are exporting. You also need to specify a key question in the child survey.

If you include the second option you don’t need to specify a key question but only data collected by launching the child survey on the phone will be included.

Password Policy settings for FieldTask

FieldTask Version 6.02 has a logon page.  By default this is shown when the app is first run so the user can set the server, username and password without having to go to the settings menu.   After successful logon it is not shown again.  This corresponds to the default password policy of “Never show logon page”.  In the tab for fieldTask options on the usermanagement page you can also specify a policy of “Always show logon page” which will require the user to enter their password every time they start the app;  and “Periodically show logon page” which will require the user to enter their password again a specified number of days after their last successful logon.

Bugs Fixed

1. Large API exports were causing out of memory errors. These data exports using /api/v1/data are now streamed so there should not be any size limits.

New Features

User activity views have been added to the dashboard. If you open a table view or a map view then you can specify the subject as “User Activity”. Then select a user to show their activity.

The source of data, such as the form name that was used to collect it, or the file name that was imported is now shown in the table view on the dashboard.

Added display_name to choices. Display names have been available for questions for a while. These allow you to specify a name to replace the question name in reports but one that is not constrained by the limitations of the odk question name. For example you can include spaces. These are now available for choices. This is particularly useful for select_multiple questions as now you can replace default column headers such as “Question Name – choice_name” with something more meaningful such as “The selected choice 10 !!!!”.

Add the ability to restrict activity within an organisation. For example you can prevent the submitting of any new survey results, access to the data api or sending of notifications. If any change is made to these settings the organisation owner will be notified by email.

Added some initial customisation of the webform page appearance. For example you can now set background colours for some of the components.

Add a new data processing option to reports. Transformation of data from Long to Wide. hence if you have done a longitudinal survey you can get a report on things within that survey with one row per thing and all the time series data converted to additional columns.

Added some settings data into a settings workbook when creating an excel report. This now shows the timezone used in the report as well as the start and end time of any date filtering applied.

Bug Fixes

• Replacing a select_one question with a select_multiple question after data collection had started caused further submissions to the form to fail. Now fixed.
• Multiple bug fixes in webforms. Images in choices now work again as does the selection of drop down select questions.

The Smap Consulting headquarters has moved from Canberra to Brisbane. The primary reason is to focus on projects in the South Pacific, Brisbane being a base for a lot of this work. We will continue of course to support all of our customers anywhere in the world and travel will be quicker and easier from here.

The company address is now:

7/47 Herston Road
Kelvin Grove,
Queensland, 4059
Australia

[osm_map_v3 map_center=”-27.468,153.024″ zoom=”14″ width=”100%” height=”450″ post_markers=”1″]

Updates

Changes to the layout of the user administration page

The new feature to allow a user to belong to more than one organisation has prompted some changes to the user administration page.  The main one is the removal of the button to move a user to a different organisation.   Instead when you open the user for editing then, if you have organisation administration privilege, you will be able to set the users current organisation.

Previously you would select one or more users by clicking on a checkbox next to their name and then click on the “Move to Organisation” or “Delete” button.  A delete button has now also been added next to each user so there is no longer a need to select users prior to taking an action.  The “Add User” button has also been moved above the list of users.

This is work in progress and their will be more changes to the user administration page layout in the next release.

Timezones

The management of timezones for reports and viewing data has been improved.

1. You can set your timezone in your user profile.  (Available on all pages)
2. The default timezone is the one your browser is set to however you can change this and it will be saved with your other settings.
3. Exports to XLS include a new tab that shows the timezone used for all dates and times.
4. You can set the timezone for a report independently of your personal time zone and this will be saved with the report

Legacy Reports

The old way of creating reports as snapshots of panels on the dashboard has been removed.

Administration Reports

Two reports have been added to the form management page:

1. Usage.  How many submissions have been submitted per user for each project or form
2. Form Access.  The users in your organisation have access to a form and why they have access or do not have access. This report considers the projects a user has access to, their security groups and their security roles as well as whether or not the form has been deleted or blocked.

Performance Improvements

As the number of people using Smap increases the size of data tables also increases and it becomes apparent that additional indexes are required.  2 new indexes were added in this release to improve the performance of messaging and submission processing.

There have been lots of mini updates over the last 4 months but no formal new releases until now. It is November and its time to get back to monthly releases.

New Features

1. A user can belong to more than one organisation. 

Many people find that they are working on multiple projects in different organisations.  Previously you would have needed more than one logon or would have had to keep asking the organisational administrator to move you from project to project.  Now however you can belong to multiple organisations, you can select the organisation you want to work in by clicking on your profile in any page.

All you projects, security groups and role are preserved for all the organisations that you belong to.  Hence you don’t need to set yourself up each time you switch organisations.  The security groups can be different between organisations so you might be an administrator in one and an enumerator in another.

To set this up go to the users admin page, select a user and then click on the organisations that they have access to.  Note you need to have “organisational admin” privilege to do this.

2. Set Max Image Size from Server

You can now specify the maximum image size in the fieldTask options on the user administration page.  This maximum value will be set on the phones when you refresh.

3. Referencing the survey key (HRK) and preloads in the advanced filter

You can now create filters such as: ${_hrk} = ‘abc 001’ and ${_device} = ‘1111111’