Hi!
>> I have the very same issue: Although "MultipleBookings" is set to 1,
>> people
>> in Lightning are able to book a resource even if the resource isn't
>>
>> available. They get a warning, but in case they ignore it, the resource
>>
>> auto-accepts the event. I think the right behavior for sogo would be to
>> reject the invitation to the second event.
>>
>> The web interface handles this differently: one cannot save the event
>> when
>> a resource is already busy (but without any message informing the user).
>>
>
>
> "I think the right behavior for sogo would be " to allow configuration by
> the
> admin, so he can choose whatever he thinks best.
>
I object: The behaviour of SOGo regarding resources is described as
"first come - first serve". Additionally there is "MultipleBookings" to
control the amount of bookings a resource can handle.
There is nothing left to decide or configure: "first come - first serve"
perfectly fits. It is just that it is not really implemented that way.
In case you want to add an overrule button to the game, add an ACL allowing
an administrative person in charge for a resource to "Respond To" all kind
of events. Done.
-- Adi
--
[email protected]
https://inverse.ca/sogo/lists
