Execution context and results

ERP.net has three stored script definitions (user business rules, calculated attributes, and managed scripts) and one freeform ExecuteScript request. The feature supplies the script's values and decides how its result is used. A script runs inside a Domain transaction; it does not acquire another entity or elevated access merely because it can use the Domain object.

Feature	Context and result
User business rule	subject is the triggering entity. The script can change data or cancel the operation.
JavaScript calculated attribute	subject is the entity being calculated; a top-level return produces the attribute value.
ExecuteScript	The request supplies source code. There is no automatic subject, declared args, or persisted parameter schema; the action returns metadata and console output.
Managed script	Read declared values from args; there is no current-entity subject. Declared output parameters and a return value are returned to the caller.

The global Domain object exposes repository access, and the global Action object exposes host helpers. The repository and helper operations run with the permissions and transaction context of the invocation.

For example, a user business rule attached to Customers can read its triggering customer:

Action.log("Processing customer " + subject.Number);

The equivalent managed script must receive a customer ID through args:

const customer = Domain.Crm.Sales.CustomersRepository.getById(args.customerId);
if (customer === null)
    throw new Error("Customer not found.");
return customer.Number;

Here, args.customerId comes from the caller's JSON arguments.customerId, which must be declared in the script's parameter schema. The return value becomes the managed action's returnValue; it does not become a calculated attribute. See the complete managed-script example for the schema, request, and response.

Shared patterns demonstrates reusable operations without assuming either global. Changes to Domain entities participate in the caller's transaction and persist only if it commits. This does not imply that every host action has the same lifetime; consult the Action reference for each helper.