<?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: ​Can I forward a browser link to a Problem in the integration between ServiceNow and Dynatrace? in Automations</title>
    <link>https://community.dynatrace.com/t5/Automations/Can-I-forward-a-browser-link-to-a-Problem-in-the-integration/m-p/117548#M956</link>
    <description>&lt;P&gt;Hello Praveen,&lt;/P&gt;
&lt;P&gt;I don't think there is a way to add a dynamic link to the problem notification but I do have some suggestions on what you could try instead.&lt;/P&gt;
&lt;P data-unlink="true"&gt;The URL for the specific problem includes the full problem ID so you might be able to put a note in your notification that the problem could be found in Dynatrace at the following link: https://&amp;lt;environmentID&amp;gt;.live.dynatrace.com/#problems/problemdetails;pid=&amp;lt;problemID&amp;gt;;gf=all&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another thing you could do is attach the tags for the entities with the problems to the notification (this is a built-in feature). This would allow users to filter the problems by the tags before searching for the specific number and would avoid them having to create the link manually as suggested above.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;BR /&gt;David Nicholls&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 29 May 2023 12:30:00 GMT</pubDate>
    <dc:creator>david_n</dc:creator>
    <dc:date>2023-05-29T12:30:00Z</dc:date>
    <item>
      <title>​Can I forward a browser link to a Problem in the integration between ServiceNow and Dynatrace?</title>
      <link>https://community.dynatrace.com/t5/Automations/Can-I-forward-a-browser-link-to-a-Problem-in-the-integration/m-p/117547#M955</link>
      <description>&lt;P&gt;Can I forward a browser link to a Problem in the integration between ServiceNow and Dynatrace? Since the ProblemID  that is passed is the entire problem identifier, it may be difficult for our end-users to find the corresponding problem if  they don't know to search on the last three digits.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 29 Apr 2019 14:11:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Can-I-forward-a-browser-link-to-a-Problem-in-the-integration/m-p/117547#M955</guid>
      <dc:creator>praveen12579</dc:creator>
      <dc:date>2019-04-29T14:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: ​Can I forward a browser link to a Problem in the integration between ServiceNow and Dynatrace?</title>
      <link>https://community.dynatrace.com/t5/Automations/Can-I-forward-a-browser-link-to-a-Problem-in-the-integration/m-p/117548#M956</link>
      <description>&lt;P&gt;Hello Praveen,&lt;/P&gt;
&lt;P&gt;I don't think there is a way to add a dynamic link to the problem notification but I do have some suggestions on what you could try instead.&lt;/P&gt;
&lt;P data-unlink="true"&gt;The URL for the specific problem includes the full problem ID so you might be able to put a note in your notification that the problem could be found in Dynatrace at the following link: https://&amp;lt;environmentID&amp;gt;.live.dynatrace.com/#problems/problemdetails;pid=&amp;lt;problemID&amp;gt;;gf=all&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Another thing you could do is attach the tags for the entities with the problems to the notification (this is a built-in feature). This would allow users to filter the problems by the tags before searching for the specific number and would avoid them having to create the link manually as suggested above.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;BR /&gt;David Nicholls&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 29 May 2023 12:30:00 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Automations/Can-I-forward-a-browser-link-to-a-Problem-in-the-integration/m-p/117548#M956</guid>
      <dc:creator>david_n</dc:creator>
      <dc:date>2023-05-29T12:30:00Z</dc:date>
    </item>
  </channel>
</rss>

