<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Max, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>You might want to take a look at workflow patterns generally... <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For 5. Usually a loop with a background step to check if there are more approvals to go, plus a background step to get the number of approvals. That way if you add more levels or reduce levels later you are covered. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For 6. You want to think about using a subflow and raising an event in the subflow on rejection – the main flow responds to the rejection by restarting at wherever you need. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Re your statuses ... no we don’t usually bother with multiple approval statuses – you can always use a container element to keep your intermediate status – but you need to think about what information the initiator needs to see to know where the approval is up to. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Jocelyn <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Max S Gro<br><b>Sent:</b> Thursday, 2 June 2011 10:45 PM<br><b>To:</b> SAP Workflow Users' Group<br><b>Subject:</b> Offline PDF Form and Workflow Integration<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi WUG-ers,<br><br>Due to my lack of SAP workflow knowledge, I would like to apologize beforehand for my silly questions. Please kindly bear with my questions.<br><br>I have the following scenario:<br><br>1. Offline interactive PDF form with "Submit" button.<br>2. Once "Submit" button is clicked, it will call web service.<br>3. Web service will save the form entries into custom table and trigger the event.<br>4. By triggering the event, system will then trigger the customized workflow. <br>5. Depends on certain condition, number of approvals will vary (the setting is in custom table). <br> example: < 1000 = 1 level of approval<br> 1000 - 3000 = 2 level of approvals<br> 3000 - 5000 = 3 level of approvals <br> <span style='color:#3366FF'>Q: How do i do this kind of dynamic level of approval ? </span><br>6. Any Approver can "approve", "reject" or ask requester to "revise" (change the application).<br> "Approve" and "Reject" will end the workflow cycle.<br> "Revise" ---> requester needs to change the application from offline interactive form and "Re-Submit" the application. <br> <span style='color:#3333FF'>Q: For "Revise" case, how can i continue the previous workflow cycle ?</span><br><br>I have the following status:<br>S = Submitted<br>A = Approved (by all approvers)<br>R = Rejected<br>V = Revised<br>T = Re-Submitted<br><br> <span style='color:#3333FF'>Q: Best practice: do i need different status for different level of approval (eg: A1 = approved by 1st approval, and so on) ? </span><br> <br>I marked my questions in blue. Hopefully i explain the scenario clearly. <br><br>Again, apologize for my silly questions.<br><br>Thanks In Advance !!<o:p></o:p></p></div></body></html>