DeleteRoom
RPC Configuration
Rpc Name:
Plain: DeleteRoom
Sha1: 4425403bc129e46e4e59cf033b69545215df375b
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"room_id" : int
@param int building_id
@param int room_id
@return array
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.
ADMINISTRATOR
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
Sample Request
->
{
"building_id": 131,
"room_id": 7933
}
<-
{
"msg": "Raum wurde gel\u00f6scht."
}