John, I think we are going to switch our default token from sid to: engineid + expid + wfid + participant.
Since we are not linking the user to the workitem (sid) but rather the workitem represented by the expression id (expid) the other problems disappeared. It also gives a good model going forward so that multiple participants can see the "status" of something, regardless of necessity to "act" on something at a specific time. We may need to tweek the token a little more to support concurrent_iterator, since it seems like the expid is set when the process evaluates rather than launch time. Thanks for the help. Eric Smith On Jun 16, 10:10 am, John Mettraux <[email protected]> wrote: > On Thu, Jun 16, 2011 at 08:01:39AM -0700, eric smith wrote: > > > How unique is wfid? > > Hello Eric, > > it's unique so that other process instances emitted by the same engine > (workers + storage system) won't bear it. > > Workitems are identified by "fei" (flow expression id), it's the combination > > (wfid, expid, engine_id, subid) > > You can obtain a unique string id per workitem by doing > > workitem.fei.sid > > Using particpant name + wfid is too vague, as you've noticed > > concurrence do > alpha > alpha > end > > and you'll be in trouble. > > Best regards, > > -- > John Mettraux -http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
