<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 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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;}
@font-face
        {font-family:"Comic Sans MS";
        panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
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-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hello Wuggers,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hope someone can help me here:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have a requirement in a workflow to have a two-part approval process for the Incoming Invoice (BUS2081) business object. The first part of the approval process is to have the approver open the document in Edit mode and review and make revisions to a restricted number of fields. Once their review is done, we want them to click “Save as Complete” and then automatically advance to the second part of the approval process where the user decision (approve or reject buttons) appear.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>For the first step of the process, I am using the standard EDIT method of the object and when I define my task for using this method, I assign the terminating event “COMPLETED” so that the task will only complete when the user clicks “Save as Complete”.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The problem is that the EDIT method for this object is asynchronous:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=405 height=378 id="Picture_x0020_1" src="cid:image001.png@01D0AF4E.2E145A20"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So the “advance with dialog” option does not work to automatically advance to the user decision step where the approve/reject buttons will appear.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I tried to create my own custom synchronous method in the object that was a copy of the standard method. I then created a new task to execute this new method and defined the same terminating event. However, the problem with that is when I insert the task into the workflow, there are two outcome paths. One path is for the terminating event I assigned but the other path is the normal “advance” path. This causes the workflow to advance to the user decision step when we don’t want it to. We only want it to advance when they click “save as complete” and raise the COMPLETED event. With this configuration, the step advances when they click other options on the screen like “back”, “exit” or “cancel”.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=403 height=471 id="Picture_x0020_2" src="cid:image002.png@01D0AF4E.2E145A20"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The workflow builder will not allow me to deactivate the “Step executed” outcome for the step:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=600 height=190 id="Picture_x0020_3" src="cid:image003.png@01D0AF4E.2E145A20"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Error message that occurs when you try to deactivate this outcome:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><img width=975 height=309 id="Picture_x0020_4" src="cid:image004.png@01D0AF4E.974AB570"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I’m trying to figure out is there some way for me to get around these limitations?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Comic Sans MS";color:blue'>Loren Bratzler<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:gray'>Norfolk Southern Corporation<o:p></o:p></span></p></div></body></html>