Condition: Object Exists

[Mark Huffman]

Thanks for the hints. I solved it somewhat similarly since we populate
some Z tables (usually I wouldn't recommend that - but in this case it
makes sense) and store the key fields of the business objects that were
passed in. These then become attributes of a custom object, so I check
if the BP & Premise attributes are initial - if so then go on to create
the objects.
 
I guess you're waiting for the next upgrade to IS Utilities as well.
 
 
Landry, Marcel wrote:
>
> Hi Mark, I'm also on 4.0B and have come accross the same 'inconsistency'.  I
> also could not make sense of this behavior.  In my scenario, I had to verify
> if a move-out document was produced earlier in the WF (as part of the
> move-in), and based on the results, take one of two paths. My plan B was to
> use a conditional branch to verify if the MoveOut container was still
> 'initial' with a simple comparison in the conditional branch such as:
> MoveOut <> "   ".  In the case where this was true, that meant that a
> moveout document was in the container, otherwise, the container was still
> empty.
>
> This has worked great so far.  Just ensure that your BP/Premise containers
> are in fact blank at the beginning of your WF and that you have not left any
> other binding in place that may inadvertantly populate these containers
> (other than from the proper source within you WF).
>
> Hope this helps.  Good luck.
>
> Marcel Lanrdy
> New Brunswick Power
> Fredericton, N.B.
> CANADA
>
> -----Original Message-----
>> From: Mark Huffman [mailto:m.r.huffman at worldnet.att.net]
> Sent: May 21, 2000 11:38 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Condition: Object Exists
>
> I am on 4.0B and tried to use the Condition logic Object EX recently.
> The workflow has a fork and the first step in each branch was to check
> if an object existed (one branch checked for business partner, the other
> branch checked for premise). The condition did not seem to operate
> consistently and due to time pressure, didn't really have a chance to
> test it out thoroughly.
>
> My expectation was that if those objects existed within the Workflow
> container (eg. in this case, they had been imported when the the WF
> started) then the conditions would be true, else false. On the first
> test with no objects passed, it reported false - ok. But on subsequent
> tests with no objects passed, both condition steps reported true. You
> can view this in the tech log.
>
> I looked at the 4.6 online doco, but that didn't really shed any light
> either for this topic.Any comments or ideas?