Zum Hauptinhalt springen

CreateOrUpdateTagProperties

Class Description

RPC Configuration​

Rpc Name:​

Plain: CreateOrUpdateTagProperties
Sha1: d463c191e52271594c16a5fa015d1eb438854f24
Rpc Call

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

Rpc Parameters:​

"tag_id" : string,
"width" : float,
"height" : float,
"azimuth" : float,
"position" : ?object = 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:​

tag_id

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​

->

{
"tag_id": "Wt8jFR4A",
"width": 150,
"height": 150,
"azimuth": 150
}

<-

false