OTRS/i18n — Bulgarian @ Weblate: Edit Invoker

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	Bulgarian	Actions
	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 Details	Детайли за заявката
	The name is typically used to call up an operation of a remote web service.	Името обикновено се използва за извикване на операция на дистанционна уеб услуга.
	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.	Този модул за обратна връзка на 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.	Този заявки ще бъдат обработени от конфигурираните събития.
	Add Event	Добавяне на събитие

Loading…

No matching activity found.

Browse all component changes

Glossary

English	Bulgarian
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.bg.po, string 658