Setting the rule constraint of Ru Discount Item Custom Not Zero
to Matches All
should solve that.
WHY?
I was sitting yesterday all day until (without reading this) i changed that by mistaque and suddendly everything workedâŠ
Thanks!!!
G.
@emre, can you give some clarification between the different Rule Constraints please?
I understand these:
Matches Any:
(constraint1 is True)
OR (constraint2Â is True)
OR (constraint3Â is True)
Matches All:
(constraint1 is True)
AND (constraint2 is True)
AND (constraint3 is True)
Not Matches Any:
NOT(constraint1 is True)
OR (constraint2 is True)
OR (constraint3 is True)
)
Not Matches All:
NOT((constraint1 is True)
AND (constraint2 is True)
AND (constraint3 is True)
)
But I donât understand this one: (I never use it)
Matches:
(constraint1 is True)
??? (constraint2 is True)
??? (constraint3 is True)
Matches does a magic match
It compares constraint names and if constraint names are same they compared by OR, everything else by AND.
For example.
Customer name == Emre
Customer name == QMcKay
Date == Today
Date == Yesterday
Resolves to âŠ
(
(Customer Name == Emre) OR (Customer Name == QMcKay)
AND
(Date == Today) OR (Date == Yesterday)
)
So our sample resolves toâŠ
Automation Command Name == Discount Item Custom NOT Zero
AND
((Command Value != 0) OR (Command Value != Null))
Dear @Emre, I would like to see the Best seller, 1.000.000 pages, SambaPos manual⊠LOL!!!
THANKS!!!
G.
Nice! Good to know, and very cool magic!