ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » _State()

Post new topic  Reply to topic
 _State() « View previous topic :: View next topic » 
Author Message
stubie
PostPosted: Thu Aug 07, 2003 2:28 pm    Post subject: _State() Reply with quote

Novice

Joined: 05 Nov 2001
Posts: 14
Location: Charlotte, NC

Has anybody worked with _State() in transition conditions? I have a model that has a connector with _State() = _Skipped, and the connector evaluates false, even though the source activity has a status (as shown in the monitor) of "Skipped".

Have I coded this wrong?
Back to top
View user's profile Send private message
Ratan
PostPosted: Thu Aug 07, 2003 2:41 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

You cant use _state() = _Skipped. Activity goes into this state when it is skipped as a result of transition condition. The connectors out of such activities are always false.
_________________
-Ratan
Back to top
View user's profile Send private message Send e-mail
stubie
PostPosted: Thu Aug 07, 2003 4:37 pm    Post subject: Thanks Reply with quote

Novice

Joined: 05 Nov 2001
Posts: 14
Location: Charlotte, NC

Thanks for the info. Anyone have any idea why the product designers included this, since it appears to have no use?

What are the valid condition checks? _Expired and _ForceFinished? (_Finish seems just as worthless as _Skipped if _Skipped always evaluates false).

Finally, is there any documentation on how this works? I'd like to see an example of the use of _State( string ).
Back to top
View user's profile Send private message
jmac
PostPosted: Thu Aug 07, 2003 6:51 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Stuart:

It makes no sense logically to have the _Skipped testing the source activity of the control connector, since as Ratan points out the connector would be forced to false due to "Dead Path Elimination".

Why the developers put it there is a good question, but maybe this is the answer. The following is a quote from the DesignIssues unit of my basic material:

Quote:
If an activity does expire you can test it's state with a transition condition like the following

_State(<activity name>) = _Expired

where activity name is the name of the activity whose state is to be tested, it may be omitted to indicate the current activity. Any activity whose state is tested, must be in the control path


Now of course, I don't remember where or how I got this information, but maybe the _Skipped makes sense when used in this format. You could be testing if some Previous activity, that was not Dead path eliminated had been skipped

Hope this helps....

Regards
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » _State()
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.