Latest Contributions by KevinHibma

I don't think this will work. The sending webhook from Survey123 would need to send the webhook as a form-body.  Meaning, the incoming webhook body would look like: payload = { "eventType": "addData", "feature": { "attributes": {various attributes} } } Without the body parameter, the GP Service does not have a way to capture the payload and use it. ... View more

Hi Thomas, You won't see a "RabbitMQ" process by name. It's wrapped in another process. But I wouldn't go real deep looking here. You said you're using ArcGIS Enterprise 11.1? When you check your Server debug logs, do you see any errors related to webhooks? If not, thats good. If so, can you paste them here? If you're getting errors I'd suspect you would be seeing them quite often. If no errors, within the Server administrator, can you check /server/admin/system/webhookprocessors  (you'll need to type the webhookprocessors part in, it's not a published API). If you check the config, is it populated? If not, can you restart you ArcGIS Data Store, and then your ArcGIS Server, then Portal  (the restart is just to get everything into a state where that config would have information. Note - if it is already filled in, just try restarting ArcGIS Server. Further to your question, no, there is no configuration parameter you need to set or modify to enable webhooks. The config I mention above would automatically be filled in by the system: you cannot manually update it. ... View more

That's exactly the enhancement request I'm evaluating. I need to see if its technically possible before accepting/rejecting. I hope to have that question figured out soon. If we can do it, we'll try to address in an upcoming release. ... View more

@PhilippeVDV Interesting timing. I've been working on this exact question this week. Today, you're correct, no webhook is triggered when a SAML user has been added to the group by based on group membership. Internally, different "things" are happening with the add user / authentication checks and calls when going this route compared to adding a built-in user to a group. I'm investigating if we're able to support this scenario. For now, I do not believe there are any workarounds. ... View more

@KevinWyckoff1 - For the sake of clarity, can you expand on what exactly you'd like to see streamlined or simplified? You mention webhooks and emails and difficulty configuring the webhooks. Are you looking for a way to have the webhook trigger an email? If I'm missing the ask, can you please provide more information? ... View more

I don't know the requirements that Survey 123 puts on the feature service. I do know there was an issue with getting change tracking enabled on a feature service from the item page inside the Home App. That was fixed in 11.2 I believe. The accepted solution on this thread, to use updateDefinition and ensure the correct capabilities is set might be your way to "fix" that. Unless Survey 123 has put sync on the feature service, then correct: you cannot enable the feature service webhooks. Your ExB idea - I don't know all your requirements, but from a high level this would work. Using Experience Builder to do a feature / attribute edit on a feature service, with a webhook on it, can dispatch to Power Automate and further on send a webhook.     ... View more

The Survey123 webhooks work a bit differently than the Feature Service webhooks in what payload is returned. Without looking at the actual differences, I'd guess that no, you cannot use the Fetch updates from the S123 webhook. In theory, the S123 and FS webhooks overlap:  Survey: "New Survey" = Feature Service: "FeaturesCreated". Survey:"Survey Updated" = Feature Service: FeaturesUpdated. It's just a feature service behind the Survey right? So you could probably create a FS webhook yourself on the service, listening for FeaturesUpdated, and then use the Fetch connector in Power Automate. ... View more

If you're using ArcGIS Enterprise 11.1 or newer you have access to Feature Service webhooks which will function much the same way as the Survey123 webhooks. Instead of a new survey triggering the webhook, a new feature being created would trigger the webhook.   You can use Make.com or pretty much any webhook receiver as long as your Enterprise can send information beyond your network. The biggest difference between S123 and Ent-FS webhooks is you'll need to set everything up yourself in Make. There is no out of the box connectors in Make for the Ent-FS webhooks; you'll need to use the Webhook connector in make, get the webhook URL, and then in ArcGIS Administrator directory you'll add this URL as the payload URL while making the webhook. ... View more

Something else comes to mind now that I read your upgrade path a bit closer. Just so I understand, you had 11.1 (no observed errors), then upgraded to 11.2 (now seeing errors). Are you using feature or geoprocessing webhooks? If not, I can give you the switch to disable them and it'll stop trying to recover webhooks, thus you won't see any errors. Otherwise, I think it's an issue logged recently (give this to your tech support analyst: BUG-000164209).  ... View more

The most common reason you see these errors are due to a closed port between the ArcGIS Server(s) and ArcGIS Data Store machine. Can you verify 45671 and 45672 are open? ... View more

I'll see if I can find someone on the team who can confirm the details (base64, sha256, etc). One thing - the payload body you're using, have you encoded it? Does it have any special characters or anything? ... View more

I'd turn debug logs on in the server. Perform your feature service action (add feature), and then check the logs. You should see messages specific to webhooks. Based on your explanation it sounds like you will NOT see the webhook dispatched message. But you might see errors or other log messages that could be helpful. ... View more

I don't work on Monitor webhooks, but from your description of the SHA256 X-esrihook-Signature, it sounds like it's implemented the same as other Esri webhooks (feature service for example). The answer of "how" you validate in the receiver largely depends on the receiver itself. If you're using Power Automate or Make or some commercial receiver, you'll need to investigate what methods they have available. The basic approach is to build up a string by adding:  sha256= to the calculated encoded payload body using the sha256 hash. This provides the calculated signature that you can compare to the X-esrihook-signature. The follow Python code represents how to do this. (myKey is a variable hardcoded into the script that matches the key you used in the webhook creation)   import hashlib import hmac import base64 encodeKey = str.encode(myKey) signature = 'sha256=' + base64.b64encode(hmac.new(encodeKey, payload, digestmod=hashlib.sha256).digest()).decode() if signature == xsigHash: return True else: return False   ... View more