Dispatcher and the Resource

[simulationUXC42]

How can we ensure that both the Dispatcher and the Resource have the same task queue arrangement and communicate effectively? For instance, if the Dispatcher passes tasks using 'Round Robin if Available,' how can we make the Resource operate in the same way?

[kavika_faleumu · Accepted solution]

Hey @simulationUXC42, I don't think you want to mix the use of dispatcher and resource, but it also depends on what you're trying to do. Do you mind sending a model showing what you're trying to do?

The Dispatcher object is used to control a group of task executers. The Resource is a bit more generic, in that it simply represents an asset with limited supply. If you are using a Dispatcher to give operators tasks and you're using a Resource to acquire operators and give them tasks, the logic in the objects may be competing with each other.

One thought is to have your Resource reference a group of operators (instead of the Dispatcher) and have your Acquire Resource activity use a Query to check if the operators have a task assigned already.

Hope this helps.

[simulationUXC42]

Thank you very much for your detailed response and clarification. I completely agree with your perspective that using both the Dispatcher and Resource together may lead to overlapping or conflicting logic.

My earlier question was simply out of curiosity, as I wanted to gain a clearer understanding of the concept. I truly appreciate the time you took to explain this thoroughly and provide valuable insights.

Best regards

[simulationUXC42]

@kavika_faleumu  If it is convenient for you, may I kindly ask if you could provide a small example model illustrating your suggested approach? It would greatly help me to better visualize and understand the concept.

[kavika_faleumu]

@simulationUXC42, attached is a model that shows the difference between using a Dispatcher and using Resources in a Process Flow.

Dispatcher Method

Key things to note about the dispatching model:

• You can center connect (S-connect) objects to the Dispatcher to create a reference. Many transport tasks default to using 

  current.centerObjects[1]​;

• The Dispatcher will out connect (A-connect) from the Dispatcher to Operators. This lets the dispatcher delegate tasks it receives to its output connections.

Process Flow Method

Key things to note about using Process Flow:

• Process Flow is great for laying out and controlling aspects of the model. It's a powerful tool, so I suggest you become familiar with it.
  • You can check out some of the Process Flow tutorials we have.
• You'll notice that there are drastically less connections. That's because most of the logic is controlled with pointer labels on tokens.
• You can reuse blocks of activities and logic using Sub Flows. Very useful for not repeating yourself.

I hope this helps!