...
| Erweitern | ||||
|---|---|---|---|---|
| ||||
This page gives a practical example to status management between hotelkit and your system. Check necessaties and a step by step walkthrough.
|
...
Characteristics
Importing of tasks comes with special characteristics as a task can change its status and has a workflow to follow. The partner can import the tasks, created in his system, to hotelkit where the customer then can process it the same way as if it was in the partners system. The status changes will be pushed back to the partner. That way the partner controls the workflows as if the tasks was handled in his backend system.
...
| Codeblock |
|---|
PUT /setup/requests
{
"type":"guestRequest",
"labelForCustomer":{
"de_DE":"Gästewunsch",
"en_US":"Guest request"
},
"content":"true",
"link":"true",
"title":"true",
"referenceID":"true",
"attachements":"false",
"enabledByDefault":"true",
"text":false,
"sendRecipients":false,
"hasActions":true
} |
Enable Request
Before sending requests to a client, the requestType must be enabled for the respective client.
| Codeblock |
|---|
PUT /setup/customer
{
"enabledRequests":["guestRequest"]
} |
To check imports in your test-environment, please make sure you are set as a recipient to read the import. This only applies in the test-environment.
Task Import
At first the task will be created at POST /requests and after that the status may be changed several times.
...
| Codeblock |
|---|
POST /requests?type=guestRequest
{
"title":"Extra towel in room #404",
"content":{
"Comment of guest":"Please in XL"
},
"link":"https://hotelkit.net/demo/123", //link to partners details
"referenceID":"123",
"actions":[
{
"type":"decline",
"label":"Decline",
"labelDone":"Declined",
"labelType":"error",
"isDone":true,
"information":{
"text":{
"required":true,
"type":"text",
"label":"Reason"
}
}
},
{
"type":"accept",
"label":"AcceptResolve",
"labelDone":"AcceptedCompleted",
"labelType":"success",
"isDone":true
},
]
} |
...