Configuring Bound Actions
The framework supports configuring actions that are bound to entities. An action bound to an entity is invoked on an instance of the entity. OData protocol considers a bound action to be an operation that changes the state of an entity instance on which it is invoked. After the bound action is configured, it is invoked by a POST request to the URL:
<Domain Root>/<Entity Set>(<key>)/<Domain Namespace>.<Bound Action Name>
The body of the POST request contains the parameters that must be passed to the action.
A bound action is configured in the same way as an unbound action except the following differences:
• A bound action is specified in the actions collection property in the <Entity JSON> file.
• While specifying the action in the <Entity JSON> file, the property includeInServiceDocument is not applicable to bound actions. This is because bound actions cannot be included in the service document available at the domain root.
• The first parameter in the action specification is called the binding parameter. The parameter must be of the same type as the entity that is bound to the action.
• The action names defined in the import.js start with action_.