<?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>topic Re: Survey 1-2-3 and Maximo in ArcGIS Survey123 Questions</title>
    <link>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852145#M23788</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been doing this for a while now using python scripts.&amp;nbsp; We are finding lots of value in the offline capabilities of Survey123 and Collector for non critical inspections and problem reports.&amp;nbsp; The geoevent server and python scripts are complex because you have to learn the Maximo REST API (doable, but complex) and it is nowhere as friendly as the enterprise REST.&amp;nbsp;&amp;nbsp;To simplify&amp;nbsp;this&amp;nbsp;My coworkers built a flow based modeler to move data between systems.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 10 Sep 2019 16:28:13 GMT</pubDate>
    <dc:creator>Milton</dc:creator>
    <dc:date>2019-09-10T16:28:13Z</dc:date>
    <item>
      <title>Survey 1-2-3 and Maximo</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852143#M23786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does there exist an integration that allows for a Survey 123 survey to fire off a Maximo work order?&amp;nbsp; Is anyone out there achieving this?&amp;nbsp; Thanks!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Oct 2017 18:17:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852143#M23786</guid>
      <dc:creator>City_of_LakelandGIS</dc:creator>
      <dc:date>2017-10-11T18:17:04Z</dc:date>
    </item>
    <item>
      <title>Re: Survey 1-2-3 and Maximo</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852144#M23787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently there isn't anything within the Survey application itself that will trigger a secondary action. &amp;nbsp;This is doable via GeoEvent Server or DB triggers using a survey tied to your enterprise geodatabase. &amp;nbsp;Having the Survey123 application support after submission actions is a feature that we are planning on in the future.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Oct 2017 20:03:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852144#M23787</guid>
      <dc:creator>JamesTedrick</dc:creator>
      <dc:date>2017-10-11T20:03:21Z</dc:date>
    </item>
    <item>
      <title>Re: Survey 1-2-3 and Maximo</title>
      <link>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852145#M23788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been doing this for a while now using python scripts.&amp;nbsp; We are finding lots of value in the offline capabilities of Survey123 and Collector for non critical inspections and problem reports.&amp;nbsp; The geoevent server and python scripts are complex because you have to learn the Maximo REST API (doable, but complex) and it is nowhere as friendly as the enterprise REST.&amp;nbsp;&amp;nbsp;To simplify&amp;nbsp;this&amp;nbsp;My coworkers built a flow based modeler to move data between systems.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Sep 2019 16:28:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-survey123-questions/survey-1-2-3-and-maximo/m-p/852145#M23788</guid>
      <dc:creator>Milton</dc:creator>
      <dc:date>2019-09-10T16:28:13Z</dc:date>
    </item>
  </channel>
</rss>

