Fusion scenario does NOT fire on form changes if form isn't on the top of the stack | Community
Skip to main content
K
Kelly_StarzEnt
New Participant
August 27, 2024
Question

Fusion scenario does NOT fire on form changes if form isn't on the top of the stack

  • August 27, 2024
  • 2 replies
  • 644 views

I have a project that has 7 forms attached. The target form is not the top form, but say the 5 form in the stack.
I have a Fusion Scenario Watch Event (Instant/Acid) set up to trigger when a project is updated with a specific categoryId.

When I update the target form in the project, Fusion scenario does NOT fire.

When I adjust the form stack on the project and move the target form to the top of the stack and then update the form the Fusion scenario does fire.

Is this normal behavior? How can I make sure to get all form updates on any form using Fusion?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

Lawson02
Lawson02
New Participant
August 27, 2024

I created an admin only field that is a concatenation of all fields on a form. This works well as long as all fields combined would not be over 2000 characters. Make the webhook trigger be on field change. This approach limits the webhook events while also giving access to all updates within the form. I did not have to worry about the 2000 char limit so I never tried to make it more pretty.

 

The formula is just CONCAT(field1, field2, ...)

gardensurfer
gardensurfer
New Participant
August 27, 2024

Yes, unfortunately, it appears to be normal behavior in the Watch event. You would have more flexibility in modules further down to bring back all objectCategories in an array and then loop through the array for the form you're looking for, but not in the Watch event. 

 

One "hack" I've used when I have an object with multiple forms is to set an Admin-Only field on the specific form with a default value. Then in the Watch event, rather than look for just the project with that categoryID, I look specifically a project with specifically that field having the default value.

 

For example, this task may have multiple forms in any stack order, yet scenario will fire if the field has this value set to Yes (or even if the field just exists):

 

Terms & ConditionsAccessibility statement

Loading footer...