ILoveSketch No-Cut Demo: Spacecraft from Seok-Hyung Bae on Vimeo.

This needs to be set in your ugii_env.dat file, so that it is consistent with Teamcenter integration and Native NX.

The Template folder for Native and Teamcenter looks for a .pax file.

For Teamcenter pax files: (start with nxdm)

• nxdm_ugs_drawing_templates.pax
• nxdm_ugs_model_templates.pax

For Native pax files:

• ugs_drawing_templates.pax
• ugs_model_templates.pax

Within each of these pax files points to the name, and location of the files to be used. The Teamcenter files are pointed to Teamcenter Item/IDs with the syntax of @DB\ITEM_ID\REV

Set a variable: UGII_ENV_FILE=<location>\ugii_env.dat to have all your clients using the same configuration. Put this <location> on a share on a server, each seat would have this location mapped as a drive and one variable set to point to this location. Now you have complete control for all seats in your environment.

Restart your Teamcenter Service and open your drawings now it will have the DDMMYYYY format. If you want other formats there are other variables to get different results.

You need to define your naming convention using regular expressions. In your case you have 6 digit part number with an ‘underscore’ two digit number.

An example Regular expression for your site standards would be: (each line represents each section in the site standards)
([0-9]{6})(|_[0-9]{2})
\1
\1(|_[0-9]{2})
\2

Set the rule to numeric.

Another example would be:
([dD]?[0-9]{2}[a-zA-Z]?[0-9]{5,7})(|([a-zA-Z]{1,2}))

which would be for parts in this type of series:
1234567
12345678
123456789
d1234567
d12345678
d123456789

1234567_a
12345678_a
123456789_a
d1234567_a
d12345678_a
d123456789_a

Set your load options to load latest (now available since you set your site standards).

DATASET_saveas_pattern=${ItemID}/${RevisionID}

Which in Teamcenter 2005 (10) is stored in the database, found from Portal at: Edit -> Option… ->  Search (tab on bottom)

But what if your UGMASTER, UGPART, UGALTREP or other datasets have different naming conventions? Lets say you add a ‘Drawing’ text into the naming. The Save-As will fail. So to fix this you need to add DATASET specific saveas_pattern. This example is for UGPART datasets:

UGPART_saveas_pattern=${ItemID}-Drawing/${RevisionID}

Think of the DATASET_saveas_pattern as the global rules, and the specific dataset patterns as overrides.

In the customer defaults:
Drafting -> General -> Drawing -> Drawing settings -> use Settings from standard (option)

Example would be to have optional many arguments:

Defun: Average (Number … $nums)

This example if a function called “Average” with optional arguments of
type “Number” that can be one or many stored in a list called “$nums”.

One way to access the $nums is by creating an expression block:

@{
$total << loop {
for $num in $nums;
sum $num;
};

So in Knowledge Fusion it is possible to have a function with optional arguments and it is possible to have a function to allow one or many arguments. The design patterns I try to stick to does not have a need for variable arguments but the optional feature is nice if you can have default values then override if necessary.

There is also a save button that will create associative expression. In the expression dialog change the Listed Expressions to “Measurements”. You will have 5 expressions, Surface area, volume, mass, weight, radius of gyration.

File -> Utilities -> Customer Defaults -> Assemblies (section) -> Site Standards (sub section) -> Part Name Versions (tab). There you will see five sections.

I would suggest this type of version control go into the Site defaults file, but I’m showing the user defaults file just because I had this set when I was doing my testing. Now the syntax is pure Regular Expressions with no short cuts. This is a simple one, that expects a number 0 -> 9 and it has to be 8 digits long, seperated by a ‘.’ (dot) then a number 0 -> 9 that has to be 3 digits long. The part name match is just the ending four characters. Should have put the dot in its own group but this was just a test, to get it working this needs to be seperated. Then the last setting is the type of version. So NX knows what is the oldest or newest. This would be set to numeric for this example. Another fix I need to do for this to work. Again this is just a test.

Now that this is set. Apply the customer defaults, close and reopen NX. Now in the load options the “load latest” option is available. Also “Allow Substitution” should be enabled, otherwise this is all useless. And the Load Method should Not be “As Saved” but instead one of the other optons.

Now you can have a part file 12345678.001 & 12345678.002. When you open the assembly that has this component added it will use the latest version.

Pretty cool for those not using Teamcenter.