To enable data sending, please register your system with OTRS Group or update your system registration information (make sure to activate the 'send support data' option.)

Some account problems

No account problems

No account activity

This CustomerID is invalid.

Select the customer user:customer relations.

Debugger

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, ...

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.

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.

Invoker backend

This rule will apply for all keys with no mapping rule.

This rule will apply for all values with no mapping rule.

The name is typically used to call up this web service operation from a remote system.

The password for the privileged user.

URI of a proxy server to be used (if needed).

The user name to be used to access the proxy server.

The full path of the certification authority directory where the CA certificates are stored in the file system.

The controller that the invoker should send requests to. Variables marked by a ':' will get replaced by the data value and passed along with the request. (e.g. /Ticket/:TicketID?UserLogin=:UserLogin&Password=:Password).