# Correct precondition syntax for presets in 1.2.0+

**URL:** <https://forum.genieacs.com/t/correct-precondition-syntax-for-presets-in-1-2-0/314>\
**Category:** Uncategorized\
**Created:** [September 26, 2019, 7:53pm UTC](https://forum.genieacs.com/t/correct-precondition-syntax-for-presets-in-1-2-0/314 "2019-09-26T19:53:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![zaidka](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.genieacs.com/zaidka/32/9_2.png) [@zaidka](https://forum.genieacs.com/u/zaidka)\
**Post date:** [September 27, 2019, 8:58pm UTC](https://forum.genieacs.com/t/correct-precondition-syntax-for-presets-in-1-2-0/314/2 "2019-09-27T20:58:39Z")

</div>

v1.2 uses a new expression format. It’s used in filters/preconditions as well as other areas that require dynamic values such as the various configuration options. The format is modeled after the SQL WHERE clause. To filter on tag:

```
Tags.mytag IS NOT NULL

```

Hope that helps. I will document this format soon before the final release.

---

_[View the full topic](https://forum.genieacs.com/t/correct-precondition-syntax-for-presets-in-1-2-0/314)._