Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Restrict naming rule usage

Gears Phenom Gears Phenom
Gears Phenom
Mine works... can we take this offline over email to work it thru and just post the results here? I'll send you my personal email.

Jamie

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Sure, lets do the hard stuff offline and report the solution here.

BTW, which Tc release are you working with, mine is Tc 10.1.7?

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong ;)
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Restrict naming rule usage

Solution Partner Honored Contributor Solution Partner Honored Contributor
Solution Partner Honored Contributor
Did you folks fix this? What was the answer?

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Restrict naming rule usage

Gears Phenom Gears Phenom
Gears Phenom

@RandyEllsworth - it works for me, and I'm using it currently. Stefan hasn't got it working yet or not that I've heard back. We are on different versions of TC and I don't any problem in TC11, seems to be a problem in TC10. I don't have anywhere with TC10.x installed to test.

 

Jamie

Re: Restrict naming rule usage

Solution Partner Honored Contributor Solution Partner Honored Contributor
Solution Partner Honored Contributor
Tc10.1.7 appears to honor the same as Tc11.2.x. Make sure to check "Override" to prevent the condition checking the parent instead of using the isTrue (default) condition.
https://docs.plm.automation.siemens.com/tdoc/tc/10.1.7/help#uid:xid1256815:index_plm00071:id1637945:...

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Sorry had to switch to more important work :(

Overwrite is only available for isTrue() conditions, so I removed the naming rule setting from the resource item to make it display the one for METool.

Others have used equal and not equal to the same group, but I need one or the other group, which seems to be the culprit.

Will report back with my findings.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong ;)
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
Highlighted

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

So I have found time to make up my mind once more about this subject and found a solution.

Since many of our users are members of multiple groups, the simple group_name check doesn't work, instead one needs to use the function "fnd0getGroupName()".

Conditions:Condition_01.PNGCondition Group HAI

 

Condition_02.PNGCondition Group HTM

Naming rules:NamingRule_01.PNGNaming Rule HAI

 

NamingRule_02.PNGNaming Rule HTM

Proposals when creating an item:NameProposal_01.PNGName Proposal HAI

 

NameProposal_02.PNGName Proposal HTM

Hope this helps.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.2, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 11.4
Development: C (ITK), .NET, Tcl/Tk Testing: NX12.0 | AWC 3.4 Preparing: NX12.0

Employees of the customers, together we are strong ;)
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide