Skip to main content
V
vmcdaniel1-Visitor
1-Visitor
July 2, 2012
Question

attribute value lists

  • July 2, 2012
  • 5 replies
  • 1150 views
Is it possible to have different value lists for an attribute depending on Context? If so, is this documented somewhere? The Biz and Sys admin courses and help don't seem to cover it.
Thanks for your help!

5 replies

V
vmcdaniel1-VisitorAuthor
1-Visitor
July 2, 2012

Is this one too simple to get a response or something? All I hear are crickets.

avillanueva
avillanueva23-Emerald I
23-Emerald I
July 2, 2012
Give it time. Some users get these emails in digest or at home. Far
from an official answer, I believe the Type Manager is not accessible
from a Product or Library page therefore, the answer is no. Unless you
customize the system to limit it, all values would be shown for all
context.


A
AL_ANDERSON12-Amethyst
12-Amethyst
July 2, 2012
You cannot do what you want exactly as you want to do it. However, if you
make a different light type subclass from some main class for each context
that needs different attributes, and then you use OIRs and access control
rules such that only your context-allowed type can be created new in each
context, then you can get what you want. You can even use different color
icons to highlight the part types/contexts as you look at them in a
multi-level BOM.

Of course, this is approach is problematic if you "move" items between
contexts frequently, and therefore would have to "change type" - something
that is not available out of the box.

If you do not plan to move items between contexts, and there is a very low
chance of creating a part or document in the wrong context with the wrong
type, then use this idea.

Al




A
AL_ANDERSON12-Amethyst
12-Amethyst
July 2, 2012
Oh, and the kicker would be to make the parent node "not instantiable" so
that in a particular context an author only sees one "type" to create -
the type for that context.

Be careful with "not instantiable" however, since any edits in some of the
manager applets (like the domain administrator) to subtypes may require a
temporary "enabling" of the parent type to see the lower types. I can't
remember exactly where that happens, but it does. We make parent nodes
like this "not instantiable" a lot just for reasons like this one.

Al




V
vmcdaniel1-VisitorAuthor
1-Visitor
July 2, 2012
Hi Al,
I was concocting the same plan with sub-typing. But, I just don't like it.

This was another thought. If I could have ATTR-A value determine ATTR-B value list, this would work for me.
We are on 10.0 M030 and I see the Attribute Constraint Conditions that appear to be designed to do this. But they are not fully enabled in 10.0, anyone know if they are in 10.1?

-Vaughn
Terms & ConditionsAccessibility statement