Dynamic or Ah-Hoc node ---------------------- Key: JBRULES-2120 URL: https://jira.jboss.org/jira/browse/JBRULES-2120 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (flow), drools-core (flow), drools-eclipse (flow) Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: FUTURE An ad-hoc or dynamic node acts as a node container where not all nodes are cleanly connected to each other but they are modeled as separate fragments that are not necessarily linked to each other. By default, all nodes that do not have an incoming connection would be triggered when the dynamic node is triggered, and the node will wait until all node instances have been completed before continuing. Different strategies could also allow: - (rule or code) constriants that define when certain fragments should be activated - the user can add additional node instances at runtime, even though they are not modeled as part of the process, and the node will wait until they are completed as well -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira