Is it recommendable to still work with ADD and GET processes?

Good day to everyone.

I have been working with UiPath for the past 2-3 years and in the company I used to work at, for every robot we would make, we would create two processes for it, an ADD process and a GET process:

  • ADD process - would be used exclusively to add the transaction items to the queue.

  • GET process - would be used exclusively to process every item from the queue.

From what I got told, this way of working followed UiPath best practices and I have always thought that it was the best way to work with every robot.

I recently have changed companies and I’m trying to create an improved work methodology in my new company and in order to do that, I have been checking UiPath documentation and courses to check whether or not I have been working following the UiPath best practices (current or past) or if this way of working is way off.

From what I see and have experienced, using ADD and GET robots have its pros and cons and so far I have really liked working with this system but I am always open to work with better and improved methods.

Thank you all, I wait for your answers and I hope we can have a nice debate about this.

Welcome to the forum.

For the starting discussions lets clear some wordings:

ADD Process - so called Dispatcher
GET Process - so called Performer

@ppr Thank you for the welcoming!

Thanks for the feedback. I didn’t know you could call them Dispatcher and Performer, it may be a language issue because I don’t usually work in English and specially don’t talk about UiPath in English.
Can I edit the post so it’s clearer for everyone?

no problem. we have cleared the terms just go ahead with the preferred wording

Thank you.

My question still stands, is it recommendable to work with ADD/Dispatcher and GET/Performer as two different processes?
From most the ReFramework templates I have been researching, both official and non official, it appears that both actions are done in the same process.

it depends on some project specific factors. Also both approaches can have pros & cons. As the templates can be customized, so it can be adapted.

We do like it separated as:

  • clear distinction between both concerns
  • no ADDings, when ReGettings

As mentioned above:
it depends on some project specific factors. Also it plays a role if more team members with different skills and expectations are to target

Thank you so much Peter.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.