SaveCampaignCategory

RPC Configuration

Rpc Name:

Plain: SaveCampaignCategory
Sha1: 9cd59333c440d0485387c24b8f17d4294270fbdf

Rpc Call

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

Rpc I18n Name:

saveCampaignCategoryI18n

Rpc Parameters:

"building_id" : int,
"campaign_id" : int,
"category_name" : string 

Parameter Description

Building ID is transmitted for context control!
@param int building_id

@param int campaign_id

@param bool isenabled

@return array|bool

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.

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

->

{
    "building_id": 131,
    "campaign_id": 115,
    "category_name": "New Category"
}