How about simply adding an XOR split node after the second node that
checks the value of the parameter? Or adding a ruleset node there and
they use rules to create this human task if necessary?
A more advanced way to model this would be to use dynamic or ad-hoc
processes. At this point you could easily have a rule that describes in
which situation a task should be created (which is already possible now)
but it will also allow you to wait for the completion of these
dynamically created tasks. But we are currently still working on this
type of processes, so it's still in experimental phase.
Kris
Quoting ramram8 <ramram858(a)gmail.com>:
Hi All,
I have a question about rule flow and web console:
- Can we create a Rule Flow scenario in which the User tasks in it
is
dynamic. I created a Rule Flow using Fluent Api but what will
happen is
that in this case I wont have a single Rule Flow scenario with
dynamic
number of user tasks I ended up by having multiple scenarios. I used
also
the ForEach loop but what happened is that the user tasks are all
created at
the same level.
what i am looking to is to have according to certain parameter of
(2) for
example
start > task 1 > task 2 > end
if the parameter value is (3) then I will have
start > task 1 > task 2 > task 3 > end
Can this be achieved in Rule Flow ???
And if it Cant?? is there any Alternative ???
--
View this message in context:
http://old.nabble.com/Question-on-Rule-Flow-and-Web-Console-tp26508838p26...
Sent from the drools - user mailing list archive at
Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
Disclaimer:
http://www.kuleuven.be/cwis/email_disclaimer.htm