Currently (as of release 11.1) service webhooks only support non-hosted data (data in an enterprise geodatabase) where the data is not registered as versioned.
Working with versioned data is a central part of many workflows using either branch or classic versioned data.
Support for webhooks in these workflows would be a great improvement.
Outside of the ESRI world, stored procedures and triggers are used in the database (Oracle, SQL Server, etc.) instead of webhooks. This is a more direct solution which doesn't have to leave the database for execution.
Support for branch versioned feature services was added at ArcGIS Enterprise 11.3.
Great that service webhooks is implemented for branch versioning - but we need it for classic versioning as well @jill_es
@NielsVemmelund1, thank you for the additional information. I've moved this Idea back to "Under Consideration."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.