<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Webhooks - administrative change trigger in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/webhooks-administrative-change-trigger/idi-p/935191</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Investigating and programatically handling&amp;nbsp;administrative changes to a GIS can be an awkward process. If administrative changes were able to trigger a webhook then this could be plugged into a logging mechanism or change management process. In the same way that /item/ can trigger a webhook, /portaladmin/ should as well.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The end goal of such a webhook would be the ability to write all administrative changes to a file. This record can then be used for diagnostic purposes in the event that a major outage occurs. Current mechanisms would require parsing through web server and application logs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Mar 2020 22:15:11 GMT</pubDate>
    <dc:creator>AngusHooper1</dc:creator>
    <dc:date>2020-03-17T22:15:11Z</dc:date>
    <item>
      <title>Webhooks - administrative change trigger</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/webhooks-administrative-change-trigger/idi-p/935191</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Investigating and programatically handling&amp;nbsp;administrative changes to a GIS can be an awkward process. If administrative changes were able to trigger a webhook then this could be plugged into a logging mechanism or change management process. In the same way that /item/ can trigger a webhook, /portaladmin/ should as well.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The end goal of such a webhook would be the ability to write all administrative changes to a file. This record can then be used for diagnostic purposes in the event that a major outage occurs. Current mechanisms would require parsing through web server and application logs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Mar 2020 22:15:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/webhooks-administrative-change-trigger/idi-p/935191</guid>
      <dc:creator>AngusHooper1</dc:creator>
      <dc:date>2020-03-17T22:15:11Z</dc:date>
    </item>
  </channel>
</rss>

