Best practice forum (Archived)
This forum discussion has been removed
Hi Eric
I'm new to Totara and we are currently setting it up with help from a third party company. They told us that staff cannot sign up for repeat instances of a face to face. We are therefore setting them up in monthly batches as new topics, with dates attached. In our scenario if someone doesn't make a session then there won't be one the same month. It also allows us to hide past sessions. I hope this helps and is what you are referring to. Apparantly there will be a fix sometime..?
Rob
Hi Eric,
I am working wioth Rob to deploy Totara presently. As Rob says above, Totara version 2.4 introduced a new function that stops users booking on sessions within the same activity within a course, so a person cannot book and attend multiple sessions within an activity, within a course. We have raised this with Totara support as a key issue and are waiting for a resolve to this as changing the function would require significant changes to core code. You were able to book users on to multiple sessions within course activities upto and including v2.2.
Our workaround, it to set up multiple topics, each containing 3-6 month blocks of sessions which should allow you to rebook users on to multiple sessions within a course, but this wont work for workshops where staff can attend as many as they wish within a short or longer timeframe. We havent found a work around for this type of course in v2.4 [yet].
We are still investigating how this impacts on course completion criteria, so you would have to report on course, F2F session and F2F Status to get your attendance reports.
Hope this is helpful,
Richard
Hi Amir
Upto and including version 2.2 we could book users on multiple sessions within courses in the same activity without any customisation, the change was recently made in version 2.4 and confirmed by Totara Support when we queried it. Upto this version you could only rebook a user once attendance had been marked, but once attendance was marked you could rebook them onto the same activity as may times as required.
What is your workaround?
Richard
Hi,
I just wanted to clarify a few things about the past, current and future behaviour with regards to multiple signups.
- Amir is correct that signing up multiple times to the same session were never supported from the earliest versions of f2f
- However, it seems Richard is also correct that once attendance has been taken you can re-signup. This was a bug that we never knew about until today!
- While refactoring the code for 2.4 it seems we also fixed that bug, so in 2.4 it is again not possible to sign up multiple times.
- Because so many people have requested this feature, we are working on it, and we will include it in the upcoming 2.5 release (due Sept/Oct).
- The 2.5 feature will make multiple signups an optional setting, and if enabled you will be able to signup even before attendance has been taken. It will also handle some of the edge cases that enabling this feature will introduce such as grades, attendence history etc.
Hopefully that clarifies things!
Simon
Hi Simon
Thanks for clarifying and confirming we werent going mad (!) - if you can incorporate this [back] in to 2.5 that would be great, and as its due November-ish we can wait for that and continue the work-around until that point.
Much appreciated, and thanks.
Richard
Hi Eric,
If you are running version 2.2 you can book users on multiple sessions within a topic as many timesa as you need to as longas the attendance is marked for previously booked sessions, ie you cant rebook a users if they have a F2F booking without marking attendance.
if you upgrade to version 2.4 when you try to book a user on a session within the same topic you will receiev an error message and be unable to rebook them.
Our workaround until version 4.5 is to set up separate topics to each hold 3-6 months of sessions, so that you can book a user on a session in quarter 1, and then rebook them in the next 3, 6 or 9 month period. If you go into your course settings you can add more topics there and then you will see topic blocks appear in the course, and you can add F2F activities in each. This also allows admin teams to hide older sessions to make the self service experience more simple.
Does that help?
hi Eric
thats correct, it wont solve the issue for workshops or sucessive sessions. The only workaround for staff who miss a session and need to rebook would be for them to cancel the previous bookings and then rebook - but yes, maintenance becomes more intensive and hopefully the fix in 2.5 will solve this.
Simon, if there is any delay to 2.5 can the fix for this be published as a patch so we can resolve this without any slippage?
Thanks
Richard
Richard,
Yes, once we've integrated it we should be able to provide a patch. We are being more strict with our release dates these days though so 2.5 should be out at the end of October.
Simon
Hi Antonio,
If you're asking about a patch to allow multiple signups, there isn't going to be a patch for 2.4. It will however be part of 2.5 which will be out at the end of October.
Simon
Hi Simon,
do you mean that Totara 2.4 will never allow multiple signups in a single face to face?
We don't plan to upgrade to Totara 2.5 at the end of October, when the first release will be out, but our client really needs this feature because the workaround suggested in the forum doesn't fit to us and our client is stuck from a very long time for this reason.
I seemed to understand that when Totara 2.5 would have been released, this feature would have been be ported also to Totara 2.4.
Am I wrong?
Thank you,
regards
antonio
Hi Antonio,
Unfortunately you are correct. We don't backport significant features to earlier stable release branches because of the risk of introducing new bugs. We want to ensure that the stable release branches are safe to upgrade with minimal changes to the code or UI to ensure that people get the bug fixes we need without introducing potentially unwanted changes.
This is becoming more important as more people use the platform and build customisations on top of it. Just recently we had a situation were a seemingly benign improvement broke someone's site because of a local customisation.
If your client really needs the feature in 2.4 perhaps they might be willing to backport it once 2.5 is out (for their install only)?
Simon