<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Customer Defaults and Routing Preferences</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic4" id="xps10_pagetitle">Customer Defaults and Routing Preferences</div>
      <hr noshade="true">
      <p class="para_topic">Routing applications are transitioning the <b class="uiTerm">Preferences</b> menu to <b class="uiTerm">Customer Defaults</b> menus. See <a class="links" href="javascript:void(0)" onclick="top.popUpPage('cust_defaults/index.html?goto=cust_defaults/01topic_1.html&vars=-aux,-home','linkInter','menubar=yes,status=yes,resizable=yes,toolbar=yes,scrollbars=yes,location=no,directories=no');return(false);">Customer Defaults</a>, for further details.
      </p>
      <p class="para_topic">In NX 5, the Routing <b class="uiTerm">Preferences</b> menu remains to allow preference changes to take effect with an NX session; however, to save any changes for future NX sessions, you must make (and save) the same changes through the <b class="uiTerm">Customer Defaults</b> menus, such as when using NX 5 for the very first time.
      </p>
      <p class="para_topic">For backward compatibility, Routing will continue to support preferences in the Application View files (.apv and .xml). However, in NX 5, the shipped APVs no longer have the references, and a release note indicates that Routing will remove preferences support within the APVs in a future NX release.</p>
      <p class="para_topic">To avoid duplicate Routing preferences between the Routing applications, the <b class="uiTerm">Customer Defaults</b> file has a <b class="uiTerm">Routing General</b> category that all Routing applications share. The Routing categories and tabs hierarchy within the <b class="uiTerm">Customer Defaults</b> menus are as follows:
      </p>
      <ul class="hangingList">
         <li>
            <p class="para_item">General (formerly <b class="uiTerm">Preferences&rarr;Routing</b>)
            </p>
            <ul>
               <li>
                  <p class="para_item">Paths</p>
               </li>
               <li>
                  <p class="para_item">Stock</p>
               </li>
               <li>
                  <p class="para_item">Parts</p>
               </li>
               <li>
                  <p class="para_item">Display</p>
               </li>
               <li>
                  <p class="para_item">Disciplines</p>
               </li>
            </ul>
         </li>
         <li>
            <p class="para_item">Electrical (formerly <b class="uiTerm">Preferences&rarr;Wiring</b>)
            </p>
            <ul>
               <li>
                  <p class="para_item">General</p>
               </li>
               <li>
                  <p class="para_item">Navigators </p>
               </li>
               <li>
                  <p class="para_item">Logical Associations</p>
               </li>
            </ul>
         </li>
         <li>
            <p class="para_item">Mechanical (formerly <b class="uiTerm">Preferences&rarr;Piping</b>)
            </p>
         </li>
      </ul>
      <p class="para_topic"><b class="uiTerm">Customer Defaults</b> cannot support the mirroring of the following Routing <b class="uiTerm">Preferences</b> (because of selection or dynamic list creation):
      </p>
      <ul>
         <li>
            <p class="para_item">Choose Stock</p>
         </li>
         <li>
            <p class="para_item">Choose Anchor</p>
         </li>
         <li>
            <p class="para_item">Specify Default Elbow (from the <b class="uiTerm">Parts</b> tab)
            </p>
         </li>
         <li>
            <p class="para_item">Set Down Direction</p>
         </li>
         <li>
            <p class="para_item">Discipline (from the <b class="uiTerm">Discipline</b> tab)
            </p>
         </li>
         <li>
            <p class="para_item">Specification (from the <b class="uiTerm">Discipline</b> tab)
            </p>
         </li>
         <li>
            <p class="para_item">Gasket (from the <b class="uiTerm">Piping Preferences</b>)
            </p>
         </li>
         <li>
            <p class="para_item">Ring Joint (from the <b class="uiTerm">Piping Preferences</b>)
            </p>
         </li>
         <li>
            <p class="para_item">Bolt Material from the <b class="uiTerm">Piping Preferences</b>)
            </p>
         </li>
         <li>
            <p class="para_item">Nut Material (from the <b class="uiTerm">Piping Preferences</b>)
            </p>
         </li>
         <li>
            <p class="para_item">Thread Type (from the <b class="uiTerm">Piping Preferences</b>)
            </p>
         </li>
         <li>
            <p class="para_item">Weld Material (from the <b class="uiTerm">Piping Preferences</b>)
            </p>
         </li>
      </ul>
      <p class="para_topic">As a result, these preferences will not appear in any form under the <b class="uiTerm">Customer Defaults</b> Routing tabs. To change the values during the NX session, you must go through the <b class="uiTerm">Preferences</b> menu. To change these values for the next NX session, you must edit the relevant preference item in the Application View file, as previous releases required.
      </p>
      <p class="para_topic">The precedence hierarchy (highest to lowest) for Routing to obtain preference values is as follows:</p>
      <ol type="1" start="1">
         <li>
            <p class="para_item"><b class="uiTerm">Preferences&rarr;Routing</b> (those set within NX).
            </p>
         </li>
         <li>
            <p class="para_item">.apv and .xml preferences (if any).</p>
         </li>
         <li>
            <p class="para_item">Routing <b class="uiTerm">Customer Defaults</b> file (.dpx).
            </p>
         </li>
      </ol>
   </body>
</html>
