Zum Hauptinhalt springen

SendFeedbackAnswer

Class Description

This class handles the api request for getting all user feedback data.

RPC Configuration

Rpc Name:

Plain: SendFeedbackAnswer
Sha1: e73b9b9c7c4a6fa4d9f31254cf7e89334c0cce38
Rpc Call

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

Rpc Parameters:

"building_id" : int,
"module_id" : int,
"feedback_id" : int,
"answer" : string
Parameter Description

Sends a Email with the text
@return bool if email is sent.

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": 1,
"module_id": 1,
"feedback_id": 1,
"answer": "Dies ist die Antwort"
}

<-

false