Cancel
Showing results for 
Search instead for 
Did you mean: 

Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Has any of you already had the need to retire naming rules?

The existing items should still be usable, but new items should not be allowed to be created with the retired naming rules.

I imagine that the conditions could be used for this, but I haven't had time to check the BMIDE by now.

Thanks in advance for your experience Smiley Wink

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, 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 Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
15 REPLIES

Re: Restrict naming rule usage

Gears Phenom Gears Phenom
Gears Phenom

You want to completely not use that naming rule any more? You should be able to just remove it from your item type in BMIDE without issues. The existing items in TC will not be affected but no more new numbers will be available. It's been a while since I needed to do this, so I'd suggest testing it out and make sure revisions still function (but I think they will work fine).

 

I've used conditions to restrict naming rules to specific groups. So instead of removing it completely, you could set it to be available for just DBA for example.

 

Jamie

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Thanks for your suggestions, I will post back with the results.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, 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 Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Hello @Jamie_Griffis,

do you or anyone else have an example of the condition that should be used to restrict the naming rule application to a specific group?

I tried to create a condition, but it failed to work out as expected.

Thanks in advance.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, 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 Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Restrict naming rule usage

Gears Phenom Gears Phenom
Gears Phenom

@Stefan_Pendl - Before I attempt to show you what I've done before (and possibly confuse the situation), how many groups are able to create this item? How many are restricted to each naming rule? Are there only 2 naming rules or more?

 

Jamie

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

@Jamie_Griffis,

initially there will be only MENCTool created by two groups and one naming rule for each group.

I think that I had the condition wrong, so I would just need a screen-shot of that.

Usually the condition isTrue() is used for our naming rules, but I need to refine them now.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, 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 Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Restrict naming rule usage

Gears Phenom Gears Phenom
Gears Phenom

@Stefan_Pendl - Here is a quick example. Create 2 conditions, one for each group type. Mine is dba or not dba, your's would be group "a" or group "b".

 

Condition example. You will create a 2 custom user session conditions (one for each group/naming rule), name the condition something that makes sense to you. Your group will be inside the quotes. Could be like "Engineering.SiteA" (I'm just making up examples because I'm not familiar with your Org.)

 

 

cond2.png

 

 

 

 

 

 

Add the 2 naming rules to the item using the 2 conditions:cond4.png

 

 

 

 

 

 

 

 

 

 

 

Hopefully that helps. Let me know if it works or not.

 

Jamie

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

Sorry, but I still seem to miss something, since I don't get a rule selector when creating the item.

Conditions:00_condition_one.PNGCondition One

 

01_condition_two.PNGCondition Two

 

I also tried with custom input parameters, but no chance.

Naming Rules:02_naming_rule_one.PNGNaming Rule One

 

03_naming_rule_two.PNGNaming Rule Two

MENCTool:04_item_definition.PNGItem definition

Display in New Item dialog:05_new_item_one.PNGNew Item One

 

06_new_item_two.PNGNew Item Two

What could be causing this, if the settings are all correct?

Thanks in advance for any pointers in the right direction.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, 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 Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Restrict naming rule usage

Gears Esteemed Contributor Gears Esteemed Contributor
Gears Esteemed Contributor

If I use IsTrue() as the condition for one rule, I get the patterns of that one rule, but then I cannot specify different rules Smiley Frustrated07_use_condition_istrue.PNGUse Condition IsTrue()So things seem to be updated as expected.

Stefan Pendl, Systemmanager CAx, HAIDLMAIR GmbH
Production: NX10.0.3, VERICUT 8.1, 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 Smiley Wink
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide

Re: Restrict naming rule usage

Gears Phenom Gears Phenom
Gears Phenom
It will take me a bit to get back into my system to figure out how I got it working. I'll get back to you.