Managing jobs with multiple results in Orchestration Process

Hey guys,

I am trying to build a robot using an Orchestration Process for the following case:

I want to start job 1 that reads an xml-file and tries to match a description with clientnumbers. At this moment, there are two outcomes: it matches and it goes on to job 2, or it goes to a list (in Excel) and it needs further examination by a colleague.

We want to create tasks for the last outcome, so the colleagues don’t have to work in an Excel-sheet. They can add the clientnumber to the task in Action Centre and submit it so it goes on to job 2.

We want to keep the jobs seperated so we can also run them without the Orchestration Process.

What is the best way to create the tasks in this instance? We thought about having two queues: one for outcome 1 and one for outcome 2. We read the queue items for outcome 2, make a task for each one and when it is submitted we add it to the same queue as for outcome 1 - as the cliëntnumber is now known.

Can you assist us? I hope the problem is clear. Thanks in advance.

Hello @Jelmer!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly