Queue messages for later processing

For example, one of your trading partners has a requirement that accompanying PRICATs collected by the day may only be delivered once per day in one message.

To collect messages for later processing you can proceed as follows:

1. Determine the recognition characteristic (e.g. subject or file name) of the messages to be queued.
2. Define a specific message basket and name it for example “OnHold”.
3. Extend the job that normally receives the messages with MessageSelector to move them to the message basket defined in 2. based on the recognition criteria defined in 1. Here the selection criteria are to be applied accordingly with the two MessageCollectors. The special thing about the delegator that receives the messages to be parked is that it does not immediately start the target job¹⁾, but moves the messages into the OnHold message basket.
   
4. Create another job that collects the messages stored in the “OnHold” with a MessageSelector and delegates them to the dispatch job. The dispatch job collects the unprocessed messages from OnHold that were delegated to this job and delegates them to the Standard Outbound job.
   
5. Automate the job created in point 4 according to the corresponding requirements, e.g. once a night.

I.e. that the messages, which generate the accompanying PRICATs, are filtered directly after the receipt in eBiss according to a criterion, are moved first into a separate message basket and are delegated at the same time to a specific job, which may not be started however immediately. The other job is now triggered by an automation at a certain time and collects all messages delegated to it from the message basket OnHold dun delegates these finally to the standard outbound job.