Business Rule VS Flow Designer

[yoli1]

Hello team, I have a situation where I'm using a Business Rule and a Flow Designer that both run on the same table (sc_task). two are designed to set the assignment group based on a specific condition. However, I've observed that the Business Rule seems to override the Flow Designer, causing conflicts.

What is the best way to resolve this issue and ensure that the assignment group is set correctly without conflicts between the two.

Thanks

[Ankur Bawiskar]

@yoli1 

why to use BR and flow both to handle same thing?

Either use only BR or only flow

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@yoli1 

check this link on docs

Execution order of scripts and engines 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Sandeep Rajput]

@yoli1 I recommend you to either use a BR or a flow for setting the assignment group. As there would always be a race condition between both of them and they would override each other's value depending on the order they execute.

[yoli1]

@Sandeep Rajput @Ankur Bawiskar  @fererroroshen The BR sets the assignment group to one group if it was empty. However, the Flow Designer is attached to a catalog item that sets the assignment group to another group if it's empty. Both actions are based on the same condition, but they result in different assignments.