Registered actions
To trigger specific actions, the Deviation Processor must be aware of the available actions. Therefore, reactors need to register their provided actions with the Deviation Processor, similar to the module registration process in the web portal. For a detailed description of how to register an action, please refer to the registration section.
| The registered action previously provided by the Notification Service reactor is deprecated and has been renamed to "Deprecated: Send Notification (Notification Service)". The Deviation Processor now includes a new hard‑coded registered action that sends notifications directly to target users and groups. please refer to the API documentation. |