Condition Expressions

[Krishna K Kammaje]

Hi Rick,

I also thought the same. But it was giving inconsistent behavior. I mean 
in some cases, even though it was X, it was treating it as blank.
Now changed it to '=X' and it is consistent now (at least in development).

It is a virtual attribute getting passed from the event. Do not know if it 
has any bearing.

Thanks
Krishna Kishor Kammaje 





From:   Rick Bakker <rbakker at gmail.com>
To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
Date:   17/02/2011 13:55
Subject:        Re: Condition Expressions
Sent by:        sap-wug-bounces at mit.edu



Hello,

If it really can only be 'X' or blank then there is no difference.
I would use the second one to be more flexible, though.

regards
Rick Bakker
hanabi technology

On Thu, Feb 17, 2011 at 5:49 PM, Krishna K Kammaje <kkammaje at in.ibm.com> 
wrote:
> Hi,
>
> I am using following expressions for a condition step. (Assume that
> &NOTIFICATION.APPROVALREQFLAG& can either be 'X' or blank)
>
> Please let me know the difference between following two expressions in 
this
> case.
>
> 1. &NOTIFICATION.APPROVALREQFLAG& EX
>
> 2. &NOTIFICATION.APPROVALREQFLAG& = 'X'
>
> Thanks
> Krishna Kishor Kammaje
> SAP Certified Development Associate - ABAP with Netweaver 7.0
> IBM India
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

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