Inheritance link, part to part, meaning of different icons in Model Tree

[Pius]

Hi all
I'm using inheritance .prt to .prt model links.
I'm getting 3 different icons shown in the model tree.

and

Can someone explain the different meanings of these 3 variants?

I already checked the information in Model Tree Icon List - PTC Community

Thanks a lot in advance
Pius

We are using Creo Paramterics 8.0.4.0, 

[MartinHanak]

Hi,

if you can ask the same question to PTC Support.

EDIT:

https://support.ptc.com/help/creo/creo_pma/r12/usascii/#page/assembly/asm/About_Inheritance_Features.html#

[remy]

Hello,

Thank you for asking about those glyphs. Those indeed pertain to Inheritance Features and carry a meaning. The best ressource here has to be the Help Center.

First 

	This is a vanilla Inheritance feature
	This is an Inheritance feature with Varied Items
	<will get back to you>

FYI Varied Items can be set accessing that menu (here when the Inheritance Feature is created) :

or RMB the existing Inheritance feature > Varied Items 

[Pius]

Hello remy

This sounds promising.
Is there an option  to get rid of the "varied items" symbol?
It may have happen that I selected this just for fun but without any need.

?

[Pius]

Oh, yes!
Here in I found a datum plane which was of no use.  

Deleted it and the Icon turned back to "Vanilla".

Many thanks.

[remy]

Finally about the Pause glyph, it looks like something related to Windchill which is out of my technical area. 

According to that article : https://www.ptc.com/en/support/article/CS243120 

And the article here : https://www.ptc.com/en/support/article/CS58783 tells that the glyph is about some frozen state of a feature and I'm not totally sure if this state is relevant with Standalone Creo Parametric.

[KenFarley]

The "Pause" glyph is something I've seen a lot in poorly constructed models where, for some reason, feature(s) are frozen. My interpretation of it is that it's kind of a near-failure. Something that was used to define a particular thing is missing or no longer there but instead of failing the feature it is "frozen". Whenever possible, if I'm confronted with this in a model, I will try to fix the feature or perhaps delete it. Use the feature info tools to decide whether fix it or kill it is appropriate. For the most part the times I've seen it the referenced feature was a garbage datum that didn't serve any purpose.

[vnamboodheri]

Hello @Pius, 

It looks like you have some responses from some community members. If any of these replies helped you solve your question, please mark the appropriate reply as the Accepted Solution. 

Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

Thanks,
Vivek N.
Community Moderation Team.