Skip to main content
N
NickD10-Marble
10-Marble
September 20, 2012
Solved

How to set CAD Doc Name = CAD Doc Number less extension rather than = CAD filename less extension ?

  • September 20, 2012
  • 2 replies
  • 7001 views

By tweaking the OOTB OIRs (to remove the GetServerAssignedConstraint from the "number" AttrConstraints) and setting some Preferences, we have almost got what we need, but not quite. As shown on the screen grab image below (if it is legible...) we have got the CAD filename driving the CAD Doc Number (which has to be unique, and it goes into CAPITALS regardless of the case of the filename), and similalry CAD Doc Name is based on CAD filename but dropping the extension - so it is quite literally becoming the "common name" for associated parts, drawings and WTParts (and these are being autonumbered). The CAD filenames come from an external system, that generates document numbers in CAPITALS. All of this is what we want except the case being used for the CAD Doc Names.

The discrepancy we are left with is due to the different behaviour or Pro/E and SolidWorks, where Pro/E always puts the filename into lowercase, but SolidWorks preserves the case of the filename as it was entered in the UI. As a result, the CAD Doc Names are created in the case set by each of the CAD tools, but the CAD Doc Numbers are always put in CAPITALS by Windchill. What we would like is to get all the CAD Doc Names also put into CAPITALS as well (without the filename extensions), so they can all be searched and browsed more easily.

We have discovered in some early testing of v10.0 for ECAD (where empty ECAD Docs are created first, then ZIP files are attached - so they have to be named and numbered without any reference to the filenames) that we can edit the ECAD OIRs to drive the CAD Doc Name from the CAD Doc Number, and also prevent the user from entering the CAD Doc Name (so they only have to enter one thing). Since the CAD Doc Number is put into CAPITALS by Windchill, we get them both in CAPITALS regardless of what case the user types in for the Number (and we regard this as perfect).

So, we have just tried adding the following to our CAD OIRs (and un-set the Preferences mentioned above), but Name is not being copied from Number.

<!-- set the name to be the same as the number but without the filename extension portion -->

<AttrValue id="name" algorithm="wt.rule.algorithm.Substring">

<Attr id="number"/>

<Arg>0</Arg>

<Value algorithm="wt.rule.algorithm.IndexOf">

<Attr id="number"/>

<Arg>.</Arg>

</Value>

</AttrValue>

<AttrConstraint id="name" algorithm="com.ptc.core.rule.server.impl.GatherAttributeConstraints">

<Value algorithm="com.ptc.core.rule.server.impl.GetServerAssignedConstraint"/>

<Value algorithm="com.ptc.core.rule.server.impl.GetImmutableConstraint"/>

</AttrConstraint>

Can anyone see or suggest what we need to do to stop the CAD filename being used to drive the CAD Doc Name, and let the OIR create the CAD Doc Name instead from the CAD Doc Number (in CAPITALS, and without the filename extension) ?

Any help gratefully received.

Names_Numbers_Filenames_OK_new_files_2.gif

Best answer by ngiacom

ModelName is the string that you insert in Proe. FileName becomes modelname.prt. Number becomes MODELNAME.PRT and Name becomes MODELNAME (with custom EPMDocumentNamingDelegate, the default behaviour should modelname.prt or modelname by preference).

The class is simple, I don't know if it works in 9.1.

package ext.yourcompany...

import com.ptc.windchill.uwgm.proesrv.c11n.DocIdentifier;

import com.ptc.windchill.uwgm.proesrv.c11n.EPMDocumentNamingDelegate;

public class EPMDefaultDocumentNamingDelegate implements EPMDocumentNamingDelegate {

@Override

public void validateDocumentIdentifier(DocIdentifier docIdentifier) {

String name = docIdentifier.getDocNumber();

if (name.contains(".")) {

name = name.substring(0, name.lastIndexOf("."));

}

docIdentifier.setDocName(name.toUpperCase());

}

}

