Yes that’s what I was thinking, but I didn’t understand why the parameter of Task1 is a List of Data.
My deduction is : Two example, I need to perform 2 separate task in my robot, two way to do it.
In the first case I want to perform Task 1 for every item and after this, I want to perform Task 2 for every item.
In the second case, I want to perform straight Task 1 and Task 2 for every transaction.
GetData.xaml -> Use this part to dispatch data in queues or get data from external sources like Website, API… Enable GetData.xaml during first run only !
If I have something to process, I will create a simple transaction, without data inside, just to process my tasks.
Process.xaml -> In my flowchart I will Invoke Task1 and Task2.
Task1 -> Use GetSetTransactionData to get data from my Queue previously filled and Process every transaction.
Task2 -> Idem.
After this, I will have no more transaction in my Main, so my execution will be over there.
GetData.xaml -> Still use this part to dispatch data in queues or get data from external sources like Website, API… Enable GetData.xaml during first run only.
Main/GetSetTransactionData -> A difference here. After dispatching or getting my TransactionData, I will get every single TransactionItem (From Queue, splitting Excel…)
And I will put this TransactionItem as Argument in my Task1 and Task2 in Process.xaml.
This required to change the datatype of the default Argument of Task1/Task2 (Which is TransactionData and not TransactionItem) in order to process it correctly.
This is just a thought, I’m not sure I’m right ! But if someone can give us an advice or correct me if I’m wrong, it will be helpful !