Configuring Unbound Actions
The framework supports configuring unbound actions in a domain similar to unbound functions. An unbound action is considered as an operation that can change the state of a service. Due to this, the framework supports calling an action with a POST request. After the unbound action is configured, it is invoked by a POST request to the URL <Domain Root>/<Domain Namespace>.<Unbound Action Name>. The body of the POST request contains the parameters that will be passed to the action.
An unbound action is configured in the import.json file in the same way as an unbound function except the following differences:
• An unbound action is specified in the actions collection property in the import.json file.
• While specifying the action in the import.json file, the property includeInServiceDocument is not applicable to actions. This is because actions cannot be included in the service document available at the domain root.
• The action names defined in the import.json file start with action_.