--- title: "Syntax" slug: "syntax" tags: ["Reference", "Helix", "Sec Ops and Analytics"] updated: 2026-09-14T13:32:26Z published: 2026-09-14T13:32:26Z canonical: "docs.trellix.com/syntax" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Syntax TQL 2.0 has stricter syntax rules for directives and transforms. Directives must now be enclosed in curly braces ( { } ) and be placed after any filters and before the pipe ( | ) character that precedes transform clauses (if any). See [Directives](/network-and-platform/docs/directives-1) for details. The pipe character must be surrounded on either side by white space. For example, the following query, which would have been acceptable in previous versions of TQL: ```plaintext class=test |groupby class ``` must now be rewritten as: ```plaintext class=test | groupby class ``` Wildcards (see [Wildcards](/network-and-platform/docs/wildcards-1) ) specified before the query string searches for any term that end with the query string. For example, the following query: ```plaintext class=*.com ``` will now return results that end with `.com`. In previous versions of TQL, the same query would have searched for the exact term `.com`.