GetActiveModules
RPC Configuration
Rpc Name:
Plain: GetActiveModules
Sha1: a7e7a34b9db4c226f6a50bf66f690250deed6f6c
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"buildingId" : int
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:
buildingId
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
Existing Versionized Executors:
This RPC has an API Level Vrsion Switch, that will allow to execute different paths on differnet API Levels. The accepted and response parameters might change when using a versionized constructor.
getActiveModules_LE22
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
->
{
"buildingId": 131
}
<-
[]