You are not a receiver of the work item in ESS Leave

Question

Hi,
We are using standard ESS leave application in our portal, where employee can raise leave and his manager can approve/reject his leave. But I want in case manager rejects the leave, the rejected leave should not come into MSS UWL of employee, we will send a mail to employee and he can again login to ESS leave application and where he will see the rejected leave and he can re apply/change/delete  the rejected leave. We do not want rejected leave to come in UWL of employee as a work item.
As of now when manager rejects the leave rejected leave of an employee , it is coming in UWL of the employee which we do not want, so what we did, we went to standard leave work flow template WS12300111, in that we double clicked on Task (TS12300116, Process Request by Employee) and in that  we clicked on agent assignment icon and than we clicked on attribute and we selected General forwarding not allowed radio button, by default general task radio button was selected.
After selecting General forwarding not allowed radio button, even when manager rejects employee leave, rejected leave is not coming in UWL of employee which we want exactly, but another error is coming when employee goes to ESS leave application again and change or delete this rejected leave he is getting the error You are not a receiver of the work item .
But if we select general task radio button in agent assignment in work flow , than eveything is working fine but employee is getting rejected leave in his UWL, that we do not want  at all, so why after selecting different radio button this error is coming ?
Why employee is getting this error, why employee can not reapply/change his rejected leave. Is this portal error OR workflow error OR HR configuration error and  what is the solution for this..

Answer 1

If you need this option then you need to change the WF Task.
General Forwarding Not Allowed
This indicator enables you to determine that work items for this task can only be forwarded to users who are agents for the task.
If this indicator is not set, a work item for this task can be forwarded to all users.
The best way to take care of User
Forwaring authorization is the Task Classification (PFTC -> Additional
Data -> Classification). Classify tasks with General Forwarding Not
allowed, will give you the oppotunity to let the user allow to forward
items JUST to the Possible Agents Assigned to the task
(Additional Data -> Agent Assingment -> Maintain)...
Clear that everything depends on How you have developed your workflows
definitions. In that cases  the best think to do is
create Different Tasks definition (TSxxxxxx) and let they start
depending on Company Code (That can be driven via Conditions steps in
the workjflow definition, for example). This will allow you to define
Just the responsible Agents per each task, depending on the Companny
Code. This definitively Resolve the Forwarding frelated Question.