OTRS/i18n — Malay @ Weblate: This field must be empty or contain a positive number.

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.

	English	Malay	Actions
	Should requests causing an error be triggered again at a later time?
	Initial retry interval
	Interval after which to trigger the first retry.
	Note: This and all further retry intervals are based on the error handling module execution time for the initial request.
	Factor for further retries
	If a request returns an error even after a first retry, define if subsequent retries are triggered using the same interval or in increasing intervals.
	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 (21=2 minutes), 10:07 (22=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?	Adakah anda benar-benar mahu memadam invoker ini?
	Invoker Details	Butiran Invoker
	The name is typically used to call up an operation of a remote web service.	Nama biasanya digunakan untuk memanggil operasi perkhidmatan web jauh.
	Invoker backend	Invoker backend
	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.	Modul OTRS invoker backend ini akan dipanggil untuk menyediakan data untuk dihantar ke sistem jauh, dan untuk memproses data respons.
	Mapping for outgoing request data	Pemetaan untuk permintaan data keluar
	Configure	Konfigurasi
	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.	Data dari invoker daripada OTRS akan diproses oleh pemetaan ini, untuk mengubah kepada jenis data sistem jauh menjangka.

Loading…

No matching activity found.

Browse all component changes

Glossary

English	Malay
No related strings found in the glossary.

String information

Source string description

Template: AdminGenericInterfaceErrorHandlingRequestRetry

String age

4 years ago

Source string age

4 years ago

Translation file

i18n/otrs/otrs.ms.po, string 651