GetCustomerImage

RPC Configuration

Rpc Name:

Plain: GetCustomerImage
Sha1: cccf86b382a9b1bd45b11bef9a96f10e84d030f9

Rpc Call

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

Rpc Parameters:

"version" : int,
"tag" : string,
"size" : int = 75,
"includeCategoryFallback" : bool =  

Parameter Description

The 'real' Executor, delivering content based on 'version'
@param integer version

@param String tag

@param integer size

@param boolean includeCategoryFallback

@return string

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

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

Existing Versionized Executors:

Executor Versions

This RPC has an API Level Vrsion Switch, that will allow to execute different paths on differnet API Levels. The accepted and response parameters might change when using a versionized constructor.

GetCustomerImage_LTV9

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

->

{
    "tag": "bMxa6bwY"
}

<-

{
    "tag": "bMxa6bwY",
    "image": "",
    "mimeType": "application\/json"
}