Change Request Legacy Workflow domain condition not honored on insert – BR vs workflow timing.

shubham007
Tera Contributor

Hi All,

I’m trying to understand the actual behavior of the “Run after business rules” option in legacy workflows, especially around condition evaluation timing.

Scenario

  • Change Request – Standard workflow

  • Workflow condition uses Domain (e.g., Domain is not XYZ)

  • Domain is set via a Before Business Rule (order < 1000) based on Assignment/Implement Group

Issue

  • At submit time, debugger shows Domain = Global initially, then the BR sets it correctly.

  • Workflow still attaches using the initial domain value, ignoring the updated one.

  • Enabling “Run after business rules” did not change this behavior.

  • Using Account-based conditions works as expected.

Questions

  1. How does “Run after business rules” actually work?

    • Does it impact only workflow execution, or also condition evaluation?

  2. Is this option deprecated or unreliable in newer releases?

  3. Given such timing issues, is it recommended to move from legacy workflows to Enhanced Flows (Flow Designer) for more reliable condition evaluation using final field values?

Looking for platform-recommended best practices.
image (6)-redacted_dot_app.pngimage (5).png
image (6)-redacted_dot_app.png

0 REPLIES 0