Run same process multiple times with different input parameters?

Help Orchestrator
, ,
1

As the title says, I have a process that takes in 2 string parameters. I would like to run this process multiple times (we only have one unattended robot) but with different parameters values? How do I achieve this without looping through an excel/csv file within my code? I looked into triggers and queues but it seems I can’t have more than 1 instance of the process in pending mode at any given time?

Thanks in advance!

2

Hi @Rohi2023

There are some approches here:

1 - if you are using ReFramework, you can add x number queue items in Init State passing the string you need like in Argument and capture this information in process and do your logic.

2 - Other one is create a new process in orchestrator choose the same package and set your arguments for this second one. This way, in Ochestrator perpective you have 2 differents processes using the same package, which one with own triggers, jobs etc. So pending state is not for the same process. You can create as many processes as you want for the same package

1 Like
3

@Rohi2023

Create different processes with different input arguments and create separate time based triggers for eqch so that the process runs with different values

Cheers

1 Like
4

Thank you both.

I have about 15 different input sets to run. Does this mean I need to create 15 different processes?
If this is the only way, I can create a subfolder and create 15 processes using same package but different inputs. How do I then run all 15 one by one (not in any order)? Do I need to schedule them or use triggers?

5

@Rohi2023

You can use time trigger and achedule them to run…they would run one after another

Cheers

1 Like
6

@Rohi2023

As mentioned by @Anil_G, you can achieve using trigger.

But one question here: with you having a lot of input (differents runs) maybe increase the effort to maintain this triggers and processes.

Is it possible to run one by one in the same job execution ? if it is, you can use the first approach that I mentioned in early reply. This way is more easy to maintain the project itself

1 Like
7

I have not really used the REFramework in it’s entirety but I have used the initSettings just to read config files from Assets, that’s about it. Also, I am not sure using the REFramework will work for various reasons:

  1. I will not know what the input values will be at the time of developing and publishing the test. These inputs are the result of a different process (API calls) outside orchestrator.
  2. More importantly, If one instance of the call fails, the entire process will fail. I don’t want this to happen. I want all the different instances (with inputs) to run independently of each other so if one fails, it won’t affect the execution of the next.
  3. This is just the same as me reading an excel sheet from a folder location and iterating through it, something I would like to avoid…

Perhaps the trigger is the best solution for me. If this becomes too cumbersome, I will re-visit the other solutions provided.

Thanks a lot, both of you!

1 Like
8

@Rohi2023

Thank you for the explanation.

I would like to mention if you are using ReFramework the execution at process level will run independently for each queue Item. If one fails, the Reframework will get the next one to process and you can retry the failed items etc

The architeture would be

1 - One Time Trigger
2 - At Init State > create x queue items, each one with one key-value that distinguish one item from another (like in in argument)
3 - Process State > Based in the key value, runs a specific branch in process

Anyway, good luck and if you have any doubt, please get in touch

Cheers

1 Like
9

Oh this sounds like something that will work for specific use case! I will need to read up more on this because I don’t know how this works. Is there a document I can read or video? Or perhaps a sample xml that can help me?
Thanks a lot, I really appreciate your help.

10

Sure

This video may help you

1 Like
11

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