Passing the list of assigned agents to a workflow rule

Rick Bakker rbakker at gmail.com
Thu Nov 17 05:05:30 EST 2011


Hello,

Okay, I think you're talking about the intersection about possible
agents and responsible agents here.

You say the agents can't be determined until runtime. Putting an
agent-determination step before the step in question *is* at runtime.

It's true, there is no generic container element for
agents-of-a-workitem, but usually there is a custom one, assigned in
the workflow before it is used in a workitem.

You have to create a step in your workflow which determines the agents.

Otherwise, I've misunderstood something along the way. Good luck!

regards
Rick Bakker
hanabi technology

On Thu, Nov 17, 2011 at 8:44 PM, Mintchev Alexander, Mag.
<Alexander.Mintchev at biac.at> wrote:
>
> Hello!
>
> 1.) A workflow step may contain a list of assigned agents that is determined at design time. All of these agents are allowed to perform the step.
> 2.) At run-time, however, a worklfow rule (in my case in the form of a functional module) can specify the exact agent to perform the step.
>
>
> Normally, there is not a (direct) relationship between (1) and (2). Whowever, if the agent determined in (2) does not belong to the set of agents in (1), the workflow remains without a responsoble agent at this step. It is then visible in the transaction swi2_adm1, but no agent recieves the workflow item in their workplace.
>
>
> The question is: How can a pass the list from (1) to (2)? Is is contained in a standard wf container variable, and if yes, what is it called?
>
>
> Thank you!
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: sap-wug-bounces at mit.edu im Auftrag von Rick Bakker
> Gesendet: Do 17.11.2011 10:15
> An: SAP Workflow Users' Group
> Betreff: Re: Passing the list of assigned agents to a workflow rule
>
> Hello,
>
> I'm not sure I understand your problem.
> No matter how your agents are determined, surely you can pass all the
> required information to a step preceding the workitem in question? If
> not, what is stopping you from doing that?
>
> regards
> Rick Bakker
> hanabi technology
>
> On Thu, Nov 17, 2011 at 8:06 PM, Mintchev Alexander, Mag.
> <Alexander.Mintchev at biac.at> wrote:
>>
>> Dear workflow colleagues!
>>
>> For a couple of worklfow steps, we defined a list of assigned agents that
>> are allowed to execute the step. The list contains all users having one of
>> the roles:
>>
>> ROLE1 or ROLE2 or ROLE3
>>
>> The workflow rule determining the responsbile agents for processing a
>> workflow step is repersented by a funcitonal module that does not take into
>> consideration the roles a given user is in and sometimes determines a user,
>> who does not have any of the roles above.
>>
>> Withing the rule (actually within the funcitonal module), I can easily check
>> whether the determined user is in a given role, but I could hardly determine
>> an alternative user, should the determined one does not have any of the
>> roles above.
>>
>> To solve the problem, I would like to pass to the workflow rule (and
>> ulitmatelay to the functional module) a list of all assigned agents. In the
>> functional module, I could pick up any of the users from the list, if the
>> determined user does not have any of the roles above.
>>
>> But: How can I do that, i.e. how can I pass the list of assigned agents to
>> the workflow rule?
>>
>> Thank you!
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>




More information about the SAP-WUG mailing list