strange container and binding behaviour in WAS 6.40

[Mike Pokraka]

Has the object changed? Is everything already up to date by the time you are
evaluating the condition? If you check it immediately after a change the
data may not be in the database yet, but everything is there by the time you
look at the container. 

 

 

Otherwise it may be that the system is just tired because it's Sunday.

 

Cheers, 

Mike

 

  _____  

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Ronen Fox
Sent: 25 June 2006 14:19
To: sap-wug at mit.edu
Subject: strange container and binding behaviour in WAS 6.40

 

Greetings dear workflow experts,

 

While working on an ECC 5 system, some strange things happen to the
container elements and binding operations.

 

Example: a business object has an attribute that I want to transfer to the
workflow container.

 

A container element for the business object exists in the WF and also a
separate container element just for this specific attribute.

 

After defining a binding between task --> WF, no data is passed.

 

Another example: The container element for the object in the WF container is
filled and contains all the data and can be viewed in the technical log.
However, trying to set a condition or a container operation to work with one
of that object's attributes always fails and the system treats it as an
empty container with no value.

 

All of this was working perfectly in R3 versions 4.6 & 4.7, If anybody has
any idea what is going on, I'll be very thankful.

 

Best regards, 

 

Ronen Fox

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060625/f078c8d8/attachment.htm