Hi All, We are having many processes coming into our pipeline.
Some of these processes would be sharing same panels in several applications.Therefore, we are working with the concept of reusable processes - handling panels in systems. My question is how to design the Work Queues between Main Processes and the reusable processesHow do I pass data back and forth from reusable processes in a best practice way.Assumption is already each panel can be processed independent of each other or at least subprocess will take care of this. Another assumption is when a process is themed reusable it can or may be processed by standalone robots (scheduling) or simply be called by main process (through main process schedule). If it was just 10 cases from each we are talking about, then i would maybe just let the robot handle it, and maybe not create a sub queue. but potentially we got 100-500 cases going through some panels, while others is low volume. I in that scenario want to have dedicated robots processing those panels.
So to give an example:
System A is the same, and between two of the processes they will be using 2 of the same panels. The input case itself is completely unrelated.
Current IdeaCurrent idea is to have a main work queue for each of the processes. These processes then need to create sub work queue items into multiple sub work queues that is being processed by the System A - Panel A,B,C,D,E,F processes e.g.
We changed our Idea and now implementing in a different way.
We are cutting down on the amount of work queues and connecting the Sub processes to the business processes more closely. We are verifying the scalability of our new approach.