SetMaximumAmountOfVisitors
RPC Configuration
Rpc Name:
Plain: SetMaximumAmountOfVisitors
Sha1: e8e9c835547e534ec6beb43bb8337ec5976ae878
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"room_id" : int,
"value" : int
Saves the the corona images from the formdata request.
@param int building_id The id of the building
@param int room_id The id of the room to write into
@param int value The value to set as the new maxium
@return bool The success.
Requires Login:
true
Requires Context:
The context providing parameter can either be a contagt-id (8-Bytes, Alphaumeric) or an integer as a building id. The context parameter name should make the choice obviouse, the type has not to be defined manually.
true
Requires contextParamName:
building_id
Requires WriteAccess:
Only accounts that have an explicit write access to the defined context can execute this RPC, no matter if the authentication level matches or not.
true
Requires AuthenticationLevel:
Authentication levels allow the SuperUser to define a by-RPC granular access configuration. If RPCs are chained in a single unified call and lenient is enabled, all allowed RPCs will be executed, while execution will fail entirely with lenient set to false.
STANDARD_USER
Requires Subbuilding Merge Strategy:
SUBBUILDING_ONLY
Cache Configuration
All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache
and readonly.
Cache enabled:
false