====== DelegateQueued ======

With the help of the DelegateQueued Jobs you can set up different queues within your eBiss system and thus process jobs piece by piece. \\
Systems with many messages can profit from the resulting load distribution, provided that your job structure whitens at the appropriate places on the DelegateQueued.

An example of this could be that you have created several jobs that write to a database. This can potentially cause the database to block tables for writing and another process to wait for. It may be slower to have many processes write to the database simultaneously than to queue them using the DelegateQueued job and process pieces of white.


~~ GENERATED src="eBiss.ClassLib.Resources.JobSteps.DelegateQueued" changed="" ~~
^Properties^^
^Name^Description^
|**Type**|Class name of the jobstep|
|**Name**|Name for the jobstep that will appears in the job designer|
|**Description**|Optional description for the jobstep|
|**Queue Name**|Load balancing is only performed within the queue of the same name. This allows the system to be divided into different queue areas. Otherwise leave default: "DefaultQueue".|
|**Maximum entries**|The highest possible number of concurrent processes that can be processed in the queue (1 - 199).  CAUTION: If you use 2 different jobs with 2 different delegates to access the same queue, but have different Max entries, the behavior may be somewhat difficult to understand, because then a different maximum load limit applies for the respective delegate before something actually enters the queue.\\\\If in doubt, set it to the same value, then the behavior becomes more transparent.\\\\|
|**Timeout**|Specifies how many minutes to wait for the queue to clear. Default = 30 (minutes).\\\\After this time the waiting is aborted and a task is created.\\In this case, messages may have to be executed again manually.|
|**Target job**|The job to start|
|**Start job immediately**|Specifies whether the job is to be started immediately (Yes) or only assigned (No). 'No' makes sense if the message job execution are to be bundled and/or should be done at a later point in time.|
|**Use output messages**|If selected, then the created messages are forwarded, otherwise the messages passed to the job are forwarded.|
|**Move Message to**|The message basket into which the messages are to be moved. If not stored, the message remains in the previous message basket.|
|**Start job if**|This can be used to specify that the job is also started if no message is to be passed.|
|**State %%<=%%**|Only messages with a status less than or equal to the selected status are forwarded.|
|**Task state %%<=%%**|Only messages whose error status is less than or equal to the specified error status.|
|**Switch message direction**|This is a special setting to be used with caution. The direction is changed for all delegated messages.|