Automating card updates with triggers

Summary: Add an update trigger to a card field so LYNX-X fills in other fields automatically when that field changes, for example by assigning the current user when a card is moved into progress.

Applies to

Property	Value
Product	LYNX-X
Version	28.10.9846.0
Required permissions	Space administrator (access to Configuration)
Last updated	2026-10-08
Owner	Support

Before you start

Identify the field whose change should start the automation. On a TameFlow board this is usually the stream's controlling property, Status.
Identify the field the trigger should write to, and note its key. Keys are shown in the Custom fields editor.

Important
A trigger is attached to a property, not to a card type. Every card type that uses the property inherits the trigger.

Procedure

Select Go to configuration, then under Object Configuration select Custom fields.

Configuration, Object Configuration group

The Custom fields editor opens. 2. Set Object type to Card custom fields. The grid lists the card properties in the space with their Key, Name, Unit of measure, ReadOnly, Required and Trigger. The Trigger column shows None until a trigger is defined.

Custom fields editor, card properties

Select the Trigger cell of the property you want to react to. The Update trigger dialog opens and names the property it applies to.

The Update trigger dialog

Enter the expression in Trigger. For example, to assign the current user when a card moves into Development:

if(Status=='Development',User=Currentuser('User'))

Status is the key of the Status property, and User is the key of Assignee, the property the value is written to. Substitute the keys from your own space. The Key column in the Custom fields editor shows them.

The pattern is if(<condition>,<field>=<value>). The condition tests the property the trigger is attached to; the assignment writes to another field on the same card.

Select OK to close the Update trigger dialog.
Select OK to save the Custom fields editor.

Expected outcome

The Trigger column shows the expression instead of None.

Open Focus > Tameflow and drag a card into the column that matches the condition. LYNX-X writes the new value into the controlling property, the trigger fires, and the target field is filled in. Select the card to confirm the change in the details panel on the right.

Additional information

Note
String comparisons must match the stored value exactly, including capitalisation. 'In progress' and 'In Progress' are different values. Check the exact wording in the Property value column of the Board configuration tab. That column shows the stored value, while Caption shows only what is displayed.

Tip
Use the field key rather than the display name in expressions. Display names can be changed by anyone with configuration access; keys cannot.

Warning
A trigger overwrites the target field every time the condition is met. Do not point a trigger at a field users maintain by hand, because their entry will be replaced the next time the card moves.

Troubleshooting

Problem	Resolution
The trigger never fires.	Check the comparison value against the Property value column on the Board configuration tab. A capitalisation difference is the most common cause.
The trigger fires on card types it should not.	Triggers apply to every card type that uses the property. Use a separate property if you need different behaviour per card type.

Revision history

Version	Date	Author	Changes
2.0	2026-07-29	Support	Rewritten for LYNX-X. Triggers moved from the TameFlow set-up screen to Configuration > Custom fields.
2.1	2026-10-08	Support	Screenshots updated to the current look. The route now starts under Object Configuration, and the Trigger cell opens with a single click.

Articles in this section