Re: [Openflow-dev] Deleting instances etc.

[Daniele T. <d.t...@ic...>]

Hello Peter,

On Monday 25 February 2002 15:59, Peter Edwards wrote:
> I have updated again but this made no difference (apart from Zope produ=
ct
> changing OpenFlow to openflow-engine). I deleted my earlier OpenFlow ob=
ject
> just to make sure, but the first problem still remains - I cannot delet=
e
> process instances.

This is amazing =3D). Maybe I'm missing something: you created an instanc=
e,=20
then you selected it (clicking on the check-box next to it) and clicked o=
n=20
the "Delete instance" button, correct?

Can it be browser problem? Try creating and deleting an instance. What=20
happens if you restart your browser? Can you still see the instance?

Even more simple than that: qhat happens if you click on the instance you=
=20
thought you just deleted. Does it raise an error (so the instance is actu=
ally=20
deleted) or does it show you its history?

> Application URLs and parameters now understood. FYI I tried all the
> parameters you indicated, and found 'openflow_id' is missing.

If you choose a DTML as an activity application you can test which parame=
ters=20
are passed to your applications: just put a=20
<dtml-var REQUEST>
in the dtml code and it will show you all parameters from openflow.

Do you still see no "openflow_id" parameter?

> Two more queries re activity applications - I haven't found any differe=
nce
> between Automatic or Manual starts and finishes;=20

Ok, here is the difference:

Auto/manual start:
In automatic start mode the activity will run its application as soon as =
an=20
instance workitem reaches it. There will be no worklist for users: it wil=
l be=20
openflow itself taking care of starting the activity application on the=20
workitem.
In manual start mode openflow will wait for user intervention to start th=
e=20
activity application: usually this is done through the call fo the=20
"callApplication" API of workflow. This API should be called by the workl=
ist=20
the user is using (like the default worklist in openflow does).

Auto/manual finish:
In automatic finish mode as soon as a "completeWorkitem" API is called=20
(supposedly by the activity application upon ending its work) the instanc=
e=20
will be automatically forwarded to the next activity.
In manual finish mode this will not be done and user (again, the activity=
=20
application upon user input) will have to call the "forwardWorkitem" API.=
=20
This enables the user to choose a given path (transition) for the instanc=
e to=20
follow. So mainly this mode is reserved for manually steering the instanc=
e in=20
alternative paths of the process. (Remeber that you can automatically ste=
er=20
the instance giving condition to transitions).

> and I haven't found out
> how to complete an activity from a WorkList. I guess the latter require=
s
> some sort of return button in the DTML?=20

The application should take care of this by calling the "completeWorkitem=
"=20
API, as above.=20

Via DTML you might write:
<dtml-call "_['openflow_id'].completeWorkitem(instance_id, workitem_id)">
or via a python script you might write:
getattr(context, openflow_id).completeWorkitem(instance_id, workitem_id)

> You can probably guess I am still a
> newbie with Zope.

We all have been at least once =3D)

Thanks for the contribution
=09Daniele