Can async business rules trigger business rules on Target Table?

[tahnalos]

We are currently using an async business rule on insert of a staging table due to circumstances of a database update from an integration.

The Staging table pushes the information obtained from the integration into our target table.  We have several other tables that are supposed to receive information from our target table and are triggered by After Business rules.  We just found out that those business rules are not triggering when the Async business rule is run.  Changing these business rules to Async business rules also does not solve this problem.

So the question is, how can we trigger a business rule to run in this scenario?

[ReginaldFawcett]

The Business Rule (BR) running Async, should have no impact on other records being updated.
There are somethings that an Async rule cannot do, for example grab a previous value.
Check the BR to make sure that the GlideRecord you are using to update the other records has an update() call on it.

If that doesn't work, can you provide an example of your code?

[tahnalos]

Is it possible that using {field_name} changes conditions in a business rule are not being detected after a async business rule triggers changes?  That's the only thing I can think of.

[ReginaldFawcett]

Yes, that is possible. Async rules run after the record has been saved to the database. So by the time the rule comes to run, nothing is changing. I would suggest changing this to an After BR.

[Ankur Bawiskar]

@tahnalos 

why would you require a business rule on import set staging table?

once record is inserted there the transform map associated with that staging table will handle the transformation.

what's the use-case here?