-
1. Re: Waiting for external input
dslevine Nov 27, 2006 10:49 PM (in response to romeufigueira)You would not need to send any input to a node, but rather you would need to send the input to a specific process instance which is waiting for that input on a node. So the external system needs to know the id or the instance that is waiting. (Or any qualifier that would find one or more processes, i.e. any process where Company Name = 'Dutch Beer Co'.)
If you were going to send a message out to the external system informing it that your workflow is ready for some input, you could pass some kind of instance ID in the message and have the external system send it back with their input. Your processing logic then becomes something like
1. parse id
2. get instance
3. parse input
4. signal instance with input -
2. Re: Waiting for external input
kukeltje Nov 28, 2006 3:22 AM (in response to romeufigueira)partly correct, and by magic, dutch beer makes it to the stage again :-)
If there are multiple tokens, it could be that you need to signal a specific token and not the process in general. In that case you do need to eventually refer to a token ID, either directly, or by e.g. passing a node name and looking up the token or whatever. -
3. Re: Waiting for external input
thuat Nov 28, 2006 7:46 AM (in response to romeufigueira)how my project run?
-
4. Re: Waiting for external input
kukeltje Nov 28, 2006 10:59 AM (in response to romeufigueira)please do not threadjack
-
5. Re: Waiting for external input
romeufigueira Nov 29, 2006 6:48 AM (in response to romeufigueira)@dslevine and kukeltje
Thank you for your input, a working solution is being fabricated ;)