Forwarding user decison in workflow

[Former Member]

Hi,

We are using the user decision step with three options 1. Accept 2.Reject  3. Edit ECM. If the user choose Edit ECM, transaction CC02 will be called from the Dialog step which using the ECM BO method. Also we are looping back the decision step to display the user decison again when the user comes out of transaction. The above stuffs are working fine.

Now we are facing some issues while forwarding this work item to other users. If the user forwards this work item, the person whom it forwarded is getting the task but if that person choose Edit ECM the work item is disappearing.

In binding both the steps having the same expression for the agent. I hope if we pass the actual agent of user decison step to Dialog step this problem will be resolved. But I want to know is there any other way to solve this problem.

Appreciate your help.

Regards,

Muruganantham

[pokrakam]

You have already answered your own question:

Muruganantham Sekar wrote:
...I hope if we pass the actual agent of user decison step to Dialog step this problem will be resolved. But I want to know is there any other way to solve this problem.

That is indeed the way to go about it. If the item can be forwarded to someone who is not an original recipient of the decision, then you need to pass the actual agent back. There are a couple of ways to do this:

1. You can populate an agent table container element and use that for your WF step agent. The _actual_agent from the edit step is then added to the table, and with "Advance in dialog" switched on (default), they should pop right back into the decision step.

2. The "edit" decision outcome branches off into a new set of decision/edit steps in a loop with the actual agent as the agent for all steps. This means you will end up duplicating the decision & edit steps in your WF design, but don't need to mess around with agent tables as per previous option. The other thing with this approach is that once in an edit loop, the other agent(s) can no longer see the work items.

Regards,

Mike

[ronen_weisz]

As Anjan wrote, you need to get the agent of the first workitem and use it in the second one, use wi_actaul_agent from the first task as the agent of the second one.

Also, I would suggest you add an new object to the task enabling the edit option as it's default method, and then you will have no need for the loop at all since users can press the link edit the ECM and go back to the original task.

[Former Member]

Hi Ronen,

Thanks for your reply.

Our client does not want the link to navigate to the transaction. They want a separate option in the user decision itself for calling transaction.

[I042439]

Hi Muruganantham

Can we assume that you are looping back if the user is NOT taking any decision and just opening-closing the screen?

If yes, then you are looping back to send to the SAME set of agents which were determined earlier......WHICH does not include the forwarded agent!

Instead of loop back, to make sure that the user "takes" a decision, why not use "Confirm End of Processing" check box in teh task definition? The design will be much simpler.

Regards,

Modak

[Former Member]

Hi Modak,

Thank you for your reply.

I agree your suggestion of using 'Confirm end of processing' for getting the user decision back in inbox. But our requirement different. If the user comes out of CC02 transaction the user still needs to be in the user decision step where the options are displaying. That's why we are looping backing.

[anjan_paul]

Hi,

I think the provlem is , after forwardin Edit ECM step is workin fine. But after step, you use some specific agent in the next step, which is not included new agent's id. That why new agent is not gettin next step workitem