5.9 1898: How many else if conditions are allowed

Rennur

Hi Support,

The rule consists of a total of 3 (if) conditions. IF (#1), Else IF (#2) and Else IF (#3).
The Else If (#3) is not being evaluated properly.

When Else If Condition in position #3.
Its evaluating NOT and stuff and in the end the rule does not execute even though Truck & Dog is IN Truck & Dog.

Evaluating:
Evaluating condition NOT(Docket_Supply.Truck_Type_Final IN 'Truck & Dog', '8 Wheeler & Dog')
Evaluated:
Condition evaluated to false: Truck & Dog NOT IN Truck & Dog

Is the NOT meant to be there?

When If Condition in position #1 or #2 - The rule executes and its all good. No NOT evaluations nothing.

Evaluating condition Docket_Supply.Truck_Type_Final IN 'Truck & Dog', '8 Wheeler & Dog'
Condition evaluated to true: Truck & Dog IN Truck & Dog
Adding action..........

Is there a restriction or a limitation on how many Else If conditions are allowed in the rule?

--------------------- RULE --------------------
If (#1)
Docket_Supply.Truck_Type_Final IN 'Truck & Dog','8 Wheeler & Dog' AND
Docket_Supply.Split_Load<>'Yes'
Then Docket_Supply.Docket_Tare=2+2
Else If (#2)
Docket_Supply.Truck_Type_Final IN 'Bogie','8 Wheeler' AND
Docket_Supply.Split_Load<>'Yes'
Then Docket_Supply.Docket_Tare=2
Else If (#3)
Docket_Supply.Truck_Type_Final IN 'Truck & Dog','8 Wheeler & Dog' AND
Docket_Supply.Split_Load='Yes'
Then
REPORT ERROR '#3 does not execute?'
----------------- LOG ---------

Cheers

tford

NOT ... IN is not supported. See #14 in appendix D of User Guide.

"Negated IN expression is not supported in queries. For example, the following expression is not supported:
FIND Event WHERE NOT(LoggedInMember IN Event.Participants)"

Rennur

I'm aware of this limitation but does it become a negated expression even though the rules do not contain NON?

hpl123

I have seen this regularly as well (NON expression being part of rule evaluation even when I´m not using NON in my rules) when going over logs and a clarification from support would be nice.

Also regarding the multiple if conditions. I sometimes have problems with this when using multiple conditions. The problems are as Rennurs points out rules not being evaluated and executed properly. The context is also sometimes acting a bit strange when using multiple if´s (if I place the exact same additional if´s in other separate rules or processes, all works).

Thanks

tford

Sorry for misinterpreting the beginning of your post. I saw NOT( ...) and jumped on it.

Rennur

No worries Tom, don't you think it's strange that the system is evaluating rules using this limitation?

Rennur

Henrik, thanks for checking. I wander if there is some bug with the 'Else If' statements.

aware_support

There appears to be a bug there. You can always use a workaround by creating several independent rules instead of one big ELSE IF statement - it is conceptually better and clearer this way, anyway.

Rennur

I have prepared a BSV.
In the mean time, I'll be revising the rules with multiple else if statements.

Cheers

chris29

Hi Rennur

Just wondering if you are still having an issue with this in V6

Thanks

Chris

Rennur

I think the issue still exists.

Support recommends to only use 2 'IF' statements per rule. 'If' and 'Else If/Else'.
If you need a rule that would require more than 2 IF statements, create separate rules.

Cheers

chris29

Thanks

Are you able to send the bsv to support again?

That will save me having to replicate it as our bsv is too big now for a standard install.

I know the solution to the fix is breaking them out into additional rules but we have 1000's of them to look at.

Chris

Rennur

I was in the same boat and had to clean up many rules that contained more than 3 IF statements.
To be honest, I can't remember what BSV I emailed to support about this. It was a while ago.

I suggest you re-visit your rules and separate them just to be safe.

chris29

That's ok, I'll see what I can do.

Currently to sort out the rules will take us weeks of work, so having it fixed is a better option for us.

I'll let you know how it goes.