How To Trigger A Scenario When A Custom Form Is Updated

[Eric_D_Miller]

Hello,

I am trying to run a scenario to update the certain fields any time a certain selection of fields on a custom form are updated.

At the end of the day a trigger based on any change on the custom form would suffice. My goal is to avoid running a scenario based on anytime a project is updated as that would amount to quite a lot of unnecessary Fusion operations. I need to base the trigger on updates to just a specific custom form and/or fields.

I am aware of how to trigger based on just one specific field change, but I am not sure how to build the trigger to allow for multiple fields changing. Does anyone know how to base a trigger off of a custom form being updated?

Any help would be greatly appreciated,

-Eric

[Rafal_Bainie]

I would say that creating such a generic trigger has to be paired with specific object type. So assuming your custom form is specific to some object type you could try something like this:

this would react to any update on the task with this custom form, it can be native, it can be custom field.

Hope this helps

[Eric_D_Miller]

Is there a way to ignore the native updates and only focus on the custom form updates? The idea is to cut down on operations.

Thank you.

[Rafal_Bainie]

you can check with support if there is some general way of distinguishing custom from native fields.

It's more a guess, but in a second step after watch events module you could build a filter that would "ignore" native fields. e.g.

logic here would be, only proceed if assignedTo hasn't changed, description hasn't change etc. for all native fields. 
What would be left are changes on custom fields.
But this is more a guess I'm not 100% sure if this would work

[Doug_Den_Hoed__AtAppStore]

Hi @Eric_D_Miller,

I invite you to consider this Targeted Auditing technique, which you could use to record changes to a custom parameter without needing Fusion (so, no operations). 

If there is more to then be done in Fusion, perhaps you could adapt the triggered calculation in a way (eg special "needs Fusion attention as of yyyy-mm-dd" prefix) that Fusion can then isolate to minimize operations.

Regards,

Doug

[Eric_D_Miller · Accepted solution]

To anyone coming here for what ended up being a solution for me:

I ended up creating a calculated field with all of the (important) fields concatenated into one. That way anytime those fields (and only those fields) change the calculated field will also change. This allows me to program my trigger to point only at my calculated field vs multiple fields on my custom form.

Happy to clarify if anyone needs, just reply here

Thanks!

[Lawson02]

This is what I did as well. Be aware of the 2000 character limit per field.