The translation has come to an end.
The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not update the repository.

Translation

English Template: AdminGenericInterfaceInvokerDefault
Add Invoker
0/110 · 11
English Persian Actions
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute' and retry factor at '2', retries would be triggered at 10:01 (1 minute), 10:03 (2*1=2 minutes), 10:07 (2*2=4 minutes), 10:15 (2*4=8 minutes), ...
Maximum retry interval
If a retry interval factor of '1.5' or '2' is selected, undesirably long intervals can be prevented by defining the largest interval allowed.
Intervals calculated to exceed the maximum retry interval will then automatically be shortened accordingly.
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum interval at '5 minutes', retries would be triggered at 10:01 (1 minute), 10:03 (2 minutes), 10:07 (4 minutes), 10:12 (8=>5 minutes), 10:17, ...
Maximum retry count
Maximum number of retries before a failing request is discarded, not counting the initial request.
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum retry count at '2', retries would be triggered at 10:01 and 10:02 only.
Note: Maximum retry count might not be reached if a maximum retry period is configured as well and reached earlier.
This field must be empty or contain a positive number.
Maximum retry period
Maximum period of time for retries of failing requests before they are discarded (based on the error handling module execution time for the initial request).
Retries that would normally be triggered after maximum period is elapsed (according to retry interval calculation) will automatically be triggered at maximum period exactly.
Example: If a request is initially triggered at 10:00 with initial interval at '1 minute', retry factor at '2' and maximum retry period at '30 minutes', retries would be triggered at 10:01, 10:03, 10:07, 10:15 and finally at 10:31=>10:30.
Note: Maximum retry period might not be reached if a maximum retry count is configured as well and reached earlier.
Add Invoker
Edit Invoker
Do you really want to delete this invoker? آیا شما واقعا می خواهید این invoker را حذف کنید؟
Invoker Details Invoker اطلاعات
The name is typically used to call up an operation of a remote web service. نام معمولا برای پاسخ یک عملیات از یک وب سرویس از راه دور.
Invoker backend باطن Invoker
This OTRS invoker backend module will be called to prepare the data to be sent to the remote system, and to process its response data. این invoker ماژول باطن OTRS خواهد شد به نام برای آماده سازی داده ها به سیستم از راه دور ارسال می شود، و برای پردازش داده ها پاسخ آن است.
Mapping for outgoing request data نقشه برداری برای درخواست داده های خروجی
Configure تنظیمات
The data from the invoker of OTRS will be processed by this mapping, to transform it to the kind of data the remote system expects. داده ها از فراخواننده OTRS خواهد شد این نقشه برداری پردازش، آن را تبدیل به نوع داده سیستم از راه دور انتظار.
Mapping for incoming response data نگاشت برای پاسخ داده های ورودی
The response data will be processed by this mapping, to transform it to the kind of data the invoker of OTRS expects. پاسخ داده خواهد شد این نقشه برداری پردازش، آن را تبدیل به نوع داده فراخواننده OTRS انتظار.
Asynchronous ناهمگام
Condition وضعیت
Edit this event
This invoker will be triggered by the configured events. این invoker باعث ایجاد حوادث پیکربندی خواهد شد .

Loading…

No matching activity found.
Browse all component changes

Glossary

English Persian
No related strings found in the glossary.

String information

Source string description
Template: AdminGenericInterfaceInvokerDefault
String age
4 years ago
Source string age
4 years ago
Translation file
i18n/otrs/otrs.fa.po, string 657