sure it can proceed independently but in several different ways: multiple tasks in one node or a dynamic fork behave differently, so for a more specific answer, you need to be more clear what happens in the 'proceding'
Thanks for the quick response and I am sorry if my description is a little lacking.
Exactly what happens at each step is going to vary - our system will have to support a lot of different kinds of steps - but in general it is just adding additional information to the request.
The main issue is that the requests should be able to proceed through the workflow instance all together, in groups or individually depending on the operating procedures and available staff in place. So in simple terms of
500 requests are created at step A and move to B.
50 are processed (information added) at B and move to C
Some time later 10 of the 50 at C are processed and 100 at B are processed
This would continue (any number of requests getting processed at any step at any time) until all have been processed or they are canceled.
I hope this makes sense.
what is the relation between the requests? if there is none, just start multiple instances of the process. If they are related, look at the custom fork in the wiki.