Hi,
Seem to be having an issue with Business Rules not executing in the correct order. I have two Custom Processes on the same table (TASK_TEXT) one updates a record using XML, the other sends out a notification based upon this update. They both have the same execution point (Commit read or insert) and the execution sequence for the update is a lower number than the execution sequence for the notification, yet the notification goes out before the update. Any ideas please?
Thanks
+28Hi
I am not sure that the sequence actually works as expected.
You can try to give large numbers as the sequence. instead of 1,2,3…. use 1000, 2000, etc
Cheers!
+14Hi
The sequence works when the transactional property is checked in the custom process as its treated as a single action which means you might need to change the execution point (without commit action).
Hi
Another option would be to have a business rule create an event when the task text is updated, then have a notification triggered by that event. That way you should be able to trust that the first action has happened before the notification takes place.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
