Is there a way to use constants or expressions in a Decision Object? We'd like to use a decision object to select which process model to start next based on status and the current process. Ideally, we'd like to be able to use a constant to compare the input process model but that doesn't seem to be an option...unless I'm missing something obvious.
I know we can use an If or create multiple decisions....just not sure why we can't reference constants inside the decision.
Bryant
Discussion posts and replies are publicly visible
We have a workaround that will prevent us from "hard coding" process model ids...but it still seems like there should be an easier way.
You can create a list of constants for comparing decision inputs like this.
Thanks. That is basically what we are doing....I just wish we could reference process models or constants directly in the "Choice Values" or directly in the table.
OK. This looks like very generic process dispatching. Do you put that into a "Start Process" node? In my experience this makes debugging and issue analysis quite difficult. Are you sure you want to do that?
We do use this for process dispatching. We typically put it in a script task before the "Start Process" node to help with debugging. We've found this design pattern useful for quickly building out processes with many different re-routing requirements or complex rules for determining which path to take.
I understand. We just built an application where dynamic routing is based on a 3 parameters routing configuration maintained in a db table. We use a separated script task as well. Makes testing a real challenge.
We considered using a similar approach with a DB table...we may revisit that idea. I agree, testing is very easy when using proper process models with gateways to control flow logic. One advantage we've found with this approach is "integration testing" is simply testing decisions (logic) to launch the next process. We can test the entire flow without starting a single process. Consequently, testing each "sub-process" becomes like a unit test.