SaveRoomContent
Adds content to a room
of a building.
The Room defined by room_id
must exist within the building defined by
building_id
RPC Configuration
Rpc Name:
Plain: SaveRoomContent
Sha1: 82ee9c44e7112dc40949bbfe532b8c5ffbcba29b
RPCs can be called by their plain name or their SHA1 representation.
Rpc I18n Name:
saveRoomContentI18n
Rpc Parameters:
"building_id" : int,
"room_id" : int,
"data" : array
- Save the Content defined in
data
.data
must be an array of Room Content Definition Objects e.g.:
{
"type":"description",
"ord":0,
"displayname":"Beschreibung",
"content":"Hallo Welt"
}
- Available content types are:
'text','telephone','email','website','hours','owner','fax','room_number','content','equipment','description','media_video','media_audio','free_single','free_multi','campaign_audio'
. - The Data-Field can be transmitted in all requested language sets at once e.g.:
{
"de_DE": "[{\"type\":\"description\",\"ord\":0,\"displayname\":\"Beschreibung\",\"content\":\"Hallo Welt\"}]",
"en_EN": "[{\"type\":\"description\",\"ord\":0,\"displayname\":\"Description\",\"content\":\"\"}]",
"fr_FR": "[{\"type\":\"description\",\"ord\":0,\"displayname\":\"Beschreibung\",\"content\":\"\"}]"
}
Requires Login:
true
Requires 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:
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:
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
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,
"room_id": 7933,
"data": [
{
"type": "room_number",
"ord": 0,
"displayname": "Raum Nummer",
"content": ""
},
{
"type": "owner",
"ord": 1,
"displayname": "Besitzer",
"content": ""
},
{
"type": "telephone",
"ord": 2,
"displayname": "Telefon",
"content": "0621 3009797"
},
{
"type": "fax",
"ord": 3,
"displayname": "Fax",
"content": ""
},
{
"type": "email",
"ord": 4,
"displayname": "E-Mail",
"content": "info@bermudafunk.org"
},
{
"type": "website",
"ord": 5,
"displayname": "Website",
"content": "http:\/\/www.bermudafunk.org"
},
{
"type": "hours",
"ord": 6,
"displayname": "\u00d6ffnungszeiten",
"content": ""
},
{
"type": "equipment",
"ord": 7,
"displayname": "Equipment",
"content": ""
},
{
"type": "description",
"ord": 8,
"displayname": "Beschreibung",
"content": ""
}
]
}
<-
false