Controlling the change trigger on a Select List (cascading)?

[Paul Konen]

I would like the control when the field type of 'select list (cascading)' triggers?

If you select the first item and click off form, it triggers and retains the value selected in the first item.

I imagine the only solution might be in the automation rule.

I would need to check if the child is Empty and just exit the rule.

But then you lose the initial values too.

Is there anything with the field type that can control when it triggers?

[Bill Sheboy · Accepted solution]

Hi @Paul Konen 

Before proceeding, would you please explain the problem you are trying to solve?  That is, "why do this?"  Knowing that may help identify other solution approaches.

Until we know that...

If I understand you question, I believe the answer is "no".

When you need the previous values (e.g., from setting the parent, exiting the field, and later setting the child), you have a couple of workaround options:

• better, more complicated: when the child value changes later, use the REST API endpoint (called with Send Web Request in an automation rule) to read the changelog entries to find the prior values, evaluating them in the rule logic
• hack: when the field changes and only the parent is set, save the prior values in a custom field or entity property; later when the child is set, use the saved value as needed

Kind regards,
Bill

[Paul Konen]

I'm calling a backend system with changes from that control.

But as soon as you click from child to parent, or off control somewhere on the form it triggers and sends off the current values.

I would like for it to only fire if both values are complete.

[Bill Sheboy]

Thanks for that information.  If one leaves the field it triggers as an update event.

When your rule only needs both current values to proceed, try using a smart value condition to check both are non-empty:

{{issue.customfield_12345.value}}

{{issue.customfield_12345.child.value}}

[Paul Konen]

Seems like the best solution.  Thanks.