container elements settings

[Michael Pokraka]

Ah, I meant that it appeared random to us at the time, but could have bee=
n
your problem and we simply didn't notice the import/export bit.
 
Raised eyebrows or not - a retransport might just work, I'd suggest givin=
g it
a go (and let us know if it worked). Appparently it's got something to do=
 with
an incorrect import sequence that can creep in in some circumstances.
 
I also just checked the message on a 620 system - the message I get is si=
mply
an info message - so nothing is broken.
 
Cheers
Mike
 
Robert.vande.Berg at nuon.com wrote:
> That's a solution, but here, it isn't random what isn't transported.
> It really are the elements which are not marked as Import Nor Export.
>
> And the transportteam doesn't do 3 times the same transport... THAT giv=
es
> raised eye browse.
>
> It looks just, since elements which are not marked as IM- nor Export, l=
ook
> like elements which are not used. But why doesn't it give an error then=
 on
> Development?? (i.e. binding check error "Element is not marked as
> IMPORT/EXPORT")
>
> -----Oorspronkelijk bericht-----
> Van: Michael Pokraka [mailto:workflow at quirky.me.uk]
> Verzonden: maandag 2 februari 2004 17:55
> Aan: SAP-WUG at MITVMA.MIT.EDU
> Onderwerp: Re: container elements settings
>
>
> Aaaahhh, that rings a big gong! Though it may not be the right one. A w=
hile
> back we had some really weird problem where elements would randomly not=
 be
> transported. A retransport would do the trick to make them appear, perh=
aps
> you
> could give that a go and the import/export is just coincidence, or it w=
as
> the
> 'common factor' that we missed at the time.
>
> There was also a thread 2-3 months ago about transporting WF's three ti=
mes
> to
> make sure they arrive safely... Ah, found it, just plug "Repetitive
> Transport
> Strategy" into wugarchive.com.
>
> Cheers
> Mike
>
> Robert.vande.Berg at nuon.com wrote:
>> Nice to know that.
>> But when data is used in several tasks, shouldn't the parameters of th=
e
> 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 ne=
xt
> task (import/export) to the next method (import).
>>
>> Big (/next) problem is that, when the container elements are NOT marke=
d 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 me=
thod
> 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 t=
o
> 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 m=
ethod
> are marked as IMPORT and EXPORT.
>>
>> Does anybody know why the settings are not set?
>>
>> Regards,
>> Robert
>>
>>
>
>