Re: [Openflow-dev] History doesn't pass to 'complete'

[Vincenzo Di S. <e.d...@ic...>]

The status diagram (except for special status like BLOCKED and FALLOUT) i=
s:

NEW -> ASSIGNED -> ACTIVE -> COMPLETE


For the moment, when a user fetch the token, the token get the ASSIGNED=20
status and is assigned to the workflow user, when the user start to work=20
on the token you have to change the status in ACTIVE. May be the=20
assignment of the token and the user`s work beginning have different=20
time. The difference between ASSIGNED and ACTIVE will be clear when the=20
"push"  assignment mode will be implemented. With this assignment mode=20
the users will not choose what to do but someone will assign them the=20
tokens on the activities. So if a workflow user fetch a token but has=20
lot of work and doesn`t begin to work on it, the administrator can=20
reassign the token to another user.
Hope I`ve been clear..let me know...:)


Juli=E1n Mu=F1oz Dom=EDnguez wrote:

> I still have the same problem from Assigned to Complete
>=20
> Even if I do this:
>=20
>      token.changeStatus('Begin', 'complete')
>      token.move('Begin', None)
>      token.changeStatus('enterdatas','assigned')
>=20
>=20
> Begin keeps on beeing 'assigned' (blue)
>=20
> Must I go to active ?
>=20
> What is the difference between active and assigned ?
>=20
>=20
>=20


--=20
Vincenzo Di Somma - Responsabile Ricerca e Sviluppo - Icube S.r.l.
Sede:   Via Ridolfi 15 - 56124 Pisa (PI), Italia
E-mail: e.d...@ic...              WWW: www.icube.it
Tel:    (+39) 050 97 02 07              Fax: (+39) 050 31 36 588