Ensure that specific automations happen in a specific order?

[Ben Weisman]

Hello,

   I've got a handful of automations. Each one creates a sub-task under a shared parent task. I had to split this automation up because it uses up too much of our processing time. The issue with splitting up the rules is now the sub-tasks are in a random order.

Is there a workaround? Any way to have automations run in sequential order?

[Marc - Devoteam]

Hi @Ben Weisman 

You have the option in every rule that it can be triggered by another rule.

Still this can trigger rules in a random order.

A solution can be to create a custom field that updates when a rule has run, I would use a number field.

Run you 1st rule and have an edit action that updates the field by 1, let the following rule run (trigger) based upon this field value and update the value again after the execution.

Do this again and again till all your rules ran.

[Ben Weisman]

Thanks @Marc - Devoteam 

With the 'Trigger by anothe rule' checkbox, I can not actually select the specific rule though, correct?

[Marc - Devoteam]

Hi @Ben Weisman 

Correct.

I just means the rule can be triggered by another rule, but you can't specify which rule.

[Roman Kern]

I made variables, if I need to update specific attributes in Asset object. Use conditional logic in smart value to specify the value of the attribute and then put this into the variable. Do not use {{object.{Attribute name}}} since this is only a snapshot of your object on change/created/deleted event. Same values into new variable if you need to re-use the computed value. Couldn't find any other way to update the value, without leavin the main branch

[Ben Weisman]

Thanks @Marc - Devoteam , talk me through this solution for my specific use case: 

"Run you 1st rule and have an edit action that updates the field by 1, let the following rule run (trigger) based upon this field value and update the value again after the execution."

What I need is, when the trigger happens, a new sub-task is created under the existing parent task. How will that work?

[Marc - Devoteam]

HI @Ben Weisman 

Here is an example of the first rule.

I have made a CF of the type number.

In the rule I check if the field number is empty, if so a new sub-task will be created and the number field value will be updated by 1.

The next rule to create a sub-task, is in basis the same.

The trigger will need to act upon number change, check the value of the number and action to create and edit the original issue