<html 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=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.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>
</head>
<body lang="EN-GB" link="blue" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Hello fellow Wuggers,</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Glad to say that my current gig during the last few years has brought me back full circle to ‘traditional’ Workflow development after some years in the SAP Netweaver Gateway / OData murk and dabbling in the dark arts of SAPUI5.
</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve even managed to play with some of the ‘newer’ toys (yes I know they came in over a decade ago) like local workflows/events as well as block processing to build in some nice dynamic succession management and ‘in-flight’ diversions.
But those are rare highlights to be honest.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">These days there’s virtually no interest in learning traditional Workflow skills from the new breed of developers coming through. Indeed, most paths to S/4HANA look likely to kill off any legacy workflow development going forward as it’s
seen as an obstacle to a smooth transition. On the plus side, if you can call it that, S/4HANA is such a hard product to sell. SAP will have to crack the whip of obsolescence on R/3 to make them jump I think.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Frankly it seems clear to me that any batch-driven process, like workflow, is doomed in the new world, as even the concept of a batch itself will evaporate. So I do think we’re coding on borrowed time, although that feeling applies to everything
ABAP-based these days. I have reconciled myself to being a dinosaur for the tail-end of my career (so long as there’s money to be made!).</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I’ve heard about ‘Flexible’ Workflows from a friend who is now an architect on a new project that might want to use it, but it does sound a bit light on content. Who knows? I may yet have a chance to dive in and give it a whirl, but I’m
not all that hopeful given the lacklustre feel of things like SAP Hana Studio. Then again I cut my teeth on R/2 and dumb terminals, so even using a mouse can be novel to me from time to time, so what do I know?</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Mike GT<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt"><br>
From: <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a> <<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>> On Behalf Of Keohan, Susan - 1155 – MITLL<br>
Sent: Thursday, June 17, 2021 1:50 PM<br>
To: SAP Workflow Users' Group (<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>) <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>
Subject: [EXTERNAL]Hello WF'ers<br>
<br>
Hi there,<br>
It's been a long time :)<br>
<br>
I'm just curious - who is still building 'traditional' workflows, who has moved on to Flexible Workflows, and who has given up on SAP WF altogether?<br>
<br>
No this isn't a marketing ploy, I have no interest in recruiting you, I don't need your mother's maiden name, and I promise not to bother you very much in the future.<br>
<br>
All the best,<br>
Sue<br>
<br>
<br>
You can unsubscribe from a list by sending "unsubscribe" in the subject line to <a href="mailto:sap-wug@mit.edu" target="_blank">
sap-wug@mit.edu</a><mailto:<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>>. Please do not send requests for subscriptions or unsubscriptions to the lists themselves, as you will only succeed in annoying many people who will not be able
to help you themselves.<br>
<br>
This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient
or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20210617/d4117feb/attachment.html" target="_blank">
http://mailman.mit.edu/pipermail/sap-wug/attachments/20210617/d4117feb/attachment.html</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu" target="_blank">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>
End of SAP-WUG Digest, Vol 157, Issue 2<br>
***************************************<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>