[Openflow-dev] activity.py

[<jm...@so...>]

Here I send the activity.py I am using actually (I finished it yesterday),
with all the modifications I have done from now: all I can do is that they
are usefull for me :-)

Vincenzo, what do you think about ??

Features:

Unified API for automatic and manual activities:

1) The application must have as minimum this parameters:
  token_id, activity_id , process_id, workflow_id
  In practice, all my python scrips have (token_id=3D'',
activity_id=3D'', process_id=3D'', workflow_id=3D'')

2) The parameters specified in the openflow activity are also sent to the
application, at the "same level" (not in an auxiliary object).

That is, if  your parameters field has: {'order_id':4}
The application must have this parameters at less:
(token_id=3D'', activity_id=3D'', process_id=3D'', workflow_id=3D'', order_=
id=3D'')
And order_id will be passed the value 4

3) The parameters are evaluated, so you can put
{'order_id':token.idorder} in the parameters field.
I think this is very usefull, because you can send specific properties
of the token the scripts, without having him to fetch them.


4) Compatible with DTML-Method and Python Scripts. DTML-Documents not
tested in automatic mode. The DTML are not given a REQUEST object in
automatic mode, which I think is more natural. Thay acquire the
variables from the parameters we sent them, and their parent.



--=20

      __o
    _ \<_
   (_)/(_)

Saludos de Juli=E1n
EA4ACL
-.-