<?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: Splunk Add-on for Service Now Madrid version in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Service-Now-Madrid-version/m-p/456499#M56197</link>
    <description>&lt;P&gt;Your company/team are bit ahead of the game it seems &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;BR /&gt;
Most of companies are in Kingston/London version, but I'm very much sure the TA would be compatible.&lt;/P&gt;

&lt;P&gt;The tests I normally do is&lt;BR /&gt;
1. Ensure the cmdb_ci hasn't changed dramatically. Adding a new column is NOT a big problem as it just leads to extra field&lt;BR /&gt;
2. If you find any increased amount of data, you can suppress them (Please &lt;A href="https://answers.splunk.com/answers/738786/splunk-servicenow-app-how-to-selectively-remove-di.html"&gt;see this post how to do that&lt;/A&gt;)&lt;BR /&gt;
3. You may need to reload the API account in some cases. But overall, no major changes may be required&lt;/P&gt;

&lt;P&gt;The only ways is to try it out in your DEV/TEST environment and point it to Madrid Version&lt;/P&gt;</description>
    <pubDate>Thu, 16 May 2019 08:15:28 GMT</pubDate>
    <dc:creator>koshyk</dc:creator>
    <dc:date>2019-05-16T08:15:28Z</dc:date>
    <item>
      <title>Splunk Add-on for Service Now Madrid version</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Service-Now-Madrid-version/m-p/456498#M56196</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I'm looking to integrate Splunk with ServiceNow in order to pull CMDB, incidents and changes information to Splunk. We're currently on Madrid version of ServiceNow and the add-on documentation states it is compatible only with Helsinki, Istanbul, Jakarta, and Kingston. I know for sure this add-on works with London (tested) but has anyone made it work with Madrid version?&lt;/P&gt;

&lt;P&gt;Best regards,&lt;BR /&gt;
Andrei&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 08:07:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Service-Now-Madrid-version/m-p/456498#M56196</guid>
      <dc:creator>raduand</dc:creator>
      <dc:date>2019-05-16T08:07:33Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for Service Now Madrid version</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Service-Now-Madrid-version/m-p/456499#M56197</link>
      <description>&lt;P&gt;Your company/team are bit ahead of the game it seems &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;BR /&gt;
Most of companies are in Kingston/London version, but I'm very much sure the TA would be compatible.&lt;/P&gt;

&lt;P&gt;The tests I normally do is&lt;BR /&gt;
1. Ensure the cmdb_ci hasn't changed dramatically. Adding a new column is NOT a big problem as it just leads to extra field&lt;BR /&gt;
2. If you find any increased amount of data, you can suppress them (Please &lt;A href="https://answers.splunk.com/answers/738786/splunk-servicenow-app-how-to-selectively-remove-di.html"&gt;see this post how to do that&lt;/A&gt;)&lt;BR /&gt;
3. You may need to reload the API account in some cases. But overall, no major changes may be required&lt;/P&gt;

&lt;P&gt;The only ways is to try it out in your DEV/TEST environment and point it to Madrid Version&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2019 08:15:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Service-Now-Madrid-version/m-p/456499#M56197</guid>
      <dc:creator>koshyk</dc:creator>
      <dc:date>2019-05-16T08:15:28Z</dc:date>
    </item>
  </channel>
</rss>

