<!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>PLV overview</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_topic2" id="xps10_pagetitle">PLV overview</div>
      <hr noshade="true">
      <p class="para_topic">Part Library View files define a menu hierarchy for choosing parts during the Routing Electrical <b class="uiTerm">Place Part</b> and <b class="uiTerm">Assign Stock</b> operations. The defined hierarchy reflects in the left panel of the <b class="uiTerm">Specify Item</b> dialog box, where you choose a part to place or a stock to assign. This topic defines the basic syntax of a part library view file.
      </p>
      <p class="para_topic">The basic concept is to create a system of nodes and subnodes that guide the user through the selection of a part. Each node may point to subnodes (SUBNODES), which are presented as further options when that node is selected. You may set up as many subnodes as you like. The last subnode of a hierarchy must define a single part file, a routing part table (TABLE) or a directory filter (FILTER).</p>
      <p class="para_topic">The APV file designates a part start node and a stock start node for a given <b class="uiTerm">Discipline</b> (see APV topic). &nbsp;The <b class="uiTerm">Specify Item</b> dialog box shows the hierarchical structure beginning at the appropriate start node. This allows you to have parts belonging to different <b class="uiTerm">Disciplines</b> (piping, tubing, etc.) in a single library but directs you to the parts of one <b class="uiTerm">Disciplines</b>. For example, if you define a <b class="uiTerm">Discipline</b> named Piping and a <b class="uiTerm">Start Part Node</b> named PIPING_PARTS, you go directly to that node when using the <b class="uiTerm">Piping Discipline</b>, so all other parts belonging to other <b class="uiTerm">Disciplines</b> do not appear.
      </p>
      <p class="para_topic">If a node specifies FILTER while in native mode, then the standard NX file selection dialog box appears using the given filter. The filer may include a directory path, which may make use of an environment variable. A dollar sign ($) is placed before and after the variable name. See the sample PLV file provided with the installation for examples. </p>
      <p class="para_topic">If the node points to FILTER while in Teamcenter mode then the Teamcenter part file selection appears and the filter string is ignored (but must be present in the PLV file).</p>
   </body>
</html>