<?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 ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388001#M47309</link>
    <description>&lt;P&gt;The answer to my question is to use &lt;CODE&gt;snowincidentstream&lt;/CODE&gt; command.  For a list of all commands, please review this documentation.  &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Commandsandscripts"&gt;https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Commandsandscripts&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;I worked with a member of our internal SNow team, and we mapped values in Splunk to custom fields in the Incident.  Then, we added the respective SNow arguments in the SPL - this left us with a lot of flexibility to add more fields than there are in the alert action UI!  I highly recommend this - here are the docs with search examples:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Usestreamingcommands"&gt;https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Usestreamingcommands&lt;/A&gt; &lt;/P&gt;

&lt;H1&gt;SplunkRules&lt;/H1&gt;</description>
    <pubDate>Thu, 10 Jan 2019 23:02:40 GMT</pubDate>
    <dc:creator>_gkollias</dc:creator>
    <dc:date>2019-01-10T23:02:40Z</dc:date>
    <item>
      <title>Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387992#M47300</link>
      <description>&lt;P&gt;Hi All!&lt;/P&gt;

&lt;P&gt;I am looking for best practices around how to update the Splunk Add-on for ServiceNow to populate custom mandatory fields in an Incident only.  To create a new parameter (e.g. &lt;CODE&gt;action.snow_incident.param.&amp;lt;custom field&amp;gt;&lt;/CODE&gt;), the most notable files to update that I can see are the following:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;snow_incident_base.py&lt;/LI&gt;
&lt;LI&gt;snow_incident_m.py&lt;/LI&gt;
&lt;LI&gt;eventgen.conf&lt;/LI&gt;
&lt;LI&gt;updating/ creating CSVs under &lt;EM&gt;/samples&lt;/EM&gt; (may not be necessary, but would update here to be consistent)&lt;/LI&gt;
&lt;LI&gt;snow_incident.html for front end interaction with workflow actions&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Are there other scripts or.conf files out there that need to be updated in order to make this successful on either the Splunk or ServiceNow side? &lt;/P&gt;

&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 19:27:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387992#M47300</guid>
      <dc:creator>_gkollias</dc:creator>
      <dc:date>2020-09-29T19:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387993#M47301</link>
      <description>&lt;P&gt;Trying to help but out of my knowledge realm. Was there no good documentation on this type of thang? Or was there a specific docs page that got you close that's worth highlighting for context?&lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 00:55:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387993#M47301</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2018-05-15T00:55:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387994#M47302</link>
      <description>&lt;P&gt;Nah, aint no thang.  This page is helpful but doesn't quite get me there with customizing:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/AddOns/latest/ServiceNow/Usecustomalertactions"&gt;http://docs.splunk.com/Documentation/AddOns/latest/ServiceNow/Usecustomalertactions&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;What I have listed above is almost there.  The behavior I see after adding to the above scripts and files is - Incidents are created, but seem to be stored behind the scenes.  What I mean by this is after I revert back to the orig scripts, all of the INC that were created using the new ones appear in Service-Now. I poked around in the Splunk App for ServiceNow, but I don't see anything that appears to need updating for populating custom fields, although I may have overlooked something. &lt;/P&gt;</description>
      <pubDate>Tue, 15 May 2018 14:10:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387994#M47302</guid>
      <dc:creator>_gkollias</dc:creator>
      <dc:date>2018-05-15T14:10:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387995#M47303</link>
      <description>&lt;P&gt;Cool. Thanks for adding that context and what helped. Lemme see what other eyes I can get on this.&lt;/P&gt;</description>
      <pubDate>Wed, 16 May 2018 15:51:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387995#M47303</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2018-05-16T15:51:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387996#M47304</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 16 May 2018 16:02:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387996#M47304</guid>
      <dc:creator>_gkollias</dc:creator>
      <dc:date>2018-05-16T16:02:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387997#M47305</link>
      <description>&lt;P&gt;Integration works as follows: when incident data hits SNOW, it is first entered into an interstitial table "Splunk Incident".&lt;BR /&gt;
Therefore to make this work you will need to adjust that table definition on the SNOW side. (This is part of the "Splunk Integration" SNOW app.&lt;BR /&gt;
Then you will need to change a few files, depending on the type of action you want to use (alert has custom UI, for example).&lt;/P&gt;

&lt;P&gt;With the above said, let me ask you this: &lt;BR /&gt;
- can you include this data in the description field?&lt;BR /&gt;
- can you set these fields using custom workflow on the SNOW side?&lt;/P&gt;</description>
      <pubDate>Wed, 16 May 2018 19:36:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387997#M47305</guid>
      <dc:creator>mreynov_splunk</dc:creator>
      <dc:date>2018-05-16T19:36:14Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387998#M47306</link>
      <description>&lt;P&gt;Hey - did you happen to hear back from anyone on this?  &lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 20:01:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387998#M47306</guid>
      <dc:creator>_gkollias</dc:creator>
      <dc:date>2018-06-19T20:01:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387999#M47307</link>
      <description>&lt;P&gt;Peek at the response from @mreynov. There's no one more qualified &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jun 2018 13:00:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/387999#M47307</guid>
      <dc:creator>sloshburch</dc:creator>
      <dc:date>2018-06-20T13:00:21Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388000#M47308</link>
      <description>&lt;P&gt;Hi!  The answer should be yes to both of your questions.  &lt;/P&gt;</description>
      <pubDate>Tue, 06 Nov 2018 16:04:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388000#M47308</guid>
      <dc:creator>_gkollias</dc:creator>
      <dc:date>2018-11-06T16:04:59Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388001#M47309</link>
      <description>&lt;P&gt;The answer to my question is to use &lt;CODE&gt;snowincidentstream&lt;/CODE&gt; command.  For a list of all commands, please review this documentation.  &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Commandsandscripts"&gt;https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Commandsandscripts&lt;/A&gt; &lt;/P&gt;

&lt;P&gt;I worked with a member of our internal SNow team, and we mapped values in Splunk to custom fields in the Incident.  Then, we added the respective SNow arguments in the SPL - this left us with a lot of flexibility to add more fields than there are in the alert action UI!  I highly recommend this - here are the docs with search examples:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Usestreamingcommands"&gt;https://docs.splunk.com/Documentation/AddOns/released/ServiceNow/Usestreamingcommands&lt;/A&gt; &lt;/P&gt;

&lt;H1&gt;SplunkRules&lt;/H1&gt;</description>
      <pubDate>Thu, 10 Jan 2019 23:02:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388001#M47309</guid>
      <dc:creator>_gkollias</dc:creator>
      <dc:date>2019-01-10T23:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Add-on for ServiceNow:  How to populate custom mandatory fields in a ServiceNow Incident?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388002#M47310</link>
      <description>&lt;P&gt;See also this answer: &lt;A href="https://answers.splunk.com/answers/736869/servicenow-how-do-set-extra-custom-fields-when-cre.html"&gt;https://answers.splunk.com/answers/736869/servicenow-how-do-set-extra-custom-fields-when-cre.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2019 00:09:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-ServiceNow-How-to-populate-custom-mandatory/m-p/388002#M47310</guid>
      <dc:creator>chrisyounger</dc:creator>
      <dc:date>2019-09-30T00:09:54Z</dc:date>
    </item>
  </channel>
</rss>

