multiline attribute problem

[Breslavets, Sergey]

Koenraad,
check the way you have task-workflow binding defined for your multiline element
- if you have "Append"-type binding (with // at the end) it will append lines
from your element from task container to the existing records in the workflow
container (i.e. not clearing it)... Use "Replace" type binding if you need to
replace the content everytime.
 
Thanks,
Sergey
 
-----Original Message-----
From: Koenraad Janssens [mailto:koenraad.janssens at sidmar.arcelor.com]
Sent: Thursday, June 12, 2003 3:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: multiline attribute problem
 
 
Hello all
 
We have a problem with a multiline attribuut.  The situation is as
follows:
 
1.  multiline (table) attribute in wf container filled with elements
2. binding with task and method container works normal
3. in the method the multiline (table) attribute is cleared and refreshed,
so all table elements are deleted
4. binding between method and tasks works...  table in task container is
cleared (set by SWC_SET_TABLE macro)
5. binding back to the wf container of this empty multiline (table)
attribute does not work...   Elements in wf container are not cleared.
 
After talking to OSS support it seems that this is SAP standard.  A empty
attribute is seen as "no data" and is not copied back to the wf container.
A possible solution is Note 387516 which modifies SAP standard.
 
We are wondering if there isn't a macro like function to directly modify
(clear the attribute) the wf container, so we are not obliged to modify
SAP standard.
 
Kind Regards and hoping for a solution....
 
Koenraad Janssens
 
 
********************************************************************************
***
This message should only be read by those persons to whom it is
addressed, and may contain confidential information, the disclosure
of which is prohibited. This message is not intended to create rights
or obligations without subsequent written confirmation of its contents.
If you have received this message in error, please notify us immediately
********************************************************************************
***