In an Async Business Rule, which operation cannot be included if the table is in a different scope?

In an Async Business Rule, the operation that cannot be included if the table is in a different scope is the query operation. Async Business Rules are designed to run asynchronously after a record has been inserted, updated, or deleted. However, querying data from a different scope introduces complexity and security concerns in ServiceNow, which prevents such operations in Async Business Rules.

When a Business Rule operates, it needs to abide by the scoping rules in ServiceNow. Each application can have its own scope, and cross-scope access is generally restricted unless explicitly allowed. Allowing a query operation across scopes could lead to data integrity issues, and potential exposure of sensitive information, making it crucial to restrict such actions.

Insert, update, and delete operations can generally be performed across scopes, provided the appropriate permissions and security measures are in place, allowing for creation and modifications of records as needed. In contrast, querying another table that resides in a different scope is limited to safeguard the environment and maintain consistency among the applications.