RE: [Openflow-dev] Deleting instances etc.

[Peter E. <P.E...@er...>]

Thanks for the response.

I have updated again but this made no difference (apart from Zope product 
changing OpenFlow to openflow-engine). I deleted my earlier OpenFlow object 
just to make sure, but the first problem still remains - I cannot delete 
process instances.

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

Two more queries re activity applications - I haven't found any difference 
between Automatic or Manual starts and finishes; and I haven't found out how to 
complete an activity from a WorkList. I guess the latter requires some sort of 
return button in the DTML? You can probably guess I am still a newbie with 
Zope.

Yours
Peter


-----Original Message-----
From:	Daniele Tarini [SMTP:d.t...@ic...]
Sent:	25 February 2002 10:47
To:	Peter Edwards; 'ope...@li...'
Subject:	Re: [Openflow-dev] Deleting instances etc.

On Friday 22 February 2002 16:28, Peter Edwards wrote:
> I now have OpenFlow 0.7 (or 0.7777777 ?) downloaded from
> http://www.openflow.it/wwwopenflow/EN/index_html

I apologize for this: I think the 0.7 is a wrong name for that version...

Mmh, I think we have OpenFlow in way too many places around. Here is a resume
of all the places you can find OpenFlow:

1) Sourgeforge: at http://sourceforge.net/projects/openflow
Here you can find the updated CVS developers use for their work. As soon as a
bug is fixed, a new functionality added and so on, this is the place that
gets modified first.

2) Zope: at http://www.zope.org/Members/vds
This place hosts some (out of date) documentation for OpenFlow as well as the
latest (hopefully) stable version.

3) OpenFlow: at www.openflow.it
This site is trying to keep up with development. Its main objectives are to
spread knowledge about OpenFlow: general and specific documentation, latest
version download. While in the future this will be the main reference for
OpenFlow, at the moment it is on experimental development.

We are working on keeping all the sites aligned to the latest version. In
case of ambiguity the sourceforge CVS will certainly have the latest version.

I just updated both OpenFlow and Zope site with the current version. I'll
update the latest sourceforge release as soon as possible (though the CVS is
obviously up to date!)

> Currently I have 4 problems :
>
> 1.
> I am unable to delete instances. In the 'Process instances' tab I select
> one or more of the instances and press 'Delete instance', and all that
> happens is the selected instances remain, unselected.

Can you try this again with a more recent version (either on www.openflow.it
or www.zope.org/Members/vds?

> 2.
> I tried creating an application from a DTML document, with URL
> http://localhost:8080/mywf/trialdtmldoc and empty brace parameters. The URL
> is correct as I can call it directly from the browser. I then created an
> activity to call this application (Manual start and finish, and empty brace
> parameters), and managed to get a 'Start application' action for it in a
> Work list. When I select the 'Start application', Zope fails, unable to
> locate the object at ...:8080/mywf/http%3A

Ok, this is easy: the url to be called should not be referred as
"http://localhost:8080/mywf/trialdtmldoc" but as "/mywf/trialdtmldoc"
or even just "trialdtmldoc" since the search starts from workflow level items
in the zope hirearchy anyway.

> 3.
> If I interrupt an OpenFlow session to browse (e.g. www.openflow.it) then
> return by the browser 'Back' button, I usually find I have lost the
> required permissions to continue, and can only retrieve the situations by
> closing and re-loading the browser. Of course I don't know if this is an
> OpenFlow problem, or Zope, or the browser (MS IE5).

Mmh, I'm not sure either. I'm sure OpenFlow product is currently not using
any session object (like Core Session Tracking) and that might cause some
session mess with browser's back button...

> 4.
> Please advise what is the format (or please give an example) for passing
> parameters to applications.

First of all: five parameters are always passed to the application:
openflow_id, process_id, activity_id, instance_id and workitem_id. With these
parameters you can call any workflow API on the workitem you selected
starting the application.

For additional parameters, the format is a python-like dictionary:
comma separated key-values pairs expressed like '<key>':<value>, all wrapped
in braces

Example 1:
You want to pass "int_one" parameter with value 1 (int) and "str_one"
parameter with value "one" (string):
You should write:
{'int_one': 1, 'str_one': 'one'}

You can pass items belonging to instance, activity, process and openflow,
like properties, python scripts results or other. As a rule of thumb you may
directly reference any attribute of an instance, activity, process or
openflow.

Example 2:
Suppose you want to pass a "myint" int property of your instance (that might
have been set by some other application with a manage_addProperty call) to
the application:
{'instance_myint': instance.myint}

You can specify parameters in two places: application definition and activity
definition. If parameter names collide, activity parameters override the
application ones (so that you can redefine an application parameter in the
activity calling that application). You can also see application parameters
as a default value for the parameters, and activity parameters as actual
value if they need to be different from default.

Clear enough?

Thanks for your contribution,
	Daniele =)