Comment on page
Content activities such as pathways, stories, articles, chat and forums can be completed by the user before the user reaches the locked activity on the pathway. For example: A user may have already previously enrolled on a different pathway or completed a story that is related to the activity. This activity still remains locked/incomplete on the app but is logged as completed in analytics.
This ensures these types of activities do not need to be repeated by the user. As a user enrols or views a pathway auto-completions happen on activity types: pathways, stories, articles, chat, and forums.
In this scenario, you may see more users that have completed the last activity but not the entire pathway.
You can safely change the fulfilment on activities as this will only affect users who have not completed the activity. Logs for users who have already completed the activity will remain completed with the previous fulfilment.
If you need users to restart to complete the new fulfilment, you will need to reset their logs.
- 1.Required activities were added retrospectively after the pathway was published. This can cause incomplete activities that appear to be skipped. This occurs when the user has already passed the activity on the previously published pathway and has not returned to complete the new required activity. We recommend adding new required activities to the end of the pathway, notifying users ahead of publishing or only adding retrospective optional activities.
- 2.Logs were not fully synced from the device. iOS/Android apps store offline logs on the device to allow limited offline usage and minimal internet bandwidth. We QA test on an array of devices, simulators, and networks to ensure local-to-server syncs. However, factors and unknown variables of the user's device, network, or even battery state may cause log sync delays making it appear they have skipped an activity. In these scenarios, we recommend waiting for the user to reopen the app or reaching out to the user to open their device and complete any missed activities. Logs are stored on the device and will continue to attempt to sync to the server until successful but requires the app to be open.
You should be prompted to publish your pathway once it is ready. If not, you can select PATHWAY from the top menu, and then select PUBLISH.
Publish a pathway
When creating a Confirmation Activity you can set the fulfilment to: Honour, Upload, or Upload & Review.
Once you have chosen a fulfilment option and a user has met that fulfilment, they will not be able to re-do the activity should you choose to change the fulfilment option. For users to re-do the activity, clear the activity logs of everyone who previously completed the activity.
Clear logs to reset a user's activity state
A few days later, you decide to change the fulfilment to "Upload Fulfilment" - meaning the user must upload a file to fulfil the activity.
Anyone who has already completed the activity with the previous fulfilment requirement will not be able to re-do the activity, i.e. upload a file. Also, their activity will no longer be read as complete.
To solve this, you will need to clear the logs of users who fulfilled the activity before it was changed - this will then allow them to re-do/fulfil the activity as per the new requirement.
If you would like to reset a user's progress or clear one/all of their logs, open the Pathway Editor and select any activity that they have completed. Select "View Logs" to open a list of all users who have completed the activity.
You can then choose to "Clear Log" for that specific activity, or select "Clear All Logs" to delete all of the user's logs for the pathway. The user will need to restart / redo the pathway.
If you have updated the name and/or description of a certificate and the change is not reflecting on the app, this may be because the file is cached to the device. When the app reloads it should update.
If the activity is saved with a past date/time, it will not reflect on the pathway, i.e. a user can not book a date/time in the past.
When you duplicate a pathway, everything will be copied except for:
- 3.Events / Bookings
For physical pathway actvities that make use of check-ins, the precise location is used on a device to determine if the user is at the venue.
GPS coordinates are not collected server side, but merely track the distance the user was at when they checked in.
Users do not have to share their location in order to check-in, and do not have to be within the radius to proceed.
The distance is tracked to allow admins to follow up on users that may have not been there, or if their distance was far off. This is so we have some sort of info on how far users were away when they checked in.
When a user books/confirms their attendance, it counts as 1 seat. Once all seats are booked no more bookings can be made.
The length of a video upload should not exceed 3mins.
If you have accessed multiple pathways, you can easily switch between them. Select the map-marker icon (top right) and then select the Pathway you want to switch to.
When you switch pathways, the UI colours may change depending on the theme pathway.
Pathways are currently auto-ordered by latest (updated/published), and alphabetical per category.