Improvement suggestion, Trigger, Object metadata changed

In some situations it would be good to be able to monitor all properties EXCEPT one or a few specific properties.

One use case is with HTTP Integrations where you may want to trigger on any change in metadata except the properties set as a result of the configuration.
You may want to update the source object with something from the HTTP response or just change a status to indicate that the change has been transferred to the external database.
If you configure Trigger to Object metadata changed without exceptions that would create a loop. The system gives a warning, so you can't do that anyway. But this means you have to list all the individual properties that should trigger rather than just the exception. The latter would be much easier 🙂

BR, Karl