Which option is not a manual way to raise an exception?

The correct option reflects that setting a database trigger is not a manual way to raise an exception. When working with manual exception handling in OutSystems, the primary focus is on actions that are initiated directly within the application logic by the developer.

Options such as using user interface events, raising an exception in the flow, and using an explicit raise exception action are all direct actions taken within the OutSystems environment to handle exceptions. For example, using user interface events allows developers to respond to user actions and throw exceptions based on interactions, while raising an exception in the flow enables exceptions to be thrown as part of the logic in a screen or process. Explicit raise exception actions are straightforward and allow developers to define specific error messages or conditions for which exceptions should be raised.

In contrast, database triggers operate at the database level and are not manually invoked in the same way as the other methods mentioned. Triggers automatically execute in response to certain events occurring within the database, such as insertions or updates, without direct control from the application logic. Therefore, this makes setting a database trigger distinct from the manual exception-raising techniques that developers explicitly implement in their application flows.