<?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 Prevent editing of CAD files with wrong version of CAD tool in Windchill</title>
    <link>https://community.ptc.com/t5/Windchill/Prevent-editing-of-CAD-files-with-wrong-version-of-CAD-tool/m-p/3223#M378</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;On 03/27/12 04:42, Darren Storey wrote:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; With Windchill we use 4 different CAD systems and concurrently multiple &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; versions of each of system. This brings us some risk, whereby users &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; inadvertently iterate CAD Docs using the wrong version of a CAD tool. For &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; example, a set of data which must be ProE WF4 should never be edited with WF5, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; because the end recipients of the data use only WF4. Of course once a model is &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; edited in WF5 it can no longer be opened in WF4.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; Does anybody else experience this problem? We looking for a way to mark a &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; selection of data (perhaps by folder contents) and force people to use a &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; particular version of the CAD tool, or at least warn them when they are about &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; to use the wrong CAD version.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; The CAD tool version previously used is stored in CAD Doc object, however it &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; is not displayed in the UI by default and the information is not in a format &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; that is easily recognizable by users.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; Regards Darren&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Perhaps something could be done with a jlink listener:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; 1. jlink listens for opening a model&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; 2. the jlink app then gets the current running Pro/Engineer version and&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    buildcode (this part is easy)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; 3. the jlink app then reads the first line of the modelfile and parses the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    Pro/Engineer version&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;      * reading the first line of the modelfile and parsing for the Pro/Engineer&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;        version would be fairly straight forward&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;      * figuring out how to find out which file in the OS to read since this is&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;        coming from a workspace would be difficult&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;      * maybe there is some jlink method that returns the version of&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;        Pro/Engineer that last edited the file&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; 4. jlink then compares the current running version of Pro/Engineer with the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    version that edited the file and pops up a warning dialog if the current&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    version of Pro/Engineer is newer&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-- &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;------------------------------------------------------------------------&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Randy Jones&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Systems Administrator&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Great Plains Mfg., Inc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1525 E North St&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PO Box 5060&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Salina, KS USA 67401&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;email: -&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Phone: 785-823-3276&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;   Fax: 785-667-2695&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;------------------------------------------------------------------------&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Oct 2017 19:59:28 GMT</pubDate>
    <dc:creator>RandyJones</dc:creator>
    <dc:date>2017-10-26T19:59:28Z</dc:date>
    <item>
      <title>Prevent editing of CAD files with wrong version of CAD tool</title>
      <link>https://community.ptc.com/t5/Windchill/Prevent-editing-of-CAD-files-with-wrong-version-of-CAD-tool/m-p/3222#M377</link>
      <description>With Windchill we use 4 different CAD systems and concurrently multiple versions of each of system. This brings us some risk, whereby users inadvertently iterate CAD Docs using the wrong version of a CAD tool. For example, a set of data which must be ProE WF4 should never be edited</description>
      <pubDate>Wed, 02 May 2018 15:47:34 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Prevent-editing-of-CAD-files-with-wrong-version-of-CAD-tool/m-p/3222#M377</guid>
      <dc:creator>DarrenStorey</dc:creator>
      <dc:date>2018-05-02T15:47:34Z</dc:date>
    </item>
    <item>
      <title>Prevent editing of CAD files with wrong version of CAD tool</title>
      <link>https://community.ptc.com/t5/Windchill/Prevent-editing-of-CAD-files-with-wrong-version-of-CAD-tool/m-p/3223#M378</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;On 03/27/12 04:42, Darren Storey wrote:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; With Windchill we use 4 different CAD systems and concurrently multiple &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; versions of each of system. This brings us some risk, whereby users &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; inadvertently iterate CAD Docs using the wrong version of a CAD tool. For &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; example, a set of data which must be ProE WF4 should never be edited with WF5, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; because the end recipients of the data use only WF4. Of course once a model is &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; edited in WF5 it can no longer be opened in WF4.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; Does anybody else experience this problem? We looking for a way to mark a &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; selection of data (perhaps by folder contents) and force people to use a &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; particular version of the CAD tool, or at least warn them when they are about &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; to use the wrong CAD version.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; The CAD tool version previously used is stored in CAD Doc object, however it &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; is not displayed in the UI by default and the information is not in a format &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; that is easily recognizable by users.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt; Regards Darren&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Perhaps something could be done with a jlink listener:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; 1. jlink listens for opening a model&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; 2. the jlink app then gets the current running Pro/Engineer version and&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    buildcode (this part is easy)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; 3. the jlink app then reads the first line of the modelfile and parses the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    Pro/Engineer version&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;      * reading the first line of the modelfile and parsing for the Pro/Engineer&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;        version would be fairly straight forward&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;      * figuring out how to find out which file in the OS to read since this is&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;        coming from a workspace would be difficult&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;      * maybe there is some jlink method that returns the version of&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;        Pro/Engineer that last edited the file&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; 4. jlink then compares the current running version of Pro/Engineer with the&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    version that edited the file and pops up a warning dialog if the current&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;    version of Pro/Engineer is newer&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;-- &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;------------------------------------------------------------------------&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Randy Jones&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Systems Administrator&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Great Plains Mfg., Inc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;1525 E North St&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;PO Box 5060&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Salina, KS USA 67401&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;email: -&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Phone: 785-823-3276&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;   Fax: 785-667-2695&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;------------------------------------------------------------------------&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 19:59:28 GMT</pubDate>
      <guid>https://community.ptc.com/t5/Windchill/Prevent-editing-of-CAD-files-with-wrong-version-of-CAD-tool/m-p/3223#M378</guid>
      <dc:creator>RandyJones</dc:creator>
      <dc:date>2017-10-26T19:59:28Z</dc:date>
    </item>
  </channel>
</rss>

