On 9 Nov 2004, at 14:54, Jeremy Boynes wrote:
[EMAIL PROTECTED] wrote:
On 8 Nov 2004, at 18:53, Jeremy Boynes wrote:
I think we may be in violent agreement here :-)
I think we should add some type of collective entity, I just
hesitate to call it a Group as that tends to be associated with a
speci
What about ResponsibleParty?
David
Jeremy Boynes wrote:
[EMAIL PROTECTED] wrote:
On 8 Nov 2004, at 18:53, Jeremy Boynes wrote:
I think we may be in violent agreement here :-)
I think we should add some type of collective entity, I just hesitate
to call it a Group as that tends to be associated wit
> -Original Message-
> From: Jeremy Boynes [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 08, 2004 1:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Agila] assigning tasks to groups of users
>
> [EMAIL PROTECTED] wrote:
> >
> > On 8 Nov 20
[EMAIL PROTECTED] wrote:
On 8 Nov 2004, at 18:53, Jeremy Boynes wrote:
I think we may be in violent agreement here :-)
I think we should add some type of collective entity, I just hesitate
to call it a Group as that tends to be associated with a specific
model ( a relatively static set of users a
On 8 Nov 2004, at 18:53, Jeremy Boynes wrote:
I think we may be in violent agreement here :-)
I think we should add some type of collective entity, I just hesitate
to call it a Group as that tends to be associated with a specific
model ( a relatively static set of users and other groups). Call it
[EMAIL PROTECTED] wrote:
On 8 Nov 2004, at 15:58, Jeremy Boynes wrote:
[EMAIL PROTECTED] wrote:
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could
On 8 Nov 2004, at 15:58, Jeremy Boynes wrote:
[EMAIL PROTECTED] wrote:
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could
perform - they then grab
[EMAIL PROTECTED] wrote:
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could perform
- they then grab one ('locking it') and then execute the task o
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could perform
- they then grab one ('locking it') and then execute the task or
releasing it back into
