AW: Workflow Forms

Rickayzen, Alan alan.rickayzen at sap.com
Wed Jul 7 10:22:21 EDT 2004


Rick,
You might want to look at the overview of simple forms on
http://www.sapinsideronline.com/spijsp/article.jsp?article_id=3D34014&vo=
lume_id=3D4722
registration required (free).
 
Best regards,
Rick ;-)
 
-----Urspr=FCngliche Nachricht-----
Von: SAP Workflow=20
Gesendet: Mittwoch, 7. Juli 2004 03:07
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Workflow Forms
 
 
Rick,
Yes a form step uses a flat structure - no multilines - no complex =
structures.
 
If you want to use more complex values then you have a couple of =
options:
 
* Use multiple individually named elements in your flat structure, e.g. =
row1field1, row1field2, row2field1, etc.
(not ideal but practical)
 
* Pass over enough info in your flat structure to go back and read the =
multiline detail from the workflow container
Note: **workflow** container not workitem - the form step talks =
directly to the workflow container.
 
* Hold the mutliline data in a custom table and pass over sufficient =
key data to access the custom table from the form
 
Use the flow logic of the form step screen to retrieve the necessary =
data.
 
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Gray, Jeffrey
Sent: Wednesday,7 July 2004 6:02 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Forms
 
 
I remember reading somewhere that the structure had to be a "flat" =
structure to be used in a form - I took this to mean data elements only =
- I will be watching to see if that is not the case.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of =
Josefek, Richard
Sent: Tuesday, July 06, 2004 1:23 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Forms
 
 
Thank you Jim, but perhaps I wasn't clear with my question.
Let me try again.
There is a new FORM element in workflow for the Enterprise release. I =
have only been able to get the form to work on a container element that =
is defined by a structure but is not multilined.
I have multilined container elements in my workflow that I would like =
to create a form around, but the FORM element doesn't seem to recognize =
the container element if it is multilined.
My question is, has anyone been able to use the form element with a =
multilined container?
 
Rick
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of =
Jim
D Hill
Sent: Tuesday, July 06, 2004 12:20 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Forms
 
 
Hey Rick ,
I just got through creating an object to pull in workflow log via
container. This container element
is multi-line. You have to make sure the object uses the swc_set_table
container instead of the set element.
Otherwise it will not write multi line.
 
 
Jim
 
 
 
 
"Josefek, Richard" <RJosefek at MassMutual.com>@MITVMA.MIT.EDU> on =
07/06/2004
12:08:41 PM
 
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:
bcc:
Subject:    Workflow Forms
 
 
Hi Fellow Workflowers,
 
There are some additional workflow steps added with R/3 Enterprise. One =
of
which is a FORM step. This step relies on a predefined structure as a
workflow container element.
I have had success generating forms with a container element who's
structure is NOT multilined, however I have not had any success with
multiline elements.
I am wondering if anyone has had any experience with this step. Any =
tips
and tricks for using multiline containers ?
 
 
         \\||//
         (o  o)
 oOO---(_)---OOo
 | Rick Josefek |
 |      ESP         |
 |    744-7142    |
 |  MIP S396     |
 ----------------------
      |__| |__|
        | |   | |
     ooO Ooo
 
 
---------------------------------------------------------
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.
 
 ---------------------------------------------------------
 


More information about the SAP-WUG mailing list