| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| repeat an activity |
« View previous topic :: View next topic » |
| Author |
Message
|
| jhea |
 Posted: Tue Jan 28, 2003 6:47 am Post subject: repeat an activity |
 |
|
Novice
Joined: 18 Dec 2002
Posts: 19
Location: UK Hursley
|
Hi all,
According to the instructions in Buildtime v3.3 manual (page 19, Chapter 3 Subsection of creating a process diagram), one can have an activity that is repeated until the exit condition is met. However I coudn't get this happen. There is a Data Loop Connector connecting the output of the activity to the input of the activity. And I have set the exit to automatic, and the exit condtion is _Sate()=_Finished, therefore if the activity is finished (not ForceFinished, _Expired, etc.) it should have gotten restarted again. But that didn't happen. Any one has comments on this?
Many thanks,
Jenny |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Jan 28, 2003 7:38 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| Jenny wrote: |
| I have set the exit to automatic, and the exit condtion is _Sate()=_Finished, therefore if the activity is finished (not ForceFinished, _Expired, etc.) it should have gotten restarted again. But that didn't happen. Any one has comments on this? |
I believe the problem is that _State() is never going to be tested if you ForceFinish or Expire the activity. What you need to do is to have this activity in a Block, and then use a Transition condition going to an activity that will set a member in the Blocks sink to cause the block to repeat.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| yaakovd |
| Posted: Tue Jan 28, 2003 9:11 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
Hi Jenny
I agree with jmac that you definitely have problem with exit condition.
If you use expiration, you must add Data Default connector on your activity. Otherwise you will loose input data after first expiration and next repeat will finish abnormally.
I guess that you talk about same problem? And activity already in block?
Try to use other member as exit condition.
For example: create member condition in your regular Data Structure. Use default value 'init', your application will set it to 'finish'.
Set exit condition as: condition = 'finish' ot condition <> 'init'.
Make sure if your application is working  - first try finish simple activity without expiration, block etc.
Good luck.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| dkrawczynski |
| Posted: Wed Jan 29, 2003 6:39 pm Post subject: |
|
|
Apprentice
Joined: 19 Dec 2002
Posts: 26
Location: Dallas, TX
|
Jenny,
The problem with what you are trying to do is that the Workflow server ignores the activity's exit condition when activity is either Force Finished or it Expires. That's why you need to put the activity inside a block to get it to repeat.
Remember, the exit condition of the activity is specifically meant to keep workitem in the activity and not let it escape so that the activity will not need to be repeated because it was not completed correctly.
_________________
Doug Krawczynski
IBM Certified Solutions Expert -
MQSeries Workflow |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
