RequestTagCodes

Class Description

Generates between 1 (default) and 500 (maximum) unique contagt IDs

RPC Configuration

Rpc Name:

Plain: RequestTagCodes
Sha1: 0f2318f00a173cecb14e8c172cdb3035a202cd33

Rpc Call

RPCs can be called by their plain name or their SHA1 representation.

Rpc Parameters:

"count" : int = 1 

Requires Login:

true

Requires Context:

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.

false

Has Named Parameters:

true

Requires WriteAccess:

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:

Context

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:

REPLACE

Cache Configuration

Response Cache

All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache and readonly.

Cache enabled:

false

Sample Request

->

{
    "count": 1
}

<-

[
    "RP5Wlg94"
]