Skip to Content
1
Apr 14, 2011 at 04:10 AM

Customization Done for 2 level approval of leave in ESS but Facing Problems

975 Views

Hi Friends,

In our ESS Project we have customized our workflow to work for 2-Level Approver, but the problem we are facing is

1. When the Leave Request is created by say for eg:- INITIATOR1 user, it goes for 1st Level Approver i.e APPROVER1.

2. When APPROVER1, logs in and checks the UWL, a Workitem is there in the UWL for Approval, When APPROVER1 opens the workitem, he can see all the accumulated request in the Show Worklist. When he selects the INITIATOR1 request and clicks on Approve, the request status changes to Sent, and also the UWL Workitem also gets removed from the APPROVER1 UWL and a workitem is gone to 2nd Level Approver i.e APPROVER2, but the Problem is if some other workitem related to Leave is there in APPROVER1 UWL, in that case he can still see the INITIATOR1 request with status SENT and if he clicks the request and Approve/Reject its, then it is actually the action of the 2nd Level Approver, i.e. APPROVER2, so it gets approved on behalf of APPROVER2, which should practically not happen.

3. If the APPROVER1 approves and does nothing, and if APPROVER2 logins and opens the request and Approves it, then the entry gets POSTED and the workflow gets completed successfully.

Please guys correct me, if any mistakes we had done in our Leave Request Customisation. Please do give any inputs for the same. Is there anything extra needs to be done in standard Leave Application if the Workflow is customised for 2-Level Approval. Is there anything missing in SPRO Configuration to make the Standard Application behave for 2-level Approvers.

Hope, the points I mentioned gives a clear idea of my problems, may be I am closed to Solution but because of some bad configurations mistakes i had done, the application might be misbehaving.

If any more explanation is required, please do let me know.