Forwarding not allowed Attribute

[Former Member]

Hi Guys,

First of all, I would like to explain my situation before posting my question.

We have a lot of different active workflows. All of them have more or less the same way of working and design. We have our own User Decision tasks. The possible agents of these tasks are all users because they have “General Task” attribute and the Agents are determined via Rules.

Now, we need to limit forwarding functionality. I have found “Forwarding not allowed” attribute could work for us.

Question: if I set “Forwarding not allowed” attribute, who are the Possible Agents? Because after this change was made, nobody has received the workitem.

We are working on ECC 5.0

Thanks in advance!

Regards,

Nancy

[Former Member]

Hi Srini,

We finally concluded this issue, changing all Standard Task of Dialog processing with "Forwarding not allowed" attribute and using Security Roles to Agent Assignment that represent the whole universe of SAP users.

You know that "General Task" Attribute of Standard Task indicates that all SAP users can perform this task. But when you change this attribute by "Forwarding not allowed", you must explicitly assign the possible users of the task. We found a custom Security Role that surely all users has assigned in their profiles and use it.

Example: in pftc transaction, I enter Standard Task 8267 "Generic decision task" in display mode. Then go to menu Additional Data - Agent assignment - Maintain

1) in Attributes... button, select Forwarding not allowed radio button

2) go to menu Agent Assignment - Create - Object type Role: in our system the name of the role is: ZGL:X_X_DIS_ALL_USR_FUNC All User General Functions

I hope this can help you, please, could you reward point to me if you consider it helpful? this could be my first rewards point

Regards,

Nancy

[Former Member]

You have to assign agents to this task separately. FRom the screen where U change task attribute. Unless the agent is assigned in this task the agent will not receive workitem though the agent determination will show retrieve that user.

You get error message Agent assignment does not agree with task assignment.

Thanks

Arghadip

[Former Member]

Hi Gurus,

Thank you very much! We have found the more convenient proposal using "Forwarding not allowed" attribute plus assigning a common Security Role that all SAP users have in their profiles.

Regards,

Nancy

[Former Member]

Hi

Can you please elaborate on this , we have a similar requirement. The agents who receives the work item should not be able to forward it to others

When I change the task attributes at maintain agent assignment screen and come back to the workflow template and do consistency check I am getting a warning message that the task has no agent assignment.

Thanks

Srini

[KKilhavn]

Setting the flag should not have such an effect, it shouldn't at all influence possible agents, or who will receive the work item. It should only disable the forwarding function (for the work items of this task) once the work item has reached the agent(s).

[former_member184112]

Hi,

Answer is here about Possible Agents and Forwarding

Possible Agents: Who is allowed to do the work

Possible Agents: People who are allowed to execute the work item based on a particular task. Possible agents are assigned to a task not the work item. Assigning as possible agent doesn’t give access to the routine called by the task. Authorizations should be provided, only then the work item can be executed.

If no possible agents are assigned, no one can execute the work item.

User who is organizationally authorized to start a task and execute the work item associated with a particular task.

Possible agents are assigned to a task not the work item.

Without possible agents a task cannot be executed.

Possible agents are usually expressed with organizational units, positions and jobs instead of user names.

Assigning as possible agent doesn’t give access to the routine called by the task. Authorizations should be provided, only then the work item can be executed.

Note:Marking the task as general task makes everyone to be a possible agent.

Recipients has the facility to forward the work item to other agents.

Possible agents (but not excluded) only can execute the forwarded work item.

Forwarding is controlled by forwarding attributes of task.

General Task: Can be forwarded to any user and executed by any user

General Forwarding: Can be forwarded to any user

No General Forwarding: can be forwarded to possible agents only

No forwarding (No forwarding allowed)

Thanks and Regards,

Prabhakar Dharmala

Message was edited by: Prabhakar Dharmala

Now You need to create Organizational Unit for possible agents if you select as GENERAL TASK it takes all user, for limit users you need to create Org unit assign required users there and it will work as possible agents at forwarding not allowed