Reducing Automation triggers when Objects are updated

[Brock Jolet]

I've been diving into Assets for JSM. Naturally, I want to be able to automate the data in these assets, but I'm growing frustrated at the lack of support for Objects in Automation.

I have a simple idea for a rule:

• When an object is updated
• Check if an attribute is empty or wrong
• If so, update it

It's working, but I'm running into a scope issue. I can only check at the Schema level if something has been updated. I want to check at the Attribute level. I want to know if a specific user field attribute has changed (ProjLead), but the way it is currently configured, if any attribute changes on any of the objects in the schema, my rule will trigger. With the Automation limit changes from last year, I'm hyper-aware of rules that run frequently.

How can I refine my rule to only run when a specific attribute is updated? This should be similar to the "Field value changed" trigger.

[Rebekka Heilmann (viadee)]

Hi @Brock Jolet 

I can't say how to change the trigger but here's some info on how Rule executions are measured: 

• Rules which don't execute an Action will not be counted towards the limit. When the Conditions in your rule aren't met, it won't count.
• Log Actions (Automation Log) don't count as "Action".

Therefore, if your conditions work as you'd expect, there wouldn't be an issue with rule executions either way.

[Brock Jolet]

Thank you for your reply. Unfortunately, it seems that doing an AQL Lookup does count as an action. So if I do an AQL Lookup and log the results, that counts against my executions.