Displaying Attributes in Common Space...

[closer9]

Hi, I'm trying to set up the display table for my Common Space, but when I add the attributes that I want to the table I get just two hyphens. The only "user defined" attribue that will populate is "drawn by", which has a default value...

Am I overlooking something?

 

[Hora]

Set the state of your attributes to "DESIGNATED". Only then you can see them in Intralink.

-Hora

 

[closer9]

Well, that's what I thought, but when I try to save with Designate checked I get an error saying its not among those filebased in Ilink. I have them all under "Object Attributes" in Admin, but still get the error. Where in Ilink am I supposed to "filebase" them?

thanks...

 

[closer9]

I still can't get this to work. Whenever I "designate" something I get an error, even though I've added to them admin. Where in admin do I need to add them?

thanks...

 

[Tofflemire]

Hi Closer9

In Admin, go to object, object attributes. Create your user made parameters there. Fill out Name which is your user defined parameter (type it exactly as it is in your part/assembly). Make sure you set the type eg string or Integer... I also set Versioned/filebased.

Tofflemire

 

[closer9]

Tofflemire,
That's what I've done, but I still have problems when I click on designate...

 

[closer9]

Also, how do I get the view I created in Workspace to become the default, so I don't have to select it each time I open Workspace?

thanks...!

 

[Tofflemire]

Hi Closer9

Go into Preferences, Configurations, under browser pick Workspace and pick your view you want as default. You set different view for each of the list in the browser, I have many set like one for locate...

Tofflemire

 

[closer9]

Thanks. Got the view to stay, but still can't get anything, but two dashes in the columns... I'll keep trying though...

 

[Tofflemire]

Hi Closer9,

Do you have any other user defined parameters created inside of your part or assembly that are not created in Admin Intralink? If so these are what giving you an error. The pop up error window states what parameters are not defined in Intralink. You can uncheck undesignate the items so you do not get that error if you do not want to have that parameter in Intralink.

Tofflemire

 

[closer9]

I have 6 user defined parameters in my parts. Nothing at the moment is checked (designated), and all of them are in admin under object attributes. The only one that will show up in the Workspace when checked (designated) is the one that has a default value. If I check any other I get an error saying its not in Intralink...

 

[closer9]

Hey, I got it!

I switched from versioned to versioned/file based... Now I just wish I knew what that meant.

I gotta take the time I guess to just browse PTC's website someday. I know the book would probably be a foot thick, but I wish they PTC put out a print manual for these programs... Maybe I need to find an Intralink book somewhere. Can anyone recommend something?

I'm using ILink 3.4, BTW...

 

[Tofflemire]

Hi closer9

I copied this for you from my Intralink Help. It may help explain Attributes to you.

Attributes
Because there can be a large number of versions of one object, there needs to be a way to uniquely identify each object version. To account for this, Pro/INTRALINK allows you to set specific properties called attributes for each instance of an object. These attributes include Object Name and Type, Branch, Revision and Version. The following seven objects can have attributes associated with them:

Branches

Baselines

Dependencies

Folders

Users

User Groups

Pro/INTRALINK Objects

Attribute Characteristics
You can set whether a Pro/INTRALINK object versioned attribute is filebased and therefore shared with Pro/ENGINEER. You can, additionally, set the following characteristics for user defines attributes.

Value Type—You can define an attribute value to be as a string, integer, floating point, date, or Boolean

Values—For an attribute, you can specify a range of valid values or an enumerated list of valid values or you can specify None. Selecting none would result in the attribute having no restrictions.

None—No restrictions

Versioned, Non-Versioned, and Lifecycle Attributes
Object attributes can be defined as one of three types: versioned, non-versioned, or lifecycle. Versioned attributes can contain a different value for each versions of an object. Non-versioned attributes, on the other hand, contain only one value for all versions of the object. Versioned attributes can only be modified in Workspace and non-versioned attributes can only be modified in Commonspace. A new version of the object is created each time you change a versioned attribute.

A third type of attribute is called a lifecycle attribute. Lifecycle attributes contain characteristics of both versioned and non-versioned attributes. Lifecycle attributes are similar to versioned attributes in that each version of an object can contain a different attribute value. Lifecycle attributes are like non-versioned attributes in that they are modified in Commonspace and when you change a lifecycle attribute, a new version of the object is not created. Lifecycle attribute values cannot be modified if an object is locked.

Release Level is a special lifecycle attribute. You can modify the release level of a new object in the Workspace by selecting Object > Modify. This command can only be used to set an initial release level or to lower the release level of an object. When you change the release level of an object in Workspace, a new version is created. This enables you to start a new design based on an existing object.

Filebased Attributes
By default, versioned attributes are accessible in a linked Pro/ENGINEER session. These are called Filebased attributes. You can, however, define a versioned attribute to not be shared with Pro/ENGINEER.

When working with instances or generic objects, you can set Filebased attributes only from within Pro/ENGINEER. For all other objects, you can set Filebased attributes either in Pro/INTRALINK or in Pro/ENGINEER.

Note: Non-versioned attributes and lifecycle attributes are, by definition, not sharable with Pro/ENGINEER.

Sharing Attributes with Pro/ENGINEER
Filebased object attributes can be shared with Pro/ENGINEER. All properly named attributes are automatically loaded and saved by a Pro/ENGINEER session that is linked to a workspace. In order to be compatible with Pro/ENGINEER, attribute names must be all lowercase except for the first letter and any letter following an underscore. For example, Height, Length1, and Base_Cost are all valid, while width, 2Length, and User_value are not. Pro/INTRALINK automatically converts incorrect names to the correct format. The attribute name can be up to 31 characters long.

Tofflemire