container elements settings

[Rick Sample]

I have had Container elements not transport. 
 
Every time this issue surfaced I looked at the WF Template.
(This is the first screen of the WF before you click on the "Workflow Builder" to get to the "Definition".)
I did not see my elements in the Template even though it is in the next screen (Definition screen).
 
I added the same container to the "Template" that is in the "Definition" and then it transports just fine. 
Don't know why this happens and never got a clear answer from SAP as to why. Sometimes 
when I add a container to the Definition it shows, sometimes not. 
 
If the container element shows in the "Template" it transports. No matter if it is IMPORT/EXPORT. 
 
Works for me...
 
Rick Sample
Graybar, Inc.
WF / Java Developer
 
 
>>> jocelyn.dart at sap.com 2.3.2004 12:44:59 AM >>>
Robert,
No they shouldn't be - it's a transport problem not a workflow problem.
So have a look at the suggestions by the others...
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Robert.vande.Berg at nuon.com 
Sent: Monday,2 February 2004 7:41 PM
To: SAP-WUG at MITVMA.MIT.EDU 
Subject: Re: container elements settings
 
 
Nice to know that.
But when data is used in several tasks, shouldn't the parameters of the
workflow elements also be IMPORT and EXPORT?? I always thought that the data
is passed from the method (export), to the task (import/export) to the
workflowmodel (IMPORT) and then via the workflowmodel(EXPORT) to the next
task (import/export) to the next method (import).
 
Big (/next) problem is that, when the container elements are NOT marked as
IMPORT or EXPORT, the elements are not taken along in transport. Then, on
the target system, the workflow returns with syntax errors, because the
element which is used in a bindings, is not present.
 
Regards,
Robert
 
-----Oorspronkelijk bericht-----
Van: Dart, Jocelyn [mailto:jocelyn.dart at sap.com] 
Verzonden: maandag 2 februari 2004 8:58
Aan: SAP-WUG at MITVMA.MIT.EDU 
Onderwerp: Re: container elements settings
 
 
Hi Robert,
Yes that's right - the parameters are import/export at the task and method
level because the workflow has to be able to pass the data down through the
task to the method.
 
However the workflow may just be passing internal container elements to the
task - i.e. to the workflow the task is just being used to do some sort of
intermediate activity or calculation - the workflow itself doesn't need to
pass that information out again to another workflow or event.
 
You only need workflow container elements to be import/export if the
workflow is:
* Accepting data from an event/calling workflow - import elements
* Returning data to a calling workflow - export elements
 
Regards,
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Robert.vande.Berg at nuon.com 
Sent: Friday,30 January 2004 11:49 PM
To: SAP-WUG at MITVMA.MIT.EDU 
Subject: container elements settings
 
 
All,
 
When creating a task in a workflow model, the bindings are generated.
The problem is that the generated container elements in the workflow model
are not marked as IMPORT nor EXPORT, but the elements in the task and the
method are marked as IMPORT and EXPORT.
 
Does anybody know why the settings are not set?
 
Regards,
Robert