Are you setting CAD Document Number, Name and File Name all to the same value?
Let's use this discussion forum to document your techniques to simplify this for the user.
I am including a proposal below.
We are currently moving to PDMLink 10 (from Intralink 3.4) and this post comes to the right time.
We try to setup PDMLink as suggested in this article.
I like your proposal. We manually set all three to be the same, and it can be tedious.
What do I do with the xml file you attached?
The .xml file is an example of OIRs (Object Initialization Rules) that will:
1. Cause the CAD Document Number and Name to show in Windchill UIs as:
e.g. in the .xml file you see:
<AttrConstraint id="number" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">
The 2nd line makes the UI display that the number is generated
The 3rd line makes the UI make the "Number" field Read Only.
2. These values will be generated from the CAD Doc "File Name"
e.g. in the file you see:
<!-- set the number to a File Name -->
<AttrValue id="number" algorithm="com.ptc.windchill.enterprise.revisionControlled.server.impl.NumberGenerator">
This sets the CAD Doc Number == CADName (the internal name for CAD Doc File Name)
You use this file in the "Object Initialization Rules Administration" UI:
In this UI, you will see all the Object Types in Windchill.
I do not suggest modifying the PTC default; but add a new one:
- Choose "New Rule" toolbar button in the OIR Administration UI
- Set the Name to whatever you want (e.g. Custom CAD Document Rule)
- Set the Type to "CAD Document" (you could also set at EPMDoc level; but if you use Dynamic Docs it would not be recommended).
- Then upload my file. It is the same as the default file; except for the changes mentioned above.
Now all Windchill actions (e.g. Upload, Save As, etc.) will set Number and Name to be the same as the CAD Document File name.
Thanks Jennifer. I am new to Windchill, but a long time Model Manager user. Windchill is a beast by comparison. I know it can be configured to do what I want, it is just about how to configure it. Here is our scenario (using MM terminology) whenever a model is checked in and later a drawing created:
Masterdata (part record) NAME = inherited from 3D model, DESCRIPTION = inherited from 3D model
|- 3D Model (cad doc) NAME = auto generated, DESCRIPTION = populated from part/assy name in CAD environment
'- 2D Drawing (cad doc) NAME = inherited from 3D model, DESCRIPTION = inerhited from 3D model
We have our CAD environment (Creo Elements/Direct formerly CoCreate) setup so the DESCRIPTION field displays in the model tree, so the human readable names continue to be where people expect them. The NAME field is tied to an attribute called Model Name and shows our automatic part numbers once data has been checked in at least once. So when a model is first checked in, a Part record is created as a container to go with it. They both get the same automatic part number. Later when the drawing is created and checked in, it also gets the same part number. The models and drawings are linked below the Part records. Multiple revisions of models and drawings can live there since uniqueness is a combination of CLASS, NAME, VERSION. Later when BOMs are created, they are maintained by links between the part records. My first real simple question is: does Winchill work the same way?
Setting this up in MM was no big deal, but I am lost in Windchill. Your proposal sounds closely related to what I am trying to do. Are there any white papers or other helpful documentation you can point me at that might give me a clue?
I did download the rule.xml from the Site / OIR Administrator / EPM Document record and compared it to your rule. It really doesn't look like it is "identical except" though the changes may be mostly cosmetic (level of indentation, commentary, order of attributes, etc.). This is a Windchill 10 system, but it has been migrated forward from 8.1 so maybe I am seeing some non-default WC10 rule? See my rule.xml attached.
We are currently in our migration from 9.1 to 10, and I hoped to get rid of our "Synchronization" customization when I read your post.
So I merged your OIR proposal with our OIR's and checked the behavior - Looks very promising.
New EPMDocs get synchronized Name, Filename and Number. Exactly what we wanted to have!
Even on "Save As" the three keep in sync. and Name and Number are grayed out in the UI - Perfect.
I probably will hide the Name and Number columns from the UI using the Layouts / Table Displays as you recommended.
The only issue I have is on renaming EPMDoc's - no OIR's are evaluated on Rename... Probably I got some wrong preference settings - you are mentioning that we need to make sure not to drive Filename by Number or Name. Could you please elaborate a little bit on the preference settings you are referring to and which values they should be set to?
Did you ever get an answer regarding the Rename function not adhering to the OIRs? I would like to update the rename to key off changes to the filename.
I never got a reply on my rename issue with Jennifers OIR's and settings. So we still have to use two customizations (one to remove the Name and Number from the rename dialog and one to copy and paste the new Filename into Name and Numner.
As you are rethinking rename - what about a multi object rename? This is another rename customization we have in place. Would be great if you coud get it into the overhaul as well (and I coould get rid of the customizatioin)
Thanks for the feedback. I plan to pursue the exact same customization that you did since we have the same requirement. Can you provide any pointers on what all files (e.g. multirename.js) to look at for customization? I am still pretty new to Windchill customizing and could use a few pointers to get started.
I am looking to make the number simply autogenerated, I don't want it to inherit the file name. Is this possible?