8:21 p.m.
Sasi R [http://community.jboss.org/people/sasir] created the discussion
"Jump to end state from Node"
To view the discussion, visit: http://community.jboss.org/message/605516#605516
--------------------------------------------------------------
We have the below work flow
start state->node1->node2->node3->node4->end state
We are trying to jump from node2 to end state directly but still node3 and node 4 are
getting executed by executuioj context. We tried setNode and other stuff but its not
working as expected
EndState endState =
(EndState)executionContext.getNode().getProcessDefinition().getNode("end-state");
executionContext.getToken().setNode(endState);
Can you please advise on how this can be done?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605516#605516]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:20 a.m.
New subject: [jBPM Development] - Re: Jump to end state from Node
Martin Weiler [http://community.jboss.org/people/mputz] created the discussion
"Re: Jump to end state from Node"
To view the discussion, visit: http://community.jboss.org/message/605784#605784
--------------------------------------------------------------
Using token.setNode(..) should work, what exactly did not work 'as expected'?
I would, however, not recommend to use it because of the following two caveats:
* the process execution logging becomes inconsistent, which might be relevant if audit
data of the executed process instances needs to be captured
* it is not visually clear just from looking at the process that the process execution can
'jump' at certain points.
A different approach for your requirement would be to introduce super-states. This concept
is basically just a group over several nodes, but with the added benefit that you can add
additional outgoing transitions from the super-state. These can be called from any node
inside the super-state.
1. FastForward w/o super-state:
start -> node1 -> node2 -> node3 -> node4 -> end
With this process definition, if you want to move from node1 directly to node4, you could
only use Token.setNode() with the above mentioned caveats.
2. FastForward w/ super-state:
___super-state1___
| |
start -> | node1 -> node2 ->| node3
|__________________| |
| v
`---------> node4 -> end
Here, you can just call the leaving transition of the super-state to node4 from any of the
nodes within the super-states. This has the advantage that the logs are created properly,
thus it does not break auditing, and that additional events are triggered, which could be
used to set/re-set any data or variables.
HTH,
Martin
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605784#605784]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:37 p.m.
New subject: [jBPM Development] - Re: Jump to end state from Node
Sasi R [http://community.jboss.org/people/sasir] created the discussion
"Re: Jump to end state from Node"
To view the discussion, visit: http://community.jboss.org/message/605904#605904
--------------------------------------------------------------
Martin,
Thanks a lot for replying in detail
We have below process definition which has Node-Enter action as shown below. As soon as we
start the process it will go to Node1 and from there we want to control the execution
(Jump to End state by avoid execution of Node2/Node3. However in some scenarios we want to
Jump to Node3)
But following code is not working as expected and its always executing all the nodes.
public class AutomationHandler implements ActionHandler {
*public* *void* execute(ExecutionContext executionContext) *throws* Exception
{
System.+out+.println(*new* Date()+"Inside
AutomationHandler::execute()");
System.+out+.println("########Going to End
State###########");
EndState endState =
(EndState)executionContext.getNode().getProcessDefinition().getNode("end-state");
Token token = executionContext.getToken();
token.setNode(endState);
//token.signal("trans4");
//token.end();
System.+out+.println(*new* Date()+"Inside AutomationHandler::execute()");
}
}
Process definition xml
********************************
<?xml version="1.0" encoding="UTF-8"?>
<process-definition xmlns="urn:jbpm.org:jpdl-3.2"
name="automationtest">
<description>
automationtest
</description>
<start-state name="start-state">
<transition to="node1" name="trans1"></transition>
<event type="process-start">
<script name="Allocation Event Started">
System.out.println("Event Creation Started "+node);
</script>
</event>
</start-state>
<node name="node1">
<event type="node-enter">
<action
class="com.citi.automation.build.jbpm.handler.AutomationHandler">
<unixCommand>
echo "Hello World"
</unixCommand>
<expectedRetunCodes>
A,B,C
</expectedRetunCodes>
<successCondition>
ExecuteCommand2
</successCondition>
<errorCondition>
End
</errorCondition>
</action>
</event>
<transition to="node2" name="trans2"></transition>
<transition to="end-state" name="trans4"></transition>
</node>
<node name="node2">
<event type="node-enter">
<action
class="com.citi.automation.build.jbpm.handler.AutomationHandler">
<unixCommand>
echo "sleeping"; sleep 60
</unixCommand>
<expectedRetunCodes>
A,D,E
</expectedRetunCodes>
<successCondition>
ExecuteCommand3
</successCondition>
<errorCondition>
End
</errorCondition>
</action>
</event>
<transition to="node3" name="trans3"></transition>
</node>
<node name="node3">
<event type="node-enter">
<action
class="com.citi.automation.build.jbpm.handler.AutomationHandler">
<unixCommand>
echo "Working"
</unixCommand>
<successCondition>
ExecuteCommand4
</successCondition>
<expectedRetunCodes>
A,B,C
</expectedRetunCodes>
<errorCondition>
End
</errorCondition>
</action>
</event>
<transition to="end-state" name="trans4"></transition>
</node>
<end-state name="end-state">
<event type="process-end">
<script name="Event End">
System.out.println("Event End "+node);
</script>
</event>
</end-state>
</process-definition>
********************************
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605904#605904]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:05 a.m.
New subject: [jBPM Development] - Re: Jump to end state from Node
Sasi R [http://community.jboss.org/people/sasir] created the discussion
"Re: Jump to end state from Node"
To view the discussion, visit: http://community.jboss.org/message/605939#605939
--------------------------------------------------------------
We figured out the issue. SetNode didnt work because we were using events on node action
and it was mentioned in the documentation that it wasnt supposed to be that way
ANyway, Thanks Martin for your guidance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/605939#605939]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:01 p.m.
New subject: [jBPM Development] - Re: Jump to end state from Node
Sasi R [http://community.jboss.org/people/sasir] created the discussion
"Re: Jump to end state from Node"
To view the discussion, visit: http://community.jboss.org/message/606054#606054
--------------------------------------------------------------
SetNode does not work, it always starts node after the one you set. Below is the correct
code
Transition leavingTransition = *new* Transition(+DYNAMIC_TRANSITION+);
leavingTransition.setTo(executionContext.getProcessDefinition().getNode("Nodename"));
leavingTransition.setFrom(executionContext.getNode());
executionContext.leaveNode(leavingTransition);
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/606054#606054]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4:56 p.m.
New subject: [jBPM Development] - Re: Jump to end state from Node
Martin Weiler [http://community.jboss.org/people/mputz] created the discussion
"Re: Jump to end state from Node"
To view the discussion, visit: http://community.jboss.org/message/606068#606068
--------------------------------------------------------------
But following code is not working as expected and its always
executing all the nodes.
The code should work, but the problem is that the process definition is composed of
<node> elements. As these are not wait states, the process execution just continues,
regardless of the ActionHandler. Change all the <node> elements in your process to
<state> elements, and you should get the desired result with the AutomationHandler.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/606068#606068]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4727
days inactive
4730
days old
jboss-dev-forums@lists.jboss.org
5 comments
2 participants
participants (2)
-
Martin Weiler -
Sasi R