Skip to main content
Writes a rule as text instead of wiring nodes: comparisons, and/or/not, arithmetic, if … then … else, date functions, and count/any/sum over lists with where. salary_amount > 40000 and not employment_terminated if input in [“sick_leave”, “child_sick_leave”] then “forfeit” else “sync” count(absences where twine_time_type = “sick_leave” and overlaps(it, period)) >= 1 a * b / 100

​
Names

  • input, a, b, c, d — whatever is wired to that port.
  • A bare name such as salary_amount — an attribute of the subject (the same record an Attribute node reads); "Custom name" in quotes for a custom property.
  • A flow assign such as employee.salary_amount — inside a flow.
  • today — the evaluation date. x @ 2026-01-01, x @ latest, x @ oldest, x @ all pick a moment of a dated attribute.

​
Configuration

  • Expression — the rule. Errors show under the field as you type.
  • Result type — optionally cast the result (a number, a date, …).

​
Tips

  • Wire nothing and read the subject directly; wire a Const or another node into a when you want a value the graph computed.
  • The result is a plain value; downstream nodes see one dated property.
  • A name the expression cannot find is an error, so a typo never passes as “no value”.

​
Ports