Hey @Joey_Sawyers,
Instead of putting all the 100 activities in a single sequence you can create 10 sequence of 10 activities. Let me explain you how:- Let suppose there is a process in which you have to login into a website, download some file from there and logout, so if I will perform all the task in a single activity it’s not easier to handle the code, to prevent the code from that issue what we can do is:-
- You create a sequence that will get the url and credential either from the orchestrator or from the configuration file with the out arguments.
- You create the login sequence with in arguments and put all the activities required for login in that sequence.
- You can create the file download sequence.
- You can create the logout sequence5.
- You can invoke all the sequence in one xaml sequentially.
Have a look on
Thanks,
Sanjit