Approval Sequence Workflow

Adriane Price

Hello,

I have setup an approval sequence workflow automation. The trigger is "when added or changed". However, I have had complaints from individuals they are receiving multiple notifications and if any of the rows are moved between sheets or cells are changed the approval sequence starts all over again.

I need to stop two things:

1 - multiple notifications going out.

2 - approval sequence starting again when rows are moved or cells are changed.

Currently our team needs to change the "SRM Validation" column to NO.

My team does not want to go in and change the column to No, is there a way to stop the approval sequence workflow automation from routing again?

Kelly Moore

Hello Adriane,

It sounds like you may need to set some conditions to your automation, if you haven't already. For instance, in the conditions section, you could include that the routine only runs if [SRM Approval] does not equal "Approval", or whatever condition best fits your circumstance. A description from you of when the automation should or shouldn't run will help the community give you a better answer. Here's an example of an approval routine with conditions (like your process, my process also has several needed approval steps throughout the overall process):

If you wish to read about Condition blocks or Automation, please see the links here or here .

Also, I'm not sure I understand your statement about 'No' in SRM validation. I think you're saying that when the team adds No to the column, it triggers the automation because the row is changed? If my understanding is correct, we will need to set the right conditions to use as a trigger.

Kelly

Kelly Moore

Hello Adriane,

It sounds like you may need to set some conditions to your automation, if you haven't already. For instance, in the conditions section, you could include that the routine only runs if [SRM Approval] does not equal "Approval", or whatever condition best fits your circumstance. A description from you of when the automation should or shouldn't run will help the community give you a better answer. Here's an example of an approval routine with conditions (like your process, my process also has several needed approval steps throughout the overall process):

If you wish to read about Condition blocks or Automation, please see the links here or here .

Also, I'm not sure I understand your statement about 'No' in SRM validation. I think you're saying that when the team adds No to the column, it triggers the automation because the row is changed? If my understanding is correct, we will need to set the right conditions to use as a trigger.

Kelly

Adriane Price

@KDM I will give your suggestion a try. Thank you!