LoadPlugins
RPC Configuration
Rpc Name:
Plain: LoadPlugins
Sha1: 70f4e600a1c8b8bc6ced20d61f5d63c527c1232a
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"load_all" : string|bool =
Building ID is transmitted for context control!
@param int building_id
@param bool load_all
@return array|bool
@internal param room_id
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
Has Named Parameters:
false
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.
false
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:
REPLACE
Cache Configuration
All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache
and readonly.
Cache enabled:
true
Cache Time to Live:
60
Sample Request
->
{
"building_id": 131
}
<-
[]