Can the IRIS agent end a booking if no login happens within a certain time?
Hello community!
I have been trying out the IRIS agent, and I was hoping that it would allow us to end a booking, in case of no show.
Does anyone have an idea if this is possible?
Unfortunately, this editor does not allow me to upload an image... (Error 500).
But here a link to a screenshot.
Basically, in Admin > Bookings > Agent settings under Parameters there are following options:
- Early arrival
- Late arrival
- Cancellation of no-show after
- Max overrun
I was hoping Cancellation of no-show after would allow IRIS to end a booking after the set time. But probably this applies if the user ends his slot after the set time?
Unfortunately, the current wiki page about the agent is out of date, and does not describe the IRIS policy settings.
I would be happy to hear about your experience with the Agent, and whether it is possible to have IRIS end a session in case of a "no-show" after a certain time.
Otherwise, I think this would be a necessary feature.
ping: @Lorentz.Pascal
Thank you!
- JJulia Haseleu @jhaseleu
Dear Loïc,
I am currently testing the agent settings. Spontaneously, I would say that it should work as you expect: the booking should be auto-cancelled after the set time in case of a no-show.
I will keep you updated.
Best wishes,
Julia - RIn reply toloicsauteur⬆:Roger Schmidt @rschmidt
Hello everyone
The "Cancellation of no-show after" setting should work. However, it is not the agent, which is actively cancelling the booking, but instead a central service should handles it, based on missing booking logs from the agent.
I guess there will likely be some delay until corresponding bookings are actually cancelled by this central service. I can try finding out more details about this process by asking the developers.
Cheers,
Roger- L@loicsauteur
Hi all,
From the IRIS agent log on IRIS, I can see that users logged in X minutes after start (e.g. 90 min or more). That would be a too long delay for a 30min "Cancellation of no-show after".
FYI: The resource has the a agent policy.
What I noticed, is in the resource's
Optionstab I do not have the Agent box ticked (see screenshot below).
I do not fully understand this tick-box from the info ("Agent: This enables the local agent on the resource to allow login by users with a booking" ). On the PC login through the agent is required for usage. But maybe the ticking this box, would enable also the cancellation?
- JJulia Haseleu @jhaseleu
Hello Loïc,
In my test, it appears that there is a bug. I’ve added a PBI to the backlog and will discuss the issue with the developers in our next sprint meeting.
Best regards,
Julia - In reply toloicsauteur⬆:RRoger Schmidt @rschmidt
Sorry, I cannot tell you exactly what effect this Agent flag has. The agent itself on the instruments does not care about this setting. It might be important for the UI in OpenIRIS, but maybe also for the central services. I am the developer of the agent and don't know all the logic on the server-side. However, I guess it is a good idea to enable this flag when the agent is in use on the instrument.
The communication from the agent to the server is authorized by the correct client ID (GUID) & secret key in the resource settings.
Julia has mentioned that there seems to be a bug on the server not cancelling bookings with no shows. When testing the Agent flag was enabled for this resource.
In the Misuse rules you can set the parameter for late arrival. This setting is taken into account by the agent - it retrieves this information with the booking, and it would not allow authentication if the user has arrived later than the specified number of minutes. I did not experience any issues with this setting - the agent will just skip authentication for corresponding bookings. The counterpart is the early arrival setting in this policy - it should be configured if you want to make sure that nobody can authenticate for a booking > x minutes in the future - depending on the settings the agent will ask to create a new booking (the user will be asked to authenticate and make a booking "on the fly", directly in the agent in an embedded browser).
Cheers,
Roger
- Progresswith handling this problem
- JJulia Haseleu @jhaseleu
The “Cancellation of no-show after” option is now working as expected. Please note that, since scans currently run every 20 minutes, cancellations are processed only on the full hour, or at 20 or 40 minutes past the hour.
We will look into shortening this interval in the near future. - L@loicsauteur
Dear @jhaseleu
Thank you very much!
For me the 20min intervals are currently fine.
It seems to work. It seems like the agent deletes the whole booking in case of no login within the specified time (e.g. 30min). I would have thought that the 30min before cancellation would have stayed in the booking system (i.e. agent ends the slot). But then I will see the entry in the agent log on IRIS the day after...
Thanks again!
Best wishes!