This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Split Processing Vs Generating Condition

Is there any consensus on when to use split processing with a script that throws an exception thereby branching a process chain or using generating conditions? I thought split processing may be better because in cases where some condition means 3 or 4 process steps should execute, instead of calculating the condition 3 or 4 times in each of the steps generating conditions, you could calculate it once in a script and then have 4 process steps execute on the success path and to continue on with whatever else not running the 4 if the condition isn't meant. So you're only processing the generating condition once.

 

However, I've made a process with split processing that has groups of 4 steps, the first step in each set is split processing and running a script. If the script is successful the 4 steps run and then the success event at the bottom of these 4 steps links to the first step of the next step. If the first step fails the orange failure link also goes to the next group of 4. I ran this though and looked in JobQueueInfo and the process has a huge number of steps. It looks like it loads every step in every possible condition of split processing then executes them as needed. So not sure how this may effect the used resources.

 

What do you think?

Parents
  • Thanks Markus. I didn't mention I'm using 7.1. I couldn't see anywhere in the documentation about passing values from one process step to the next (apart from out parameters from a script component but that's something else). I did try adding a value to the Values object array and accessing from the next step and I recall this not working. I came to the conclusion that each process step has it's own Values array. I don't have a problem writing to Values and reading from it from within the same process step. It sounds like my testing is mistaken?
Reply
  • Thanks Markus. I didn't mention I'm using 7.1. I couldn't see anywhere in the documentation about passing values from one process step to the next (apart from out parameters from a script component but that's something else). I did try adding a value to the Values object array and accessing from the next step and I recall this not working. I came to the conclusion that each process step has it's own Values array. I don't have a problem writing to Values and reading from it from within the same process step. It sounds like my testing is mistaken?
Children
No Data