I set multple actions for a single item-event. How to execute these actions in order when event is fired.
I set priority for each action, but its not working.
Second,
If i have multiple item-events set for single database field, how to fire these events in order?
Thanks
To register for the forums, please contact your Digital-Clay representative.
Execute multiple actions in sequence
-
impactconsultant
- Posts: 16
- Joined: Thu Jul 16, 2009 7:16 am
-
ZevToledano
- Posts: 722
- Joined: Fri Apr 03, 2009 2:29 pm
Re: Execute multiple actions in sequence
(There was a database restore so a couple of new posts may have gotten lost - my apologies.)
Multiple events/action are no problem and all should be running one after another. The order in which multiple events or actions are run are normally set by their priority, but due to the fact that actions can cause other events to be triggered recursively, and due to the fact that some filters you set can cause some events to be skipped, the order is not always obvious.
I suggest you temporarily switch on automation debugging (in ClayCentral settings) so you can see exactly what is running and what is being skipped and why. Check the Automatiuon log for debugging information and when you're done, don't forget to switch this off as it slows down a system.
Other things to check:
-You can also use the History feature to see what was changed in a record.
-Check your Automation log for errors on the action that isn't being run.
-If you are trying to change a field, make sure that field isn't set to readonly/hiddenvalue for the user who owns the Automation Event.
-Make sure all of your actions/events are Active.
Multiple events/action are no problem and all should be running one after another. The order in which multiple events or actions are run are normally set by their priority, but due to the fact that actions can cause other events to be triggered recursively, and due to the fact that some filters you set can cause some events to be skipped, the order is not always obvious.
I suggest you temporarily switch on automation debugging (in ClayCentral settings) so you can see exactly what is running and what is being skipped and why. Check the Automatiuon log for debugging information and when you're done, don't forget to switch this off as it slows down a system.
Other things to check:
-You can also use the History feature to see what was changed in a record.
-Check your Automation log for errors on the action that isn't being run.
-If you are trying to change a field, make sure that field isn't set to readonly/hiddenvalue for the user who owns the Automation Event.
-Make sure all of your actions/events are Active.