I assume that For Each will do the trick, but there is one problem: sometimes the submit button disappears, due to system error and I have to repeat the process. This is why I have added Element exist check, where if the robot doesn’t find the button it repeats the first steps.
I don’t how can I do that in For Each. If you have any suggestions or solutions IT WOULD BE GREAT (the deadline is ticking)
I would start off by saying For each can be used for Data table or collection.
Either use each file in folder xaml and build the workflow.
Or use list of file names and you can use for each item in array/list until the end
If I have misunderstood your question then please elaborate on how you want to approach the design. Do you really want to use for each or did you intend to ask something else.
I would suggest you to break the initial steps into smaller workflows so that it can be reused in the for each construct as the submit button has issues and reuse them/retry them inside the loop.
Well i am asking is there a possibility not to use for each in the workflow, or to use for each just to pass the next file from the folder into the workflow.
Are you suggesting to put the whole workflow in the For Each. There should be If statement for the existing of the submit button. Not sure how, just guessing.
When you create a REFramwork project, the documentation will be in Documentation folder and it’s up to date. I do not know if this git is still maintained.
Just like @c.ciprian mentioned RE Framework would also be helpful and you can consume Queues for looping through the data set that you have.
Or if you want your own custom retry mechanism then the only wrkflow that needs to be retried should be separated from the others so that it can be modular and code duplication does not happen.
The application that tries until the ‘submit’ appears must be the workflow which should be independent and invoke it using ‘Invoke workflow file’ and retry it with condition that until submit button/element exists or on element appear.