• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 64 subscribers
  • Views 195 views
  • Users 0 members are here
Options
Related

Workflow - Approval Rule based on VA Value

craig mcfarlane
2 months ago

Hi Team. 

I am having some issues with a workflow. I have a separate workflow that looks for all accounts in a security group and if they are due to expire in 8 days then to set a VA to TRUE. That works fine. 

Once the VA has been set to TRUE it should kick off this work flow. I am trying to get it to send an approval notification to the correct team based on a VA value. For example, there could be 10 accounts in a group 5 belonging to Infrastructure and 5 to the Service Desk teams. If the approval email goes to a different set of email addresses.  

It seems to not be firing off the approval rule when the VA is set to TRUE. However, if I change the VA to FALSE, I am prompted with a reason why. 

There are two issues. 

1) The Approval rule does not seem to be firing when the VA is set to TRUE

2) Why is the approval request firing when I have the Workflow set to only start if the VA attribute is TRUE. ? It is already TRUE, and I am changing it to FALSE. Maybe the issue is related to point 1 

So, I am building this workflow as per the screenshot below. 

I am setting a VA to start the workflow and then, in the conditions setting it to only start if the value is TRUE. 

Here I am looking for the VA Value to be Infrastucture Team, As you will see from the first screen shot, I have an Approval rule setup 

Here I am looking for the VA Value to be Service Desk, As you will see from the first screen shot, I have an Approval rule setup 

  • 0 2 months ago

    Craig,

    I think the main issue is your filter for the workflow start condition.  In your screenshot, the start conditions are configured to only start if a modify properties operation has occured to the Account expiry check VA, and only if the pre-change value = true. 

    AR is executing your previous workflow to mark the value as true, but before it does, it executes this one.   This is why it kicks off the approval when you uncheck that value which takes it from True to False, but not the other way around.

    A simple fix would be to just flip the start condition to only trigger if the changed value equals True.

    Hope this helps!