App versions

Mostly historical

This page dates from before the app was published on Google Play and the App Store. Day-to-day updates are now delivered through the stores, so you will rarely need anything here. It is still documented because the version list and the forced-update mechanism behind it remain in place.

The App Versions page is where administrators register builds of the mobile monitoring app and control which version users are required to upgrade to. It is reached from the App Versions link in the sidebar and is administrator only; other roles see a permission-denied message.

The App Versions list

The page shows a table of versions, sorted with the newest version code first. Its columns are:

Column	What it shows
Code	The version code (a number)
Name	The version name
Number installed	How many monitors are on that version
Number requisite	How many users are required to upgrade to it
Download URL	A Download link to the build
Open	A link into the version’s detail page

Adding a version

Click New App Version to open the dialog titled “New App Version”. Its fields are:

• Version Code: a whole number greater than zero.
• Name.
• Download Url: the link to the build.

The version detail page

Clicking Open on a row takes you to that version’s detail page. It shows a Details card with the version’s code, name and a link to the build, a Current Users card listing the monitors currently on this version (with their last sync), and a Requisite Users card listing the monitors required to upgrade.

On the newest version’s detail page, alongside the rollout actions, you also get an edit control (to change the Version Code, Name and download link) and a delete control. Older versions do not show these controls. A version can only be deleted when no users are required to upgrade to it.

Releasing a version

The rollout actions appear on the detail page of the newest version only, together with the edit and delete controls above. Older versions do not show them, because you only ever roll forward. Each action sets the “required” version for a different group of users.

A rollout sends nothing to anyone. It only marks the version as required; the next time one of those users’ apps tries to sync, the server refuses the sync with an “Update Required” message that carries the download link, and the app cannot sync again until it has been updated. A user who never opens the app will not notice anything.

• Rollout Everywhere: opens the confirmation dialog “Confirm global rollout” with the text “Really release to all users?” and a Release button. This requires the version for every user.
• Rollout To Coordinators: pick a Country. This requires the version for that country’s coordinators (project staff).
• Rollout To Project: pick a Project. This requires the version for that project’s staff and region officials.
• Rollout To Country: pick a Country. This requires the version for that country’s project staff, region officials and country officials.

A global rollout reaches everyone

Rollout Everywhere sets the required version for all users at once. Confirm you have the correct version open before pressing Release.

The Install App page

The build itself is served from a public Install App page at /install_app. This is the page the Download Monitoring App sidebar link points to. It walks a user through downloading and installing the app and offers a Download button. Because it is public, you can share its link with anyone who needs to install the app.

Next: The Configuration menu