[EN] USEAF364 - Flow trigger restricted to specific fields

  1. 1. In the flow editor, double-click the Start node to open the trigger settings

    In the flow editor, double-click the Start node to open the trigger settings
  2. 2. Under Start Mode you can choose Manual, Item Actions, Webhook or Timer (coming soon); here the flow already uses Item Actions, which fires from events in a category

    Under Start Mode you can choose Manual, Item Actions, Webhook or Timer (coming soon); here the flow already uses Item Actions, which fires from events in a category
  3. 3. Under Trigger Action you can choose Creation, Update or Deletion; only Update lets you restrict the trigger to specific fields

    Under Trigger Action you can choose Creation, Update or Deletion; only Update lets you restrict the trigger to specific fields
  4. 4. Scroll to Conditionals and click Add, on the Branch or, to create the condition that will restrict the trigger

    Scroll to Conditionals and click Add, on the Branch or, to create the condition that will restrict the trigger
  5. 5. In the Input Variables panel, the Changes group lists each field of the category that can be watched; here we use Name, but any listed field works

    In the Input Variables panel, the Changes group lists each field of the category that can be watched; here we use Name, but any listed field works
  6. 6. Drag the field to the Reference column: it becomes the expression {{ changes.name }}, which stands for the changed value of that field

    Drag the field to the Reference column: it becomes the expression {{ changes.name }}, which stands for the changed value of that field
  7. 7. Under Operator, choose Filled/True: this option confirms the field showed up among the changed data. Comparison operators, such as Equal =, Different != and Contains, are also available to check the value of the field

    Under Operator, choose Filled/True: this option confirms the field showed up among the changed data. Comparison operators, such as Equal =, Different != and Contains, are also available to check the value of the field
  8. 8. Even with Filled/True, the Value field requires a filled text to save the condition; use true

    Even with Filled/True, the Value field requires a filled text to save the condition; use true
  9. 9. Click Save and close to apply the condition to the node

    Click Save and close to apply the condition to the node
  10. 10. Click the save icon, in the top right corner: the red dot marks pending changes

    Click the save icon, in the top right corner: the red dot marks pending changes
  11. 11. On the Save new version screen, choose the change type: here we use New features, because the condition does not change the structure of the flow. Confirm on the button to save

    On the Save new version screen, choose the change type: here we use New features, because the condition does not change the structure of the flow. Confirm on the button to save
  12. 12. The success notice confirms the saved version, and the Start node goes back to showing OK

    The success notice confirms the saved version, and the Start node goes back to showing OK