Workflow Agent not Determined for Task with Classification

[Former Member]

Hi All,

I am having an issue with Agent Determination when using a Task that has a classification to prevent forwarding (see classification below).  From what I can tell, this is defined correctly in order to prevent forwarding.

My rule also appears to be working correctly based on testing via PFAC (see below).

The Bindings appear to be correct (see screen below) within the workflow.

However, when testing the Workflow, the agent does not appear to be determined.

I am not sure what I am doing wrong.  When I test the rule scenario in PFAC it provides the correct agent yet the WF fails for the same scenario.

Can anyone help me understand what I am doing wrong?  Thanks in advance for your help.

John  

[I042439]

Hello Jon

You need to make it general...the task classification for your case should be "General Forwarding Not Allowed".

Without setting it to general, the systems looks for possible agents in the task (Agent Maintenance) ...which is empty. "Actual agents" is an intersection of Possible Agents from the task (which is empty in your case) and the Possible Agents from your rule. Hence there is no agent.

Once you make it general - it means all users are possible agents and the rule agents help get he intersection of Actual agents.

Remember that it is a client dependent activity and you need to transport it to other clients. Also remember to put that in a transport request when moving to other systems.

Regards,

Modak

[Former Member]

Hi Modak,

Thanks for your reply.  I made the change to General Forwarding Not Allowed.  However, I get the same result.  No agents were determined for the Task.

Any other suggestions?  Thanks.

John

[I042439]

Hi John

Did you do the change in one client and testing in other? If yes, do an SCC1 of the transport to the test client (if you save d it in a transport)

Did you do the change and then triggered a new instance or are you checking the older instance? If checking the older instance; try triggering the a new instance and then check with the latest work item.

Also, it is never harmful to run a buffer refresh after changes - tcode SWU_OBUF

Regards,

Modak