TestMethodRequiresContext
RPC Configuration
Rpc Name:
Plain: TestMethodRequiresContext
Sha1: 2a3e4b35b518d8dd3013e0c1ffb223403b50e292
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"param1" : int,
"param2" : 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:
param1
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
->
[]