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.
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.
Example: You create a Confirmation Activity and set the fulfilment to "Fulfil with Honour". This means the user must simply open the activity.
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:
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.
A new Classroom Activity can be created to accommodate any overflow.
The length of a video upload should not exceed 3mins.