on 04-28-2009 12:00 PM
Hi Folks
I am using a copy of Standard Workflow 12300111 for leaving processing in ESS. Originally WF 12300111 determines the agent based on ORG STRUCTURE however My client wanted to determine agents based on a custom table. The copied workflow brings the correct agents based on the custom table and send the approval request to them However it is also sending request to the AGENT which was determined by ORG structure as I was unable to find the Agent determination logic in WF12300111. Please guide me how to stop the WF from bringing agent based on Org Structure.
2. There is an issue in Posting as well. Although the status of Absence Request becomes POSTED but the WF stops at the WAIT STEP at the Workflow and does not proceed further.
Thanks & Regards
Waz
Hello,
How is the copied workflow determining the agents from the custom table? Probably an FM. Just check the logic to see why it's giving unexpected results.
regards
Rick Bakker
Hanabi Technology
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Can you check both the workflow are triggering at a time. Check the SPRO Configurations where you assign the custom workflow No.
Regards,
Surjith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
WS12300111 uses the BO type AAGENT to determin the agent which in turn uses the class CL_WFD_ADHOC_PROPERTY_DB to determine the ad-hoc agents for the workflow;
Regards,
Saurabh Anand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.