Additional Windchill Capabilities > Service Information Management > About Service Structures > Managing Service Structures > Service Structure Attributes
  
Service Structure Attributes
Service structures and their components have attributes common to many other types of Windchill objects. Information structures and publication structures also have some unique attributes. You can view the majority of these attributes from the following locations:
Details tab on the information page
Attributes tab on the Structure tab of the information page
More Attributes customization of a tab on an information page
The attributes that are visible depend on the type of component and which method you are using to view the attributes. The following two attributes always appear on an information page:
Version — Appears after the object name at the top of the page.
State — Appears at the top right of the page.
Common Attributes
The following common Windchill attributes are generally available on service structure information pages:
Name
Number
Status
Modified By
Last Modified
Description
Item Choices
Authoring Language
The following system attributes are available on the General > More Attributes part of an information page custom tab:
View
Context
Life Cycle Template
Created By
Created On
Location
Team Template
Attributes Unique to Service Structures
Service structures have some unique attributes that you can set when creating a service structure or one of its components. You can then modify these attributes by opening the Edit Attributes window for a component, for example, by selecting Edit Attributes from the Actions menu on an information page.
The following Arbortext Content Delivery attributes are unique to service structures:
* 
Note that you can only view this and other Arbortext Content Delivery related attributes on the More Attributes part of an information page custom tab. You can change these attributes on the Edit Attributes window.
For more information about Arbortext Content Delivery, see About Servigistics InService.
Exclude content from output
This attribute determines whether the content referenced from the component is included in published output. The default is No meaning to include the content in published representations. If set to Yes, the content does not appear in generated output.
This attribute is only available on publication sections, information groups, and all types of content holders.
Exclude title from Table of Contents
This attribute determines whether the title for the content referenced from the component is included in the table of contents for published output. In this case, the content is included in the representation but is not included in the table of contents. The default is No meaning to include the title in the table of contents. If set to Yes, the content does not appear in generated output.
This attribute is only available on publication sections, information groups, and all types of content holders.
Apply title from content
This attribute determines whether the title from the XML content referenced from the component is used in the table of contents for published output. The alternative is to use the name of the content holder. The default is No meaning to include the name of the content holder in the table of contents.
This attribute is only available on a publication section and textual content holder.
Content Attribute and Content Holder Attribute Synchronization
Information in content holders and content objects is synchronized. This includes parts lists, dynamic documents, and documents, along with their content holders.
Changes to one object are reflected in the other object, including the following:
Name
State
Description
Version
Checkout state
Exceptions include the following:
If the lifecycle templates are different, the state is not synchronized.
The description attribute for a dynamic document cannot be edited after creation.
If the content and content holder are not using the same versioning scheme, versioning is not synchronized.
If the content object is a textual content information element, the checkin and checkout states are not synchronized.