You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/changelog.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,40 @@ sidebar_label: API Changelog
6
6
7
7
⚠ Consider subscribing to our [**API Newsletter**](http://eepurl.com/g2EiC1) to be notified about upcoming API changes in the future.
8
8
9
+
## Version 1.14
10
+
11
+
### Manifest API: New ticketAction type delete`
12
+
13
+
A new `delete` ticketAction type has been introduced for the [Manifest API](general/manifest-api). This means that a dedicated delete button can be availble to tickets. The action type `delete` should be added to the ticketActions array when updating the channel using the [Manifest API](general/manifest-api).
14
+
15
+
The delete action type accepts one kind of config: `{ forceTagging: true }` . Any other action config given will throw an error.
16
+
As with other ticketActions the delete type requires an `id` and `labels` for the 3 supported languages: 'en', 'de', 'fr'.
17
+
18
+
- webhooks: If configured, the delete action will trigger webhooks.
19
+
- action reset: The delete action can be reset using the [Ticket API's error handling](inbox/ticket-api#error-handling) route where `:actionId` will be `delete`.
20
+
21
+
Manifest API ticketAction example
22
+
```json
23
+
// ...
24
+
"inbox": {
25
+
"ticketActions": [
26
+
{
27
+
"type": "delete",
28
+
"id": "delete-id",
29
+
"label": {
30
+
"en": "Delete",
31
+
"de": "löschen",
32
+
"fr": "Supprimer"
33
+
},
34
+
"config": {
35
+
"forceTagging": true//optional
36
+
}
37
+
}
38
+
// ...
39
+
],
40
+
// ...
41
+
```
42
+
9
43
## Version 1.13
10
44
11
45
The following changes to the API are scheduled to be deployed in **calendar week 11**. As all of these changes are **New** additions to existing behavior, there should be no action required by Developers. The impacted documentation pages and swagger specifications have already been updated accordingly.
|`type`| Type of the Ticket Action. At the moment we support `reply`, `template_reply` and `button` actions. There may be multiple actions of the same type. |
88
+
|`type`| Type of the Ticket Action. At the moment we support `reply`, `template_reply`, `delete` and `button` actions. There may be multiple actions of the same type. |
89
89
|`id`| Identifier of the Action. Each Action within a manifest must have a different identifier. Pattern regular expression: `^[a-zA-Z0-9-_]{1,256}$`|
90
90
|`label`| Button labels for different locales. Locale is selected depending on user settings. |
91
91
|`config`| Configuration options for this Ticket Action. |
|`approvalProcess`| Boolean (default is `true`) controlling whether the Approval Process feature should be applied for this Ticket Action. Only supported for `reply` and `template_reply` at this moment |
107
107
|`templates.url`| URL to fetch templates for the `template_reply` action from. Required for the `template_reply` action. |
|`forceTagging`| Boolean (default is `true`) controlling whether the feature forcing the user to add tag(s) to the ticket should be applied for this Ticket Action. |
109
+
|`forceTagging`| Boolean (default is `true`) controlling whether the feature forcing the user to add tag(s) to the ticket should be applied for this Ticket Action. (The action of type: `delete` only accepts a config of `forceTagging` . Any other config for the type `delete` will throw an error.) |
|`followupId`| The identifier of the Reply Followup that has failed to be processed. Only required for `reply` and `template_reply` actions. |
382
381
|`reason`| Optional human readable reason why the Ticket Action has failed. |
382
+
|`followupId` (optional) | The identifier of the Reply Followup that has failed to be processed. Only required for `reply` and `template_reply` actions. |
0 commit comments