Survey123 Email Notification via GeoEvent Server

[klandicho]

Hi,

I would like to get some help or advice from anyone who has used Survey123 and GeoEvent Server for email notification.

One of our clients configured a Survey123 form in ArcGIS Enterprise and would like to include an email notification every time a new survey and update on an existing survey comes in. Updates on the surveys happen on the “Status” attribute and each level of Status has different sets of email receipts.

Since their ArcGIS Enterprise is not available via internet, we cannot use the webhooks (Integromat and Power Automate) for sending emails.

We used the GeoEvent Server as a workaround. For new survey updates, we have no problem because we can use Object ID to poll new survey in the input:

But we are having issues with the updates on the existing survey. The Input for the Survey Updates polls continuously even without updates on the survey. Furthermore, we want to send one (1) email per update per survey only but even if there are no updates on the surveys, an email notification is being sent to recipients. We observed that emails are sent every 5 days (April 1, April 6, and April 11).

Below are the configurations that we did for the updates on surveys:

• Updates on the surveys happen on the “Status” attribute and each level of Status has different sets of email receipts.
• Used same input for all the GeoEvent Service related to the updates on surveys.
• Created individual Output for each Status.
• Created individual GeoEvent Service for each Status.

1. Created another Input, where Get Incremental Updates is set to ‘No’. Also set Refresh Interval to ‘0’. We used this same input for all the GeoEvent Service related to the updates on surveys.

2. Configured Outputs for each Status with different sets of email recipients.

3. Created individual GeoEvent Service for each Status with Incident Detector and Field Enricher Processors and Filter. The following screenshots is based on the ‘Security’ Status. (see GeoEvent Service_Security Status screenshot).

• Added the Input for survey updates and connect it to an Incident Detector Processor. We configured Opening Condition when the Security Status is Go while the Closing Condition is the opposite of the Opening Condition.

• Configured a Filter after the Incident Detector Processor. 

• Afterward, configured a Field Enricher Processor connected to the Filter. (see Field Enricher screenshot)

• And then finally, added the appropriate Output for the Security Status.