<div dir="ltr"><div class="gmail_default" style="font-size:small">Kjetil</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Yes, I am looking at Cloud Wf. I am very bullish about SCP, I believe the SAP story and think the whole IT industry is moving to Cloud Services, so I am keen to get to work with SCP Wf. It could be that SCP Wf follows a similar path to Portal Wf. That is 'I don;t know of many implementations using it', but I do think the driving factors are different now and think SCP Wf will be used. If it is, SAP will need to build more admin around it. For instance, if a SCP Task was delivered to a User that does not exist, I would not know how to move the workitem to a new User. I also would not know how to set up a substitute (as an admin).</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Maybe Jocelyn or someone will put me right?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Andy </div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">---------- Forwarded message ----------<br>From: Kjetil Kilhavn <<a href="mailto:list.sap-wug@vettug.no">list.sap-wug@vettug.no</a>><br>To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>Cc: <br>Bcc: <br>Date: Thu, 10 May 2018 04:59:09 +0200<br>Subject: <div class="gmail_default" style="font-size:small;display:inline"></div>Re: Re: SCP Workflow question<br>
<div text="#000000" bgcolor="#FFFFFF">
<p>Ahhh, finally dawned on me that SCP is not just any old acronym -
you are working on a SAP Cloud Platform workflow solution.<br>
Sad to say I don't really know anything about that yet - so my
input may be completely useless. (Or should I be happy to say I
don't know anything about SCP Workflow yet? Hmmm...)<br>
</p>
<br>
<div class="m_6489759359010409357moz-cite-prefix">Den 09. mai 2018 12:13, skreiv Andy
Curtis:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-size:small">Maybe I am
doing a poor job of explaining because we do have a team of
experienced mobile people. </div>
<div style="font-size:small"><br>
</div>
<div style="font-size:small">We originally
said, 'when user presses 'submit' there should be 2 things
happen, the 'request' should be saved and Wf should be
triggered. They read this as 2 client side actions (1 to send
screen data to the server, the second to trigger Wf) and were
concerned what would happen if the first action succeeded and
the second failed. The answer to that is to have 1 server
side service to receive the screen data, create a database
record and trigger Wf). But the pushback came that if there
was 1 client side action to trigger Wf (server side) passing
the screen data to the Context, then Wf could create the
database record as the first step. </div>
<div style="font-size:small"><br>
</div>
<div style="font-size:small">Thats where
my karma is suffering. I believe it is 'right/correct' to
have a server side service receive the screen data, create a
'request' on a database and then trigger Wf. Replacing the
server side service to receive the screendata and trigger Wf,
I think is fundamentally wrong because I have never created a
Wf that did not have an business object/Class instance when it
started.</div>
<div style="font-size:small"><br>
</div>
<div style="font-size:small">Thoughts?</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="m_6489759359010409357gmail_signature" data-smartmail="gmail_signature">Andy<br>
</div>
</div>
<div class="m_6489759359010409357gmail_signature" data-smartmail="gmail_signature"><br>
</div>
</div></div></blockquote></div></blockquote></div><br></div></div>