LastGuideDataUpdate

Class Description

Loads the Date of the last modification of the Guide's Data. If there was non, unix timestamp 0, or 01.01.1970 in ISO Formatting (1970-01-01T00:00:00+00:00) will be returned.

RPC Configuration

Rpc Name:

Plain: LastGuideDataUpdate
Sha1: 111be2b733147631ded64563800caa3d4790a36c

Rpc Call

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

Rpc Parameters:

"building_id" : int,
"isoDateFormatting" : bool =  

Parameter Description

@param int building_id The Building ID identifying the Guide and locking the context.

@param bool isoDateFormatting When true, ISO 8601 Format will be returned instead of Unix timestamp.

@throws BuildingNotFoundException Will throw Exception, if Building does not exist.

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:

building_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.

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.

STANDARD_USER

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:

true

Cache Time to Live:

60

Sample Request

->

{
    "building_id": 131
}

<-

1737450776