Skip to main content

Hi,

Hopefully there is a simple solution for this, which I just cannot see anymore. I have been building a pair of workflows to process our Service Requests automatically, but it seems that events with Approval change trigger doesn’t get triggered at all. 

I have tried different methods and checked that there is only one workflow which is watching this Approval change as trigger. I’ve also created a test workflow with only two steps (below) but this didn’t help either.

I have tried to remove every other change and action after the Approval Request has been made as I found some information about the bug in this trigger, but that didn’t solve my issue.

This should trigger if the Approval Status is changed from Requested to Approved:
 


But I can see from the Request Activities that even this simple thing doesn’t trigger as that Note should have been added into the request ticket.  (I manually closed the request as it was a test)

 


This is how approval change is requested on the Approval workflow:

 

Part of FI IAM - STEP 1 Approval Process


This goes through as expected. I have tried to add Debug “Add Note” to every action node, and those are working as expected. And as you can see from the Action log, this workflow ends normally. 


To confirm that Step 1 exists normally and events happening after that normally, I have also an another workflow which will be triggered, if this this STEP 1 writes “Automatically Approved” into the ticket, but I cannot use that on Manual Approvements and it is not using the Approval Change as the trigger but watching other activities and using wait-node. 

 

If you have anything after the Approval node the event is consumed. 
So if you have any other WFA with the event Any to approve will not trigger. 
You need the approval node to be last node. 

If you have anything after the Approval node the event is consumed. 
So if you have any other WFA with the event Any to approve will not trigger. 
You need the approval node to be last node. 

Hi Daniel,

Thank you for your reply. I tried to remove everything the Approval Request mail (I hade Add Note and the actual Approval Node with a notification mail to the user. Sadly that didn’t solve the issue. I have a support call schduled for today - hopefully we can find some reason for this behaviour.

 

If you have anything after the Approval node the event is consumed. 
So if you have any other WFA with the event Any to approve will not trigger. 
You need the approval node to be last node. 

Hi Daniel,

Thank you for your reply. I tried to remove everything the Approval Request mail (I hade Add Note and the actual Approval Node with a notification mail to the user. Sadly that didn’t solve the issue. I have a support call schduled for today - hopefully we can find some reason for this behaviour.

 

It should, remove the action nodes for reject and approval.  If you have anything there the event will be consumed. 
Then you can have a another WFA running on the approved event. 

If you have anything after the Approval node the event is consumed. 
So if you have any other WFA with the event Any to approve will not trigger. 
You need the approval node to be last node. 

Hi Daniel,

Thank you for your reply. I tried to remove everything the Approval Request mail (I hade Add Note and the actual Approval Node with a notification mail to the user. Sadly that didn’t solve the issue. I have a support call schduled for today - hopefully we can find some reason for this behaviour.

 

It should, remove the action nodes for reject and approval.  If you have anything there the event will be consumed. 
Then you can have a another WFA running on the approved event. 

Oh… That one also. 

Well that fixed it. That is… Now it works, but that is just incredibly unintuitive. I kind of understand why it happens now, but I still consider this more of a usability challenge than a feature. Anyway, it works now, and I can avoid it in the future.

Thank you!

Setting up an event-based workflow triggered by approval status changes (from 'any/required' to 'approved') is a great way to automate processes and ensure timely actions. It's perfect for streamlining workflows. For more insights, check out Vivetool for additional tools!

If you have anything after the Approval node the event is consumed. 
So if you have any other WFA with the event Any to approve will not trigger. 
You need the approval node to be last node. 

Hi Daniel,

Thank you for your reply. I tried to remove everything the Approval Request mail (I hade Add Note and the actual Approval Node with a notification mail to the user. Sadly that didn’t solve the issue. I have a support call schduled for today - hopefully we can find some reason for this behaviour.

 

It should, remove the action nodes for reject and approval.  If you have anything there the event will be consumed. 
Then you can have a another WFA running on the approved event. 

Oh… That one also. 

Well that fixed it. That is… Now it works, but that is just incredibly unintuitive. I kind of understand why it happens now, but I still consider this more of a usability challenge than a feature. Anyway, it works now, and I can avoid it in the future.

Thank you!

I hope this will be fixed with new Approval function. Will see what they do.  

Reply


Terms of Use