Hi Rick,<br>
Thanks for helping me out, Handling escalation at method level instead at workflow level, for this I need to use standard FM for forwarding workitem or there are already standard methods for deadline escalation using methods.<br>
Rick, if you can provide me some sample doc for understanding deadline escalation using methods, it will help me to achieve my purpose.<br>Thanks.<br><br clear="all">Best Regards<br>Tushar Shinde.<br><a href="mailto:tushar.shinde20@gmail.com">tushar.shinde20@gmail.com</a><br>
<br>
<br><br><div class="gmail_quote">On Sat, Dec 3, 2011 at 4:05 PM, Rick Bakker <span dir="ltr"><<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br>
<br>
If deadline/agent determination rules get too complex then the<br>
simplest thing to do is to take it outside of the workflow and put it<br>
in a method. If the minimum escalation date is 1 day then set the<br>
deadline to 1 day and call a method to decide if it really should be<br>
escalated and to whom.<br>
<div class="im HOEnZb"><br>
regards<br>
Rick Bakker<br>
hanabi technology<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Sat, Dec 3, 2011 at 8:59 PM, Tushar Shinde <<a href="mailto:tushar.shinde20@gmail.com">tushar.shinde20@gmail.com</a>> wrote:<br>
> Hi Rick,<br>
> Agent determination is already done, my concern is how it can be<br>
> handled at workflow level i.e sometimes I need to escalate to next agent but<br>
> sometimes the escalation should not happen. In same path how can I control<br>
> the escalation to happen or not to happen.<br>
> Any inputs for this.<br>
><br>
> Regards<br>
> Tushar Shinde.<br>
> <a href="mailto:tushar.shinde20@gmail.com">tushar.shinde20@gmail.com</a><br>
> <a href="mailto:ts_tushar@yahoo.co.in">ts_tushar@yahoo.co.in</a><br>
><br>
><br>
><br>
><br>
> On Sat, Dec 3, 2011 at 3:08 PM, Rick Bakker <<a href="mailto:rbakker@gmail.com">rbakker@gmail.com</a>> wrote:<br>
>><br>
>> Hello,<br>
>><br>
>> You will have to build a fairly complex agent determination method with<br>
>> ABAP.<br>
>><br>
>> regards<br>
>> Rick Bakker<br>
>> hanabi technology<br>
>><br>
>> On Sat, Dec 3, 2011 at 6:57 PM, Tushar Shinde <<a href="mailto:tushar.shinde20@gmail.com">tushar.shinde20@gmail.com</a>><br>
>> wrote:<br>
>> > Dear Workflow Team,<br>
>> > I had a scenario to be built up in my existing workflow, the<br>
>> > scenario is, my existing workflow is of 2-Levels, wherein now based on<br>
>> > the<br>
>> > new requirement I have to achieve the below mentioned purpose.<br>
>> > 1. When workflow triggers, it goes first to Reporting Manager (1st<br>
>> > Level) -><br>
>> > then to HOD(2nd Level), but now as per new requirement, if say today the<br>
>> > workitem comes in inbox of HOD(2nd Level), and if for next 1-day HOD is<br>
>> > on<br>
>> > Leave also if HOD is directly reporting to President of company, then<br>
>> > only<br>
>> > the workflow should be escalated to HR instead of escalating to<br>
>> > President,<br>
>> > otherwise no need for any escalation.<br>
>> ><br>
>> > 2. But here, the main problem is, the workitem should initially goto HOD<br>
>> > &<br>
>> > should get escalated only after 1-day, if HOD is on Leave only on that<br>
>> > particular day & only if HOD is direct reporting to President, if the<br>
>> > condition are not met than the workitem should not get escalated to HR<br>
>> > or<br>
>> > President.<br>
>> ><br>
>> > 3.Also there is apossibility of 1st Level & 2nd Level are both same<br>
>> > Agents<br>
>> > or Person, in that case I have to built a check at 1st Level also.<br>
>> ><br>
>> > One thing is sure that I have to branch into 2-condition if the person<br>
>> > is<br>
>> > direct reporting to president than 1st Branch will execute else 2nd<br>
>> > Branch<br>
>> > will execute. Now whatever escalation logic I have to implement is that<br>
>> > will<br>
>> > be in 1st Branch.<br>
>> ><br>
>> > Hope, I am pretty much clear in explaining my problem. Please let me<br>
>> > know<br>
>> > how best I can solve the problem.<br>
>> ><br>
>> > Happy Weekend.<br>
>> > God Bless.<br>
>> ><br>
>> > Best Regards<br>
>> > Tushar S.<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > SAP-WUG mailing list<br>
>> > <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
>> > <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> SAP-WUG mailing list<br>
>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div></div></blockquote></div><br>