<div>G'day Vijay,</div>
<div> </div>
<div>In the case of the absence demo the mulitple outcomes are a due to the 'Result' parameter. In these case you get a possible outcome for each of the fixed values of the result type.</div>
<div> </div>
<div>The other alternative is method exceptions which you can then model by turning the on in the outcome tab of the step.</div>
<div> </div>
<div>In both cases it is a normal activity step.</div>
<div> </div>
<div>Good luck,<br>Mark<br><br> </div>
<div><span class="gmail_quote">On 6/1/06, <b class="gmail_sendername">vijay srikanth</b> <<a href="mailto:vijay_d15@hotmail.com">vijay_d15@hotmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>When we enter a task in a workflow, there are either executed or rejected<br>outcomes.<br>How do I have multiple outcomes of my own there. like in the absence
<br>notification, workflow<br>there are multiple outcomes, like accepted, rejected. Is this done as a<br>normal activity step or is there any other step type for such tasks. If it<br>is done as normal activity, then for my custom business objects/tasks how Do
<br>I add multiple outcomes in my workflow task.<br><br><br>Regards,<br>Vijay<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">
http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br></blockquote></div><br>