Details
-
Type:
Change Request
-
Status: Closed
-
Priority:
Trivial
-
Resolution: Duplicate
-
Affects Version/s: 3.4.0alpha1
-
Fix Version/s: None
-
Component/s: API (A), Frontend (F)
-
Labels:
Description
Current validation rules allow only and and or operators, but under the hood server is using the same expression evaluation engine as for trigger expressions and calculated item formulas.
I suggest to relax validation so that it allows not operator too. This will give users a complete set of logical operators to build more sophisticated expressions.
Attachments
Issue Links
- duplicates
-
ZBXNEXT-2788 Use of NOT keyword in Custom expression fields (Z4)
-
- Closed
-
- part of
-
ZBXNEXT-97 ability to test an action in frontend
-
- Open
-