-
Notifications
You must be signed in to change notification settings - Fork 5
/
tr.dict.combodo-webhook-integration.php
214 lines (199 loc) · 19.1 KB
/
tr.dict.combodo-webhook-integration.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
<?php
/**
* Localized data
*
* @copyright Copyright (C) 2010-2024 Combodo SAS
* @license https://opensource.org/licenses/AGPL-3.0
*
*/
/**
*
*/
Dict::Add('TR TR', 'Turkish', 'Türkçe', [
'ActionGoogleChatNotification:message' => 'Message~~',
'ActionMicrosoftTeamsNotification:additionalelements' => 'Additional elements to include~~',
'ActionMicrosoftTeamsNotification:message' => 'Basis message~~',
'ActionMicrosoftTeamsNotification:theme' => 'Theme~~',
'ActionRocketChatNotification:additionalelements' => 'Bot information~~',
'ActionRocketChatNotification:message' => 'Basis message~~',
'ActionSlackNotification:Payload:BlockKit:UserInfo' => 'Notification from <%2$s|%1$s> (%3$s)~~',
'ActionSlackNotification:additionalelements' => 'Additional elements to include~~',
'ActionSlackNotification:message' => 'Basis message~~',
'ActionWebhook:advancedparameters' => 'Advanced parameters~~',
'ActionWebhook:baseinfo' => 'General information~~',
'ActionWebhook:moreinfo' => 'More information~~',
'ActionWebhook:requestparameters' => 'Request parameters~~',
'ActionWebhook:webhookconnection' => 'Webhook connection~~',
'Class:ActionGoogleChatNotification' => 'Notification by Google Chat',
'Class:ActionGoogleChatNotification+' => 'Send a notification as a Google Chat message in a space~~',
'Class:ActionGoogleChatNotification/Attribute:message' => 'Message~~',
'Class:ActionGoogleChatNotification/Attribute:message+' => 'Message that will be displayed in the chat, only plain text is supported for now.~~',
'Class:ActionGoogleChatNotification/Attribute:prepare_payload_callback+' => 'PHP method to prepare payload data to be sent during the webhook call. Use this if the standard options are not flexible enough or if your payload structure must be dynamically built.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($aContextArgs, $oLog, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $aContextArgs, $oLog, $oAction)
IMPORTANT: If set, the \'message\' will be ignored.~~',
'Class:ActionMicrosoftTeamsNotification' => 'Notification by Microsoft Teams',
'Class:ActionMicrosoftTeamsNotification+' => 'Send a notification as a Microsoft Teams message in a channel~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:image_url' => 'Medallion picture~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:image_url+' => 'URL of the image to display as a medallion in the message card, it must be publicly accessible on the internet for Microsoft Teams to be able to display it~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_delete_button' => 'Delete button~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_delete_button+' => 'Include a button below the message to delete the object in '.ITOP_APPLICATION_SHORT.'~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_delete_button/Value:no' => 'No~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_delete_button/Value:yes' => 'Yes~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_list_attributes' => 'Attributes from~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_list_attributes+' => 'Display additional attributes below the message. They can be either from the usual \'list\' view or the custom \'msteams\' view of the object triggering the notification . Note that the \'msteams\' view must be defined in the datamodel first (zlist)~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_list_attributes/Value:list' => 'the usual list view~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_list_attributes/Value:msteams' => 'the custom "msteams" view~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_modify_button' => 'Modify button~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_modify_button+' => 'Include a button below the message to edit the object in '.ITOP_APPLICATION_SHORT.'~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_modify_button/Value:no' => 'No~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_modify_button/Value:yes' => 'Yes~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_other_actions_button' => 'Other actions buttons~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_other_actions_button+' => 'Include other actions (such as transitions available in the current state) below the message~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_other_actions_button/Value:no' => 'No~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_other_actions_button/Value:specify' => 'Specify~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:include_other_actions_button/Value:yes' => 'Yes~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:message' => 'Message~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:prepare_payload_callback+' => 'PHP method to prepare payload data to be sent during the webhook call. Use this if the standard options are not flexible enough or if your payload structure must be dynamically built.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($aContextArgs, $oLog, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $aContextArgs, $oLog, $oAction)
IMPORTANT: If set, the \'title\', \'message\' and all \'additional elements\' will be ignored.~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:specified_other_actions' => 'Other actions codes~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:specified_other_actions+' => 'Specify which actions to include as buttons below the message. Should be a comma separated list of the actions codes (eg. \'ev_reopen, ev_close\')~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:theme_color' => 'Highlight color~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:theme_color+' => 'Highlight color of the message card in Microsoft Teams, must be a valid hexadecimal color (eg. FF0000)~~',
'Class:ActionMicrosoftTeamsNotification/Attribute:title' => 'Title~~',
'Class:ActionRocketChatNotification' => 'Notification by Rocket.Chat',
'Class:ActionRocketChatNotification+' => 'Send a notification as a Rocket.Chat message in a channel or to a user~~',
'Class:ActionRocketChatNotification/Attribute:bot_alias' => 'Alias~~',
'Class:ActionRocketChatNotification/Attribute:bot_alias+' => 'Overrides the default bot alias, will appear before the username of the message~~',
'Class:ActionRocketChatNotification/Attribute:bot_emoji_avatar' => 'Emoji avatar~~',
'Class:ActionRocketChatNotification/Attribute:bot_emoji_avatar+' => 'Overrides the default bot avatar, can be any Rocket.Chat emojis (eg. :ghost:, :white_check_mark:, ...). Note that if an URL avatar is set, the emoji won\'t be displayed.~~',
'Class:ActionRocketChatNotification/Attribute:bot_url_avatar' => 'Image avatar~~',
'Class:ActionRocketChatNotification/Attribute:bot_url_avatar+' => 'Overrides the default bot avatar, must be an absolute URL to the image to use~~',
'Class:ActionRocketChatNotification/Attribute:message' => 'Message~~',
'Class:ActionRocketChatNotification/Attribute:message+' => 'Message that will be displayed in the chat~~',
'Class:ActionRocketChatNotification/Attribute:prepare_payload_callback+' => 'PHP method to prepare payload data to be sent during the webhook call. Use this if the standard options are not flexible enough or if your payload structure must be dynamically built.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($aContextArgs, $oLog, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $aContextArgs, $oLog, $oAction)
IMPORTANT: If set, the \'message\' and all \'bot information\' will be ignored.~~',
'Class:ActionSlackNotification' => 'Notification by Slack',
'Class:ActionSlackNotification+' => 'Send a notification as a Slack message in a channel or to a user~~',
'Class:ActionSlackNotification/Attribute:include_delete_button' => 'Delete button~~',
'Class:ActionSlackNotification/Attribute:include_delete_button+' => 'Include a button below the message to delete the object in '.ITOP_APPLICATION_SHORT.'~~',
'Class:ActionSlackNotification/Attribute:include_delete_button/Value:no' => 'No~~',
'Class:ActionSlackNotification/Attribute:include_delete_button/Value:yes' => 'Yes~~',
'Class:ActionSlackNotification/Attribute:include_list_attributes' => 'Attributes from~~',
'Class:ActionSlackNotification/Attribute:include_list_attributes+' => 'Display additional attributes below the message. They can be either from the usual \'list\' view or the custom \'slack\' view of the object triggering the notification . Note that the \'slack\' view must be defined in the datamodel first (zlist)~~',
'Class:ActionSlackNotification/Attribute:include_list_attributes/Value:list' => 'the usual list view~~',
'Class:ActionSlackNotification/Attribute:include_list_attributes/Value:slack' => 'the custom "slack" view~~',
'Class:ActionSlackNotification/Attribute:include_modify_button' => 'Modify button~~',
'Class:ActionSlackNotification/Attribute:include_modify_button+' => 'Include a button below the message to edit the object in '.ITOP_APPLICATION_SHORT.'~~',
'Class:ActionSlackNotification/Attribute:include_modify_button/Value:no' => 'No~~',
'Class:ActionSlackNotification/Attribute:include_modify_button/Value:yes' => 'Yes~~',
'Class:ActionSlackNotification/Attribute:include_other_actions_button' => 'Other actions buttons~~',
'Class:ActionSlackNotification/Attribute:include_other_actions_button+' => 'Include other actions (such as transitions available in the current state) below the message~~',
'Class:ActionSlackNotification/Attribute:include_other_actions_button/Value:no' => 'No~~',
'Class:ActionSlackNotification/Attribute:include_other_actions_button/Value:specify' => 'Specify~~',
'Class:ActionSlackNotification/Attribute:include_other_actions_button/Value:yes' => 'Yes~~',
'Class:ActionSlackNotification/Attribute:include_user_info' => 'User info.~~',
'Class:ActionSlackNotification/Attribute:include_user_info+' => 'Display user information (full name) below the message~~',
'Class:ActionSlackNotification/Attribute:include_user_info/Value:no' => 'No~~',
'Class:ActionSlackNotification/Attribute:include_user_info/Value:yes' => 'Yes~~',
'Class:ActionSlackNotification/Attribute:message' => 'Message~~',
'Class:ActionSlackNotification/Attribute:prepare_payload_callback+' => 'PHP method to prepare payload data to be sent during the webhook call. Use this if the standard options are not flexible enough or if your payload structure must be dynamically built.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($aContextArgs, $oLog, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $aContextArgs, $oLog, $oAction)
IMPORTANT: If set, the \'message\' and all \'additional elements\' will be ignored.~~',
'Class:ActionSlackNotification/Attribute:specified_other_actions' => 'Other actions codes~~',
'Class:ActionSlackNotification/Attribute:specified_other_actions+' => 'Specify which actions to include as buttons below the message. Should be a comma separated list of the actions codes (eg. \'ev_reopen, ev_close\')~~',
'Class:ActionWebhook' => 'Action by Webhook (generic)',
'Class:ActionWebhook+' => 'Webhook call for any kind of application~~',
'Class:ActionWebhook/Attribute:asynchronous+' => 'Whether this action should be executed in background or not (mind that global setting for webhook actions is the "prefer_asynchronous" conf. parameter of the "combodo-webhook-action" module)~~',
'Class:ActionWebhook/Attribute:headers' => 'Headers~~',
'Class:ActionWebhook/Attribute:headers+' => 'Headers of the HTTP request, must be one per line (eg. \'Content-type: application/json\')~~',
'Class:ActionWebhook/Attribute:language' => 'Language~~',
'Class:ActionWebhook/Attribute:language+' => 'Language of this notification, mostly used when searching for notifications but might also be used to translate attributes label~~',
'Class:ActionWebhook/Attribute:method' => 'Method~~',
'Class:ActionWebhook/Attribute:method+' => 'Method of the HTTP request~~',
'Class:ActionWebhook/Attribute:method/Value:delete' => 'DELETE~~',
'Class:ActionWebhook/Attribute:method/Value:get' => 'GET~~',
'Class:ActionWebhook/Attribute:method/Value:head' => 'HEAD~~',
'Class:ActionWebhook/Attribute:method/Value:patch' => 'PATCH~~',
'Class:ActionWebhook/Attribute:method/Value:post' => 'POST~~',
'Class:ActionWebhook/Attribute:method/Value:put' => 'PUT~~',
'Class:ActionWebhook/Attribute:path' => 'Path~~',
'Class:ActionWebhook/Attribute:path+' => 'Additional path to append to the connection URL (eg. \'/some/specific-endpoint\')~~',
'Class:ActionWebhook/Attribute:payload' => 'Payload~~',
'Class:ActionWebhook/Attribute:payload+' => 'Data sent during the webhook call, most of the time this is a JSON string. Use this if your payload structure is static.
IMPORTANT: Will be ignored if \'Prepare payload callback\' is set~~',
'Class:ActionWebhook/Attribute:prepare_payload_callback' => 'Prepare payload callback~~',
'Class:ActionWebhook/Attribute:prepare_payload_callback+' => 'PHP method to prepare payload data to be sent during the webhook call. Use this if your payload structure must be dynamically built.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($aContextArgs, $oLog, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $aContextArgs, $oLog, $oAction)
IMPORTANT: If set, the \'Payload\' attribute will be ignored.~~',
'Class:ActionWebhook/Attribute:process_response_callback' => 'Process response callback~~',
'Class:ActionWebhook/Attribute:process_response_callback+' => 'PHP method to process the webhook call response.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($oResponse, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $oResponse, $oAction)
- $oResponse can be null in some cases (eg. request failed to send)~~',
'Class:ActionWebhook/Attribute:remoteapplicationconnection_id' => 'Connection~~',
'Class:ActionWebhook/Attribute:remoteapplicationconnection_id+' => 'Connection information to use when status is \'in production\'~~',
'Class:ActionWebhook/Attribute:test_remoteapplicationconnection_id' => 'Test connection~~',
'Class:ActionWebhook/Attribute:test_remoteapplicationconnection_id+' => 'Connection information to use when status is \'being tested\'~~',
'Class:ActioniTopWebhook' => 'Action by '.ITOP_APPLICATION_SHORT.' REST API',
'Class:ActioniTopWebhook+' => 'Webhook call to a remote iTop application~~',
'Class:ActioniTopWebhook/Attribute:headers+' => 'Headers of the HTTP request, must be one per line (eg. \'Content-type: application/x-www-form-urlencoded\')
IMPORTANT:
- \'Content-type\' should be set to \'application/x-www-form-urlencoded\' for iTop, even though we send JSON
- A \'Basic authorization\' header will be append automatically to request during sending, containing the credentials from the selected connection~~',
'Class:ActioniTopWebhook/Attribute:payload' => 'JSON data~~',
'Class:ActioniTopWebhook/Attribute:payload+' => 'The JSON payload, must be a JSON string containing the operation name and parameters, see documentation for detailed information~~',
'Class:ActioniTopWebhook/Attribute:prepare_payload_callback+' => 'PHP method to prepare payload data to be sent during the webhook call. Use this if your payload structure must be dynamically built.
You can use 2 types of methods:
- From the triggering object itself (eg. UserRequest), must be public. Example: $this->XXX($aContextArgs, $oLog, $oAction)
- From any PHP class, must be static AND public. Name must be name fully qualified. Example: \SomeClass::XXX($oObject, $aContextArgs, $oLog, $oAction)
IMPORTANT: If set, the \'JSON data\' attribute will be ignored.~~',
'Class:EventWebhook' => 'Webhook triggered',
'Class:EventWebhook/Attribute:action_finalclass' => 'Final class~~',
'Class:EventWebhook/Attribute:headers' => 'Headers~~',
'Class:EventWebhook/Attribute:payload' => 'Payload~~',
'Class:EventWebhook/Attribute:response' => 'Response~~',
'Class:EventWebhook/Attribute:webhook_url' => 'Webhook URL~~',
'Class:RemoteApplicationConnection' => 'Remote application connection~~',
'Class:RemoteApplicationConnection/Attribute:actions_list' => 'Webhook notifications~~',
'Class:RemoteApplicationConnection/Attribute:actions_list+' => 'Webhook notifications using this connection~~',
'Class:RemoteApplicationConnection/Attribute:environment' => 'Environment~~',
'Class:RemoteApplicationConnection/Attribute:environment+' => 'Type of environment of the connection~~',
'Class:RemoteApplicationConnection/Attribute:environment/Value:1-development' => 'Development~~',
'Class:RemoteApplicationConnection/Attribute:environment/Value:2-test' => 'Test~~',
'Class:RemoteApplicationConnection/Attribute:environment/Value:3-production' => 'Production~~',
'Class:RemoteApplicationConnection/Attribute:remoteapplicationtype_id' => 'Application type~~',
'Class:RemoteApplicationConnection/Attribute:remoteapplicationtype_id+' => 'Type of application the connection is for (use \'Generic\' if yours is not in the list)~~',
'Class:RemoteApplicationConnection/Attribute:url' => 'URL~~',
'Class:RemoteApplicationType' => 'Remote application type~~',
'Class:RemoteApplicationType/Attribute:remoteapplicationconnections_list' => 'Connections~~',
'Class:RemoteApplicationType/Attribute:remoteapplicationconnections_list+' => 'Connections for that application~~',
'Class:RemoteiTopConnection' => 'Remote iTop connection~~',
'Class:RemoteiTopConnection/Attribute:auth_pwd' => 'Auth. password~~',
'Class:RemoteiTopConnection/Attribute:auth_pwd+' => 'Password of the user (on the remote iTop) used for the authentication~~',
'Class:RemoteiTopConnection/Attribute:auth_user' => 'Auth. user~~',
'Class:RemoteiTopConnection/Attribute:auth_user+' => 'Login of the user (on the remote iTop) used for the authentication~~',
'Class:RemoteiTopConnection/Attribute:version' => 'API version~~',
'Class:RemoteiTopConnection/Attribute:version+' => 'Version of the API called (eg. 1.3)~~',
'Class:RemoteiTopConnectionToken' => 'Remote iTop connection using a Token~~',
'Class:RemoteiTopConnectionToken/Attribute:token+' => 'Token~~',
'Dashboard:Integrations:ActionWebhookList:Title' => 'Webhook type actions~~',
'Dashboard:Integrations:Outgoing:Title' => 'Outgoing webhook integrations~~',
'Dashboard:Integrations:Title' => 'Integrations with external applications~~',
'Menu:Integrations' => 'Integrations~~',
'RemoteApplicationConnection:authinfo' => 'Authentication~~',
'RemoteApplicationConnection:baseinfo' => 'General information~~',
'RemoteApplicationConnection:moreinfo' => 'More information~~',
]);