The rename is an other Universe. This approach is valid only the first time that you upload a cad document.

As said before I found UwgmEvent.PRE_RENAME ... (it should be tested).

Are you welcome.

Nicola

2 replies

N
ngiacom14-Alexandrite
14-Alexandrite
September 24, 2012

Hello, do you have the preference Operation > Upload Operation > Upload > Upload Drop Name File Extension?

There is this preference in my Windchill 10.1 and it works.

I tried other solutions without success:

OIR --> doesn't work

custom EPMDefaultNamingDelegate --> doesn't work

P
ptc-19173661-Visitor
1-Visitor
September 24, 2012

The preference setting from Nicola suggests is what we use; back to 9.1. BUT, we still have an issue with users being able to Rename and do whatever they want. The system does not enforce this on renames. We have complained to PTC, but no resolution after a year.

N
NickD10-MarbleAuthor
10-Marble
September 24, 2012

We have used all four of the following Preferences to get the behaviour shown in the screen grab image in my original posting, and they all work as expected in v9.1

WGM / Client / Sync’ Number & Filename = Yes, & Locked (This option is applied when creating new files from an authoring application. Number may be with or without file extension depending on the preferences "Upload Drop Number File Extension")

WGM / Server / New CAD Doc’ / Sync’ CAD Model Name with CAD Doc Number = Yes, & Locked (This synchronization is not applicable when auto numbering is in effect)

WGM / Server / Auto Associate / Auto Associate Truncate Name File Extension (changing it to Yes, and Locked)

WGM / Client / Upload / Upload Drop Name File Extension (changing it to Yes)

But what we are trying to do now is keep the same CAD Doc Numbering behaviour, ie. it goes into CAPITALS when copied from the CADName (filename), and then get that Number (in CAPS) truncated and copied into the Name using the following OIR entries - and we are currently trying this with all of the Prefs listed above set back to thier OOTB defaults :

<!-- set the number to a CAD File name -->

<AttrValue id="number" algorithm="com.ptc.windchill.enterprise.revisionControlled.server.impl.NumberGenerator">

<Attr id="CADName"/>

</AttrValue>

<!-- set the name to be the same as the number but without the filename extension -->

<AttrValue id="name" algorithm="wt.rule.algorithm.Substring">

<Attr id="number"/>

<Arg>0</Arg>

<Value algorithm="wt.rule.algorithm.IndexOf">

<Attr id="number"/>

<Arg>.</Arg>

</Value>

</AttrValue>

The results of this are: Name (in lowercase) = Number (in UPPERCASE) = CADName (in lowercase).

N
ngiacom14-Alexandrite
14-Alexandrite
September 24, 2012

I think that the problem is about the Policy-Managed Naming and Numbering. In your case is name-driven. Then the name is the creo file name. CADName is the name + extension. Number is CADName uppercase.

Maybe if you had the number-driven or parameter-driven policy your OIR (or EPMDefaultNamingDelegate) should work.

Eventually you (and Rick) could implement a custom service on event EPMWorkspaceManagerEvent.POST_WORKSPACE_CHECKIN that changes the name.

Have you opened a ptc case? What they say about this issue?

P
ptc-19173661-Visitor
1-Visitor
September 24, 2012

We want what Pro/E wants. CADName is the unique key. But WC the unique key is Number. So we try to get Number driven from CADName (and it is on uploads) but users can change Number without changing the CADName, thus causing a problem. PTC of course says this is fine and that we need to customize or submit an enhancement request that will never be implemented (which we have done).

Customization is rarely simple. Your suggested event, I don’t think is triggered on a rename. There is no Check out for this task….correct?

N
ngiacom14-Alexandrite
14-Alexandrite
September 24, 2012

Can you remove "rename" access to your bad users?

Otherwise I found UwgmEvent.PRE_RENAME ... it should be tested.

Terms & ConditionsCookie settingsAccessibility statement