Re: Assign workflow steps to groups/roles

> Yeah, unfortunately there's no way around looping through all the
> steps, the problem with adding more columns to step tables is there
> where do you stop? There's always someone who needs just one more
> column to query/sort/restrict by.
>
I know, but don't you prefer to assign a step not just to a user,  but to a
role. (e.g. support, sales clerk, accounting, product manager XYZ ...) this
can be handled quite well in the current implementation if there's just one
user in those roles (by calling a function that returns the user, which
currently has this role).
but in the case where you have more than one member in this group (e.g.
support: an email is received on [email protected]; new workflow is created,
assigned to "support" group/role, now everyone from this group can see this
email in his in-box and the first who takes it will have it assigned to him.
I think, there's no simple solution to that, even if you add an additional
field to the tables you'd still have to make lot of queries to find all
steps.
i think, I'll probably use your caching approach, and I'll try to limit the
number of steps with a "null" owner. (e.g. by setting the user directly, if
role has only one member and assigning the steps to users as soon as
possible)

> I do use the EJB provider yeah, but it also has its limits (eg, no
> query support).
>
how do you build a "to-do list" for the workflow user without queries?

philipp



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf