How to avoid the execution of BRs once its aborted in other BR which is first in sequence.

[PuluM]

I have a BR1 on the incident which  validate the field on the form on  while state changes to resolve and it throw an error if it fails and abort the action. Now there is an OOTB BR2 (caller close)on the same condition that when state changes to resolve it shows an info message as incident has approved ( for caller) but ,
when the end user tries to resolve the incident by UI action the both BRs getting executed. Even after set abort action in BR1 when it fails still it the BR2 runs and an info message is getting populated how can we avoid this info message when BR1 aborted.

@Atul5 

[Mark Manders · Accepted solution]

Why not make it one BR? When state changes to closed and triggered by caller, all is fine, if not, check for the field and abort.

[Ankur Bawiskar · Accepted solution]

@PuluM 

both the business rules will trigger if condition matches.

I agree with @Mark Manders why not merge both and discuss with customer what they exactly want

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

[Mark Manders · Accepted solution]

Why not make it one BR? When state changes to closed and triggered by caller, all is fine, if not, check for the field and abort.

[PuluM · Accepted solution]

Thanks for reply but cant we control this behavior without merging. Is there anyother approach? because if more requirements comes up related to BR we need to add all those here in the same business right? if not wrong?

[Ankur Bawiskar · Accepted solution]

@PuluM 

both the business rules will trigger if condition matches.

I agree with @Mark Manders why not merge both and discuss with customer what they exactly want

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