<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=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
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: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><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi folks, <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Just to set expectations early … “mobile workflow” in SAP/Sybase is not really workflow as WUG-ers understand it – just a simple form/call mechanism. It will let us communicate back and forth with mobile, but do any sort of decent business process as WUG-ers understand them, expect to have to pair it with NW BPM or SAP Business Workflow.<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'>I would suggest you not regard mobile workflow as another type of workflow – just a feature for communicating between mobile and workflow.<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'>Expect that some of the demos you will be seeing from SAP will incorporate these sorts of scenarios. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards,<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 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span 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>mikkomr@gmail.com<br><b>Sent:</b> Saturday, February 26, 2011 6:24 AM<br><b>To:</b> sap-wug@mit.edu<br><b>Subject:</b> RE: WDA & ABAP Objects -Percent of WF'ers using them? <o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Rick,<br>Having read your posts and getting a glimpse of your abap / abap oo skills in the past, learning wda shouldn't take you that long. There are lots of good tutorials in sdn as well should you be a self learner.<br><br>For portal / web browser based use cases, wda would be my first choice for delivering new ui:s for any sap business suite app. <br><br>For mobile access, the choice is a bit trickier. In the past most mobile ui:s have been web browser based and developed with its, bsp, wdj/wda with the basic principle of optimizing their user experience for fast access. This is where wda also stands and it provides some useful features like the page scaling & dynamic layout mentioned in previous posts.<br><br>Currently in the iOS/Android(/Symbian since I come from the land of Nokia :) ) era however, web browser access is not that wanted any more and people are looking more into native mobile apps with better usability and enhanced features.<br><br>My suggestion would thus be to keep a close eye on the SAP/Sybase offering, they are pretty soon launching e.g. their mobile workflow solution (kind of a mobile uwl) which can be installed on any major mobile operating system enabled phone. Sdn has more material on this if you're interested and of course there are many 3rd party mobile apps which can do the same thing if you can't wait for SAP's offering to be fully available.<br><br>Regards,<br>Mikko<br><br>Date: Fri, 25 Feb 2011 07:59:51 -0600 <br>From: "Sample, Rick" <Rick.Sample@graybar.com> <br>Subject: RE: WDA & ABAP Objects -Percent of WF'ers using them? <br>To: "SAP Workflow Users' Group" <sap-wug@mit.edu> <br>Message-ID: <804C1CFBDB06C9428368F4B9023839748406270CCB@SEMBV1PW.graybar.com> Content-Type: text/plain; charset="iso-8859-1" <br><br>Hi Mikko, <br>I have no WDA experience -yet. Will be pushing for training soon. <br><br>Simple question and please forgive my ignorance. I am assuming WDA will be better choice for Portal and smart devices? <br>There are business folks asking when we will support iPhone, BB, and iPads, etc. for simple Approve / Reject type WFs. <br><br>Thank you for your time, Rick<br><br>Sent from my HTC<o:p></o:p></p></div></body></html>