<!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>How do I?</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_topic1" id="xps10_pagetitle">How do I?</div>
      <hr noshade="true">
      <div class="title_division">What happens if I leave a conference but not NX?</div>
      <p class="para_division">Nothing serious happens. Your session will continue to work as always, but you will not receive any collaborated changes, nor can you send any changes.</p>
      <div class="title_division">What happens if I leave a conference accidentally?</div>
      <p class="para_division">Rejoin the conference using <b class="uiTerm">Tools&rarr;Collaborate&rarr;Connect to Teamcenter Community</b>. &nbsp;NX will automatically reconnect to the conference provided you have not closed NX or exited the Teamcenter Community <b class="uiTerm">Conference Manager</b>.
      </p>
      <div class="title_division">What happens if I exit NX but not Teamcenter Community CAD conference?</div>
      <p class="para_division">Your NX session will save any parts as you direct. The connection to Teamcenter Community will terminate. &nbsp;The conference will continue to be active until you leave the conference.</p>
      <div class="title_division">What happens if NX crashes or gets hung and I have to terminate it?</div>
      <p class="para_division">You will lose all of your unsaved work. Most likely, you will have to also hang up and immediately recall the participants in the Teamcenter Community conference, to allow NX to reestablish a proper connection to the conference session.</p>
      <div class="title_division">Can I create new parts and collaborate them in an active collaboration session?</div>
      <p class="para_division">You can create new parts, but you will need to do several things to get them into collaboration. All collaboration participants who wish to receive the part must first create a new part. This will put the part into collaboration. You can modify the part and transfer it like any other part in collaboration.</p>
      <div class="title_division">What happens if I reopen a part that the Part Send function has updated?</div>
      <p class="para_division">If you use the <b class="uiTerm">NX Reopen Part</b> function, then all changes you have made or received will be lost. This may or may not be what you want to have happen.
      </p>
      <div class="title_division">What happens if two people are collaborating a part and they both add features that use the same parameter/expression name?</div>
      <p class="para_division">If you are going to be making changes to a part in collaboration, and you don't hold the token for the part, it is best to coordinate with the person who does have the token. This will prevent or at least minimize your local changes from being overwritten or rendered inappropriate by the person with the token.</p>
      <p class="para_division">It is a best practice to always name your parameters, and be especially creative when working on a part in collaboration. However if you do end up with parameters of the same name, when they are updated in a <b class="uiTerm">Collaboration Expression</b> change, your results will (most likely) be undesirable and you will need to correct the situation. You will probably want to get the token holders part (with their new features) and then recreate your features (but get the token first!).
      </p>
      <div class="title_division">How do I recover if someone sends me a part I don't want?</div>
      <p class="para_division">There are no rollback or undo capabilities for received parts. Your options are either to reopen your part or to manually delete the changes you received. Depending on the situation, you may want to save the just received part to a new name, then reopen your original part and cut and paste between the parts if any received changes are wanted.</p>
      <div class="title_division">How do I make sure no one changes my parts?</div>
      <p class="para_division">The best way to prevent changes to parts that you do not want to collaborate is to ensure they are withdrawn if collaboration puts them in automatically.</p>
      <p class="para_division">Remember that when other participants open parts, they may cause one of your parts to go into collaboration even though you were not expecting it.</p>
      <p class="para_division">Of course, it is also good to talk with your collaboration partners to ensure accidental collaborations do not happen.</p>
      <div class="title_division">What happens if two people give different parts the same name in an assembly?</div>
      <p class="para_division">Parts that are different, but named the same, are put into collaboration by Collaborate. If you do not withdraw the parts, you will receive updates and Collaborate will attempt to process the changes as if the parts were the same (see  <a class="links" href="javascript:void(0)" onclick="top.openFile('ugcollaborate/control_changes.html');return(false);">Controlling Collaborated Changes</a>)
      </p>
      <p class="para_division">If you transfer a piece part, the received part will replace the currently loaded part. If the transferred part is a component of an assembly, the file load will fail with message <em>Part is not a valid version of component part</em>. If the parent assembly file is transferred, the file load will fail with the message A part with the same filename is already loaded. This is also due to a version mismatch.
      </p>
      <p class="para_division">It is always good practice to check your <b class="uiTerm">PIC</b> list to ensure that the listed part are the parts you want and expect to be collaborated. NX is trying to be helpful by putting similarly named parts into collaboration automatically, but at times this action can be inappropriate or incorrect.
      </p>
      <div class="title_division">Can I continue to make model changes during a long part transfer?</div>
      <p class="para_division">If are receiving a file, you can continue to make changes to your model. Be aware that if you are changing the part you are receiving, those changes will be lost once the transfer is complete.</p>
      <p class="para_division">If you are the sending participant, then you can continue to make changes while the file send is active. You can move the progress meter that shows the status, out of the way, and you are free to work on any part, including the one you send.</p>
      <table border="0">
         <tr>
            <td valign="top" align="left"><img align="left" src="../graphics/note.gif" alt="Note" title="Note"></td>
            <td valign="bottom" align="left" width="100%">
               <div class="para_note">
                  <p class="para_note_body">The part that is sent is first saved to a temporary file and compressed before you can proceed to make changes. Therefore, no additional changes will be sent.</p>
               </div>
            </td>
         </tr>
      </table>
      <div class="title_division">Can I download files or browse the Internet while doing a collaboration or part transfer?</div>
      <p class="para_division">Collaborate does not interfere with your use of the Internet. Beside the impacts on overall network bandwidth and CPU time, there are no limitations on what you can be doing on the Internet while using Collaborate.</p>
      <div class="title_division">What is that dialog box that sometimes flashes when I first send collaboration changes?</div>
      <p class="para_division">That dialog box is the <b class="uiTerm">Request Token</b> dialog box. The request token function automatically executes when you collaborate a change to a part and no one has ownership of the token. 
      </p>
      <div class="title_division">I closed my display part and therefore had a blank display. Then I got a display part without doing anything. What is going on?</div>
      <p class="para_division">When you receive a message from another NX session that causes a change in your session, we often have to change the work and/or display part to process the message. In most cases we can restore the display (display part and work part) to the previous state. But if you have no display part, Collaborate cannot restore to that state. What happened is that your session received a message and we had to change the display part, but could not put it back to a blank display.</p>
      <div class="title_division">What should I do if I am using Knowledge Fusion to control the parameter expressions of a feature?</div>
      <p class="para_division">Do not use the <b class="uiTerm">Send Expressions</b> button. You should use the <b class="uiTerm">Part File</b> button or the <b class="uiTerm">Send Part</b> button from the <b class="uiTerm">PIC Navigator</b> to update parts controlled by Knowledge Fusion. The reason for this is that Knowledge Fusion will only store the rule or expression value in the <b class="uiTerm">Expression Subsystem</b>, for example, 20 and not the rule or expression string itself. Transferring expressions will update the recipient's expressions and Knowledge Fusion attribute with the value, losing the design intent in Knowledge Fusion (KF). One collaborator will have the rule, and the other only the value.
      </p>
      <div class="title_division">Why do I lose my component, which has been Part Name Mapped, after transferring the parent assembly file?</div>
      <p class="para_division">When using <b class="uiTerm">Part Name Mapping</b>, sending assembly files will result in the use of part file names of the sender. You might see warning or error messages. The mapped file names will not be used in the assembly unless the mapped component is added again using <b class="uiTerm">Assemblies&rarr;Components&rarr;Open As</b>, or <b class="uiTerm">Substitute Component</b>. Often, the error message is <em>Part is not a valid version of component part</em>.
      </p>
      <div class="title_division">If the collaborators are using operating system file management, how do I prepare the files for distribution?</div>
      <p class="para_division">Save the necessary parts to a directory, compress them if possible, and use the file transfer facility of the conferencing system to distribute them.</p>
      <div class="title_division">If the collaborators are using operating system file management, how do we create a new part?</div>
      <p class="para_division">All collaborators must create a new part in their session with the same name. The part is then in collaboration, and can be transferred as changes are made.</p>
      <div class="title_division">If the collaborators are using operating system file management, how do I add a new component to an assembly?</div>
      <p class="para_division">The person holding the token for the parent adds a new component, and then does a <b class="uiTerm">Send Part</b> of the assembly file. If the component is already loaded it add automatically. If it is not loaded, Collaborate will attempt to load the component using the assembly load options.
      </p>
      <div class="title_division">If the collaborators are using Teamcenter Engineering or Teamcenter Integration file management, how do I prepare the files for distribution?</div>
      <p class="para_division">Use <b class="uiTerm">Tools&rarr;Teamcenter Integration&rarr;Export Assembly</b> to a directory (be sure the <b class="uiTerm">Partial Component Load</b> option is off), compress them if possible, and use the file transfer facility of the conferencing system to distribute them. Collaborators use <b class="uiTerm">Tools&rarr;Teamcenter Integration&rarr;Import Assembly</b>, using the same file names.
      </p>
      <div class="title_division">If the collaborators are using Teamcenter Engineering or Teamcenter Integration file management, how do I create a new part?</div>
      <p class="para_division">All collaborators must create a new part in their session with the same name and version, and then <b class="uiTerm">Save</b> the part. The part is then in collaboration, and can be transferred as changes are made. If the part is not saved, a part transfer error is received with message Part item not found.
      </p>
      <div class="title_division">If the collaborators are using Teamcenter Engineering or Teamcenter Integration file management, how do I add a new component to an assembly?</div>
      <p class="para_division">The person holding the token for the parent adds a new component, and then does a <b class="uiTerm">Send Part</b> of the assembly file. If the component is already loaded it add automatically. &nbsp;If it is not loaded, Collaborate will attempt to load the component using the assembly load options.
      </p>
      <div class="title_division">If the collaborators are using a mixed environment for file management, how do I prepare the files for distribution?</div>
      <p class="para_division">Save the files directly to a directory, or use <b class="uiTerm">Tools&rarr;Teamcenter Integration&rarr;Save Outside Teamcenter Engineering</b> (be sure the <b class="uiTerm">Partial Component Load</b> option is pff) to a directory, and use the file transfer facility of the conferencing system to distribute them. An OS collaborator can then open the parts directly, a Teamcenter Integration user will use <b class="uiTerm">Tools&rarr;Teamcenter Integration&rarr;Import Assembly</b>, using the same file names.
      </p>
      <div class="title_division">If the collaborators are using a mixed environment for file management, how do I create a new part?</div>
      <p class="para_division">All collaborators must create a new part in their session with the same name and version, and Teamcenter Integration users must <em>save</em> the part. The part is then in collaboration, and can be transferred as changes are made. If the part is not saved in Teamcenter Integration, a file transfer error is received with message <em>Part item not found</em>.
      </p>
      <div class="title_division">If the collaborators are using a mixed environment for file management, how do I add a new component to an assembly?</div>
      <p class="para_division">Do not exchange assembly part files. It is not possible to add a new component in this environment. Do not exchange assembly part files. Sending assembly part files will corrupt the assembly structures, due to differences in component information stored in the part file and used by the different file managers (OS and Teamcenter Integration). If an assembly is transferred accidentally, the receivers should restart their NX session, and reestablish the conference.</p>
   </body>
</html>