<?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: PTC Technical Support and eAlert emails in PTC eSupport Help Discussions</title>
    <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108200#M932</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Me too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Nov 2015 15:37:21 GMT</pubDate>
    <dc:creator>Marco_Tosin</dc:creator>
    <dc:date>2015-11-11T15:37:21Z</dc:date>
    <item>
      <title>PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108199#M931</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In the last week or two, the format has changed for the WORST. Each software used to be broken into builds like we subscribe to, Creo Parameteric listed Creo 2 in one section followed by Creo 3 in the next section under Creo Parametric.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now they all fall under on section called Creo Parametric and are all mixed together. It is this way for each subject. Now I have to hunt and pick for Creo 3 Parametric issues.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Has everyone else seen this regression?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Nov 2018 17:39:54 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108199#M931</guid>
      <dc:creator>llie</dc:creator>
      <dc:date>2018-11-27T17:39:54Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108200#M932</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Me too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Nov 2015 15:37:21 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108200#M932</guid>
      <dc:creator>Marco_Tosin</dc:creator>
      <dc:date>2015-11-11T15:37:21Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108201#M933</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good day Lance,&lt;/P&gt;&lt;P&gt;Thank you for letting us know and I will be looking into the matter further.&lt;/P&gt;&lt;P&gt;I may not have an update until next week, but will post the findings when I have them.&lt;/P&gt;&lt;P&gt;Best,&lt;/P&gt;&lt;P&gt;Toby&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Nov 2015 14:24:53 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108201#M933</guid>
      <dc:creator>Tmetcalf</dc:creator>
      <dc:date>2015-11-12T14:24:53Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108202#M934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It started with the emails last Friday 11/6. The email on Thursday 11/5 was broken down by version still.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Nov 2015 15:11:37 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108202#M934</guid>
      <dc:creator>BenLoosli</dc:creator>
      <dc:date>2015-11-12T15:11:37Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108203#M935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.ptc.com/u1/38768"&gt;Lance Lie&lt;/A&gt;, &lt;A href="https://community.ptc.com/u1/292586"&gt;Mar Gru&lt;/A&gt;‌, &lt;A href="https://community.ptc.com/u1/111899"&gt;Ben Loosli&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We've found the root cause of the problem and are now working on a fix. We have 2 possible approaches to display the information and I am interested in your input.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let's say we have 3 articles&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Article 1 which applies to Creo 2.0 and Creo 3.0&lt;/LI&gt;&lt;LI&gt;Article 2 which applies only to Creo 2.0&lt;/LI&gt;&lt;LI&gt;Article 3 which applies only to Creo 3.0&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We basically have 2 ways to structure the notification email, both with pros and cons&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="text-decoration: underline;"&gt;Option 1&lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;We break down the list by Product/Version (based on what you subscribed to) : 1 section for Creo 3.0 and 1 section for Creo 2.0&lt;/LI&gt;&lt;LI&gt;Under each section, you'll see all the articles applying to this product/release with the caveat that a given article could apply to 2 sections. As a consequence, the email might be longer and some articles might appear several times in different sections&lt;/LI&gt;&lt;LI&gt;For instance in our case&lt;UL&gt;&lt;LI&gt;Creo 2.0&lt;UL&gt;&lt;LI&gt;Article 1&lt;/LI&gt;&lt;LI&gt;Article 2&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Creo 3.0&lt;UL&gt;&lt;LI&gt;Article 1&lt;/LI&gt;&lt;LI&gt;Article 3&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="text-decoration: underline;"&gt;Option 2&lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;We just have 1 list per Product and add a column to the list which shows to which release the article applies to&lt;/LI&gt;&lt;LI&gt;It would produce a more condensed email, but would prevent you to have a "release" break down of the list of articles&lt;/LI&gt;&lt;LI&gt;For instance in our case&lt;UL&gt;&lt;LI&gt;Creo&lt;UL&gt;&lt;LI&gt;Article 1 -- Creo 2.0 to 3.0&lt;/LI&gt;&lt;LI&gt;Article 2 -- Creo 2.0&lt;/LI&gt;&lt;LI&gt;Article 3 -- Creo 3.0&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you have a preference ? Which one would be the most convenient for you guys ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 13:56:19 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108203#M935</guid>
      <dc:creator>Pierre_M</dc:creator>
      <dc:date>2015-11-16T13:56:19Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108204#M936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've been following this but haven't been in the discussion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the standpoint of one who uses multiple versions concurrently, depending on the client, I'd prefer option #2. That will allow me to scan for issues that are important to me then check to see if they effect the version I'm currently using.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either one is an improvement over what is happening now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 14:07:43 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108204#M936</guid>
      <dc:creator>dgschaefer</dc:creator>
      <dc:date>2015-11-16T14:07:43Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108205#M937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree with Doug.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 14:15:59 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108205#M937</guid>
      <dc:creator>Marco_Tosin</dc:creator>
      <dc:date>2015-11-16T14:15:59Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108206#M938</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I deal more with Windchill so I prefer Option 1. Seldom do Windchill articles cross multiple releases or if they do, it will hit every release out there.&lt;/P&gt;&lt;P&gt;From a Creo side, I only support 1 production version at a time, so Option 1 is ideal for me to see only those articles for Creo2 right now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But if the majority prefer Option 2, go with what the majority want. (Right now it is Option2-2, Option1-1).&lt;IMG src="https://community.ptc.com/legacyfs/online/emoticons/wink.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 14:54:57 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108206#M938</guid>
      <dc:creator>BenLoosli</dc:creator>
      <dc:date>2015-11-16T14:54:57Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108207#M939</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I like option 1. If it is not broke, then don't fix it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It was great the way it was especially if you only follow one release like Creo 3.0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Lance&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 16:34:16 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108207#M939</guid>
      <dc:creator>llie</dc:creator>
      <dc:date>2015-11-16T16:34:16Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108208#M940</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.ptc.com/u1/2619"&gt;Pierre Maraninchi&lt;/A&gt;‌,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know it's slightly off topic, but PLEASE, PLEASE, PLEASE fix the article "Types".&amp;nbsp; Almost every article shows up as "New" even though most of them are not new, they have simply been updated.&amp;nbsp; It's very frustrating to read an article thinking it is new when I've actually read it a half a dozen times before (and can't even tell what's changed in the "new" release.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See &lt;A href="https://community.ptc.com/message/411997"&gt;Re: Windchill 10.3 (X-26)&lt;/A&gt; for a previous discussion about this problem.&amp;nbsp; Back in July &lt;A href="https://community.ptc.com/u1/11633"&gt;Heidi Khetani&lt;/A&gt;‌ said you were waiting for a vendor to fix this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 16:46:46 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108208#M940</guid>
      <dc:creator>TomU</dc:creator>
      <dc:date>2015-11-16T16:46:46Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108209#M941</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I &lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;strongly&lt;/STRONG&gt;&lt;/SPAN&gt; agree with Tom.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 16:48:39 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108209#M941</guid>
      <dc:creator>Marco_Tosin</dc:creator>
      <dc:date>2015-11-16T16:48:39Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108210#M942</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is still on the top of our list. We had confirmation from vendor a couple of weeks ago that a fix had been postponed to later on in 2016. We are now working on a home made workaround. &lt;A href="https://community.ptc.com/u1/11633"&gt;Heidi Khetani&lt;/A&gt;‌ will keep you posted as soon as we have some visibility on target dates.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 17:53:48 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108210#M942</guid>
      <dc:creator>Pierre_M</dc:creator>
      <dc:date>2015-11-16T17:53:48Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108211#M943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Lance,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;just to clarify the options, if a user only subscribed to 1 release, only articles relevant to that release will be displayed in the email. In our case, if user only subscribed to Creo 3.0, it will look like this&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN style="text-decoration: underline;"&gt;Option 1&lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;Creo 3.0&lt;UL&gt;&lt;LI&gt;Article 1&lt;/LI&gt;&lt;LI&gt;Article 3&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="text-decoration: underline;"&gt;Option 2&lt;/SPAN&gt;&lt;UL&gt;&lt;LI&gt;Creo&lt;UL&gt;&lt;LI&gt;Article 1 -- Creo 2.0 to Creo 3.0&lt;/LI&gt;&lt;LI&gt;Article 3 -- Creo 3.0&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Nov 2015 18:01:03 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108211#M943</guid>
      <dc:creator>Pierre_M</dc:creator>
      <dc:date>2015-11-16T18:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108212#M944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Good news, Option #2 has been implemented today! Work on "created date" is still ongoing though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Nov 2015 14:21:40 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108212#M944</guid>
      <dc:creator>Pierre_M</dc:creator>
      <dc:date>2015-11-26T14:21:40Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108213#M945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is the new layout.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Support.PNG" class="jive-image image-1" src="https://community.ptc.com/legacyfs/online/95433_Support.PNG" style="height: auto;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Nov 2015 07:49:05 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108213#M945</guid>
      <dc:creator>Marco_Tosin</dc:creator>
      <dc:date>2015-11-27T07:49:05Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108214#M946</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.ptc.com/u1/2619"&gt;Pierre Maraninchi&lt;/A&gt; and &lt;A href="https://community.ptc.com/u1/11633"&gt;Heidi Khetani&lt;/A&gt;‌,&amp;nbsp; I've noticed that the knowledge base articles are now showing their original creation dates.&amp;nbsp; Yay!&amp;nbsp; &lt;IMG src="https://community.ptc.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-1" src="https://community.ptc.com/legacyfs/online/102861_pastedImage_0.png" style="max-height: 900px; max-width: 1200px;" /&gt;&lt;/P&gt;&lt;P&gt;One problem though... the email updates are still calling the updated articles "New" when they clearly are not.&lt;/P&gt;&lt;P&gt;&lt;IMG class="jive-image image-2" src="https://community.ptc.com/legacyfs/online/102862_pastedImage_2.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jun 2016 16:11:35 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108214#M946</guid>
      <dc:creator>TomU</dc:creator>
      <dc:date>2016-06-14T16:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: PTC Technical Support and eAlert emails</title>
      <link>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108215#M947</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you are correct. There is only a partial fix here, that's why we did not make an official announcement. We are still working on a fix for the email notifications&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jun 2016 08:30:36 GMT</pubDate>
      <guid>https://community.ptc.com/t5/PTC-eSupport-Help-Discussions/PTC-Technical-Support-and-eAlert-emails/m-p/108215#M947</guid>
      <dc:creator>Pierre_M</dc:creator>
      <dc:date>2016-06-15T08:30:36Z</dc:date>
    </item>
  </channel>
</rss>

