workflow

Former Member — Fri, 16 May 2008 05:14:58 GMT

hi ,

guys

who will assign the agents

Re: workflow

Former Member — Fri, 16 May 2008 05:52:27 GMT

Hi,

Workflow developer can assign the agents.

There are 5 roles.

1.Process consultant

2.Workflow developer

3.Workflow system administrator

4.Process controller

5.Agents

Give me your id, I will send one document which give you full idea regarding workflow.

Reward,if useful.

Thanks,

Chandu

Re: workflow

Former Member — Fri, 16 May 2008 05:56:49 GMT

Hi,

1. Possible agents are static and set up at definition time for the task, and are all people that are allowed to receive it in theory.

Example: Accounts dept org unit, or a security role for accounting.

2. Responsible agents (I prefer 'selected agents') can be dynamic and are evaluated at runtime according to the agent info you put against the step in the workflow builder. If you leave it blank it will determine all possible agents as responsibles.

Example: G/L accounts manager position, or a responsibility for company code.

3. Excluded agents are the guys you put under the excluded agents bit in the WF builder.

Example: WFINITIATOR could be excluded from an approval step to implement a "can't approve your own" policy.

4. The actual agents are the ones who really get the work item at runtime. Think of it as two intersecting circles - one containing possibles, the other responsibles. The guys in the intersecting bit are the actuals. Of course one set can be within the other entirely.

Ex: At runtime company code 2040 may evaluate to many agents, but only those who are in accounts (possible agents) - minus any excluded - will become actual agents. If no responsible agents are posssibles (no intersection between circles), WF reverts to sending it to all possibles.

Regards,

Raj.

topic Re: workflow in Application Development and Automation Discussions

workflow

Re: workflow

Re: workflow