SaveTagCategory

RPC Configuration

Rpc Name:

Plain: SaveTagCategory
Sha1: 9bad55933641abe93ae543add4e666135631b1ad

Rpc Call

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

Rpc I18n Name:

saveTagCategoryI18n

Rpc Parameters:

"tagID" : string,
"category_name" : ?string = null,
"category_handle" : ?string = null,
"category_id" : ?int = null 

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.

true

Requires contextParamName:

tagID

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.

true

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.

LOCAL_ADMINISTRATOR

Requires Subbuilding Merge Strategy:

SUBBUILDING_ONLY

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

->

{
    "tagID": "P205wmTu",
    "category_id": 2
}

<-

{
    "existing": true,
    "category_id": 2,
    "category_name": "Ausgang",
    "category_handle": "#exit"
}