Object Attributes question

[lylebeidler]

I have a few questions about object attributes. I'm thinking of creating a
"Tags" parameter that can be used for a variety of purposes in Intralink -
we could just add a string of comma-separated tags, such as the customer, a
descriptor on the type of product, anything that we may want to search for
later. This parameter would not necessarily need to be editable in Pro/E,
but would need to eventually transition over whatever Windchill or Creo data
management solution we eventually upgrade to (we're currently on Ilink 3.4).

So I'm thinking of a non-filebased, perhaps non-versioned attribute. Since
I'm pretty new to Ilink administration, will this do what I want it to be
used for? Any recommendations would be welcome.

Thanks.



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>

[MikeFoster]

Hi Lyle,

We use lots of non-versioned attributes in Intralink 3.4 to do things like tracking, status, etc...

We've done a couple of test migrations to Windchill and I'm discovering that non-versioned attributes are not well implemented in Windchill. Here are two very irritating problems:


1. Apparent bug: A custom Table View will not filter on non-versioned attributes so we can't show a table that only displays objects that have a certain value of a non-versioned attribute.

2. GUI oversight: Cannot pick multiple objects and modify their non-versioned attributes all at the same time as you can with versioned attributes.

Both of these represent a loss of functionality that will negatively impact our users compared to their workflow in 3.4.

Thanks,

Mike Foster