On 9/18/07, Juan Pedro Paredes <[EMAIL PROTECTED]> wrote:
>
> Hi all,
>
> Imagine we have lots of processes
> When we go to eadmin to see, whats going on,
> we use the feid as id for requests to pause/cancel/resume controllers.
> But if we want o pause a process and edit it directly(as store
> controller do)
> the id that the controller needs is the id of the activerecord.
> In eadmin context is not clean request to edit controller with the
> feid.
> What we will do? use the feid, AR id or both?

Hi Juan Pedro,

you are mentioning two kind of objects at least : process instances
and workitems. Process instance have a unique "workflow instance id"
(wfdi). Workitems have both a "flow expression id" (fei) and an
ActiveRecord id.

There is a third object (resource) which is the expression (an atomic
piece of process instance). Workitems have a fei because they travel
throughout the process instance, thus throughout the process
expressions. When a workitem is emitted outside of the process engine,
it bears the "flow expression id" (fei) of the last expressions (most
certainly a ParticipantExpression instance that emitted it).

In the case of the "engine admin" (eadmin), there are no workitems
involved, only process instances, thus only workflow instance ids are
useful.

AR workitem ids are only relevant when addressing stores (and the
workitems they contain). There is no "workitem id inconsistence" in
Densha, because there is no connection between workitem  (AR) ids and
workflow instance ids and flow expression ids.


Hope this helps, best regards,

-- 
John Mettraux   -///-   http://jmettraux.openwfe.org

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"OpenWFEru dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/openwferu-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to