Adding additional conditions to an "if" activity

[Jason Stephens]

Hi all,

I gave up on figuring this one out a few years back and used other ways to pull it off the same functionality, but now I'm in the same boat so I would like to know what I'm doing wrong.  

I am trying to add an additional condition to an "if" activity in a workflow.   I have also modified the yes and no OOB ones, so I want:

Parking (formerly yes)

Signage (formerly no)

Both (new)

as conditions.   I have also changed the "activity.result" field for each to match:

activity.result == 'parking'

activity.result == 'signage'

activity.result == 'both'

When I run the workflow, no mater what choice I make on the item for this field (select box with parking, signage, or both as options), it always evaluates to "no".   What am I missing here?   I'm sure it's something simple, but I don't see it...

Thanks for any help!

Jason

[Masha]

I was in the same boat until I decided to add another IF (with 'yes' and 'no') to my WF and that (even if not very elegantly) solved my issue. BUT! I did find why my IF Activity with customconditions always returned 'no', as yours does. Look for IF activity definition script in the Activity Definitions module. From what I can tell at first glance If activity is explicitly looking for a true or 'yes' from the script and if it get's it it puts out a 'yes' and all other times you get a 'no'. So your options would be to alter the If activity definition (which I don't suggest for obvious reasons) or copy it/create another If activity that would meet your needs better.

I am pretty sure this is not the answer you were looking for, but I hope it helps clear some things up a bit. Good luck!

[Claudio6]

Very clever!

[himapallela87]

Hi,

Seems its not working in Eureka. But its working fine in Calgary.

Regards,

Hima Pallela

[Pradeep Sharma]

Hi Hima,

I have just tried it on demo and seems to be working fine on Eureka.

Can you ping me the demo instance on which you are doing so that I can take a look.