Agent assignment situation

[Rick Bakker]

Hello,

I would use a container element Current_Agents for the agent and not
use a default rule.
Fill Current_Agents in a step or steps before the user decision.

If a different container element, say Actual_Agent, is empty then have
a step (which calls a task which calls a method that calls fm
RH_GET_ACTORS which calls the rule) to fill Current_Agents, otherwise
assign Actual_Agent to Current_agent.

Actual_Agent is filled with the actual agent of the user decision step.

regards
Rick Bakker / hanabi technology

On Wed, Oct 24, 2012 at 9:43 PM, Robert van den Berg <wug at bergtop-ict.nl> wrote:
> Hi all,
>
>
>
> I have a situation where I have a step (user descision) in the workflow
> which goes to a group of people via a rule.
>
> Person A takes the task, chooses an option and the next step goes to a
> different department. When this task is done, the workflow returns to the
> user descision but I want this task only to be delivered at person A, not to
> the whole group.
>
>
>
> I tried to do this using the default rule on the task and on the step, using
> a container element for the agent. So at first, the containerelement is
> empty and I assumed that then the default rule would be used.
>
> But now I see that the workflow runs in error because the agent could not be
> determined.
>
>
>
> How can I create this requirement?
>
>
>
> Kind regards,
>
> Robert
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>