<?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 Dynatrace problems into ServiceNow as incident state not updating and duplicate problem is generated for closed state into problem in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-problems-into-ServiceNow-as-incident-state-not/m-p/271010#M35824</link>
    <description>&lt;P&gt;configured ServiceNow with Dynatrace for problem generation into ServiceNow but whatever the problem is closed in Dynatrace it is opening new problem in ServiceNow as the open one already exist for same id. The incident that is created into SNOW needs to update it's state as closed but the incident state is not updating - it needs to update when it is closed&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 26 Feb 2025 05:53:37 GMT</pubDate>
    <dc:creator>gauravpayghan__</dc:creator>
    <dc:date>2025-02-26T05:53:37Z</dc:date>
    <item>
      <title>Dynatrace problems into ServiceNow as incident state not updating and duplicate problem is generated for closed state into problem</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-problems-into-ServiceNow-as-incident-state-not/m-p/271010#M35824</link>
      <description>&lt;P&gt;configured ServiceNow with Dynatrace for problem generation into ServiceNow but whatever the problem is closed in Dynatrace it is opening new problem in ServiceNow as the open one already exist for same id. The incident that is created into SNOW needs to update it's state as closed but the incident state is not updating - it needs to update when it is closed&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 05:53:37 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-problems-into-ServiceNow-as-incident-state-not/m-p/271010#M35824</guid>
      <dc:creator>gauravpayghan__</dc:creator>
      <dc:date>2025-02-26T05:53:37Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace problems into ServiceNow as incident state not updating and duplicate problem is generated for closed state into pro</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-problems-into-ServiceNow-as-incident-state-not/m-p/271041#M35829</link>
      <description>&lt;P&gt;Did you try the new Service Now for workflows approach?&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/service-now" target="_blank"&gt;https://docs.dynatrace.com/docs/analyze-explore-automate/workflows/actions/service-now&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2025 10:56:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Dynatrace-problems-into-ServiceNow-as-incident-state-not/m-p/271041#M35829</guid>
      <dc:creator>PacoPorro</dc:creator>
      <dc:date>2025-02-26T10:56:21Z</dc:date>
    </item>
  </channel>
</rss>

