Webflow

[Dart, Jocelyn]

Hi All,
We seem to be getting some confusion happening between the two parts of
webflow, i.e.
a) Dialog webflow - e.g. where a user executes a workitem via the
web
b) Automatic webflow - i.e. where XML documents are communicated
between workflows
 
These are two separate areas (although both part of "webflow") and
work quite differently.
 
Dialog webflow works using the Internet Transaction Server i.e. SAP's ITS
and uses FORM.HTMLPROCESS tasks with generated web transactions.  It is
available from R/3 3.1.
 
Automatic webflow uses web activity tasks and is available from R/3 4.6C.
 
I gather Dave is talking about Dialog webflow, but Nicholas is talking
about automatic webflow.
 
Please don't confuse the two, folks in your questions.  They really
do use quite different techniques.
 
Re Dave's question.
You only have to stick to "Simple" container elements if you want to use
the generated web transaction (generated from your FORM.HTMLPROCESS task)
as is.  You should definitely stick to simple container elements for the
result of your task to keep the binding to the workflow simple.
However if you want to use more complex structures to build the
web display, you can bind complex structures, e.g. object references
to your HTMLPROCESS task, but you will need to change the generated
web transaction to read these references out of the container and use
them.
 
This is ok - the generated web transaction is in the customer namespace
so you are allowed to change it.  You can use the workflow API
(function modules in function group SWWA) to get extra information
about the current workflow/task/container/etc.
You can add to the generated code and screens just be careful not to
lose the generated code so that all the bindings still work.
 
 
As an example there are a number of web transactions in EBP/BBP and
ESS that use this technique - i.e. just use the generated web
transaction as a starting point.
 
You do need an ABAP-er with dialog programming skills and some HTML
knowledge to adjust the matching ITS service files/templates.
 
Regards,
Jocelyn Dart.
SAP Australia.
 
-----Original Message-----
From: Nicholas Brand
To: SAP-WUG at MITVMA.MIT.EDU
Sent: 3/20/01 12:22 AM
Subject: Re: Webflow
 
Memo from Nicholas N Brand of PricewaterhouseCoopers
 
-------------------- Start of message text --------------------
 
Dave,
 
I have recently created a WebFlow that triggers a workflow in a separate
SAP
system across the company's intranet; it also waits for feedback before
continuing.
I read the documentation too and came to your conculsion.
The generated Wf-XML can only get its data from the Web activity Tasks
container
- these are then sent to the receiving workflow's workflow container.
So, no objects can be sent, only their attributes via the tasks
container
elements.
 
 
Kind regard,
Nicholas Brand
SAP Consultant
PricewaterhouseCoopers
 
 
 
 
 
 
 
Dave Shoemaker <david.shoemaker at esapient.com>@MITVMA.MIT.EDU> on
19/03/2001
13:09:19
 
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
 
 
Subject:  Re: Webflow
 
 
Hello,
Regarding Webflow, I have been confused on what seems
to be a contradictory point in the documentation. The
workflow performance tips indicate that it is better
to use the attributes of an object than container
elements when a large structure is required. However,
the webflow docu. seems to say that the module pool
generator for forms, and thus the IAC generator for
Webflow, can only see container elements. I therefore
conclude that if I have a large structure yet desire
to implement using webflow, I must design a large
container, moving my object's attributes in and out
of it.
 
Any comments?
 - Dave
 
 
--------------------- End of message text --------------------
 
The principal place of business of PricewaterhouseCoopers and its
associate
partnerships is 1 Embankment Place, London WC2N 6NN where lists of the
partners' names are available for inspection. All partners in the
associate
partnerships are authorised to conduct business as agents of, and all
contracts for services to clients are with, PricewaterhouseCoopers. The
UK
firm of PricewaterhouseCoopers is authorised by the Institute of
Chartered
Accountants in England and Wales to carry on investment business.
PricewaterhouseCoopers is a member of the world-wide
PricewaterhouseCoopers organisation.
----------------------------------------------------------------
The information transmitted is intended only for the person or entity to
which
it is addressed and may contain confidential and/or privileged material.
Any
review, retransmission, dissemination or other use of, or taking of any
action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited.   If you received this in error,
please
contact the sender and delete the material from any computer.