Setting Service Preferences
You need to be familiar with Windchill administration, including managing preferences. For more information, refer to the Administering Preferences section of the Windchill Basic Administration Guide.
The Windchill Service Information Manager installation sets the defaults for these preferences. It’s not likely you need to change them. However, you can follow this procedure to check the defaults or change them if necessary.
1. Locate your product in the Navigator.
2. Open the Utilities folder and choose Preference Management.
3. Find the specified category (as explained following this procedure) and expand it to view the preferences.
4. Right-click on the preference name and choose Set Preference.
5. Enter or change the preference value and click OK to save it.
The following preferences are required for a service product:
• In the Add to Baseline category, Collector sub-category, find the Include related CAD / Dynamic Documents preference.
Set the value to All to allow users to specify the documents which are added to collected parts and check the Locked box.
• In the Options and Variants category, find the Configurable Module Support preference.
Set the value to Yes to enable Assemble to Order features, and check the Locked box.
• In the Part Management category, find the Default Part View preference.
Set the value to Service and check the Locked box.
In addition, you can check the values for preferences in these categories:
The Arbortext Category
• Customizations Folder
You can deploy a zipped custom application using the Customizations Folder preference.
Specify a path to a folder that contains Arbortext customizations in a zip file. Arbortext Editor uses a URL specified by the APTCUSTOM environment variable to locate it.
• Source Language
Set to the locale by default.
The Save As Category
Preferences in this category control the saving of objects and their related objects with a Save As action.
• Display collected objects
Controls the default display of objects that are set to be collected with an object being saved from the Save As window. The default setting is As a List.
This option is available in the From Commonspace Collector and From Workspace Collector sub-categories.
This preference can also be set for other common actions, in these preference categories:
◦ Delete action — see Delete category, Collector sub-category
◦ Move action — see Integral Operations category, Move Collector sub-category
◦ Revise action — see Revise category, Collector sub-category
• Use Location of Source Object
Specifies the location where new objects created using save as and replace with local copy operations are stored. The default setting is Yes, meaning to store the new object in the same context as the object from which it was created. Set this preference to No, and new objects created by these operations are stored in the root folder of the context in which they are created. Note that if you use the Windchill Service Information Manager General Product template to create your context, the value of this preference is set to No automatically.
The Service Information Management Category
• Enable Information Structure Support for Check-in
Supports Windchill Workgroup Manager using Windchill Service Information Manager features. Setting the value of Enable Information Structure Support for Check-in to yes enables the ability to associate Creo Illustrate and Windchill Arbortext IsoDraw illustrations with an information structure during the Windchill check-in process. See the Windchill Workgroup Manager documentation for additional information.
• Include empty information groups and publication sections when generating from template
Controls whether to allow empty groups and sections to be copied when generating and regenerating service structures from a template. The default configuration is set to No to exclude empty nodes. This does not apply when generating a publication structure from an information structure.
• Information Structure Search Types List
Specifies the types listed in the Search On field when inserting content. By default, it’s set to Document, Dynamic Document, and Parts List when choosing Insert Existing Information Element.
The object type’s fully qualified name must be supplied; for example, com.ptc.arbortext.windchill.softtypename.
• Information Structure Soft Type
Specifies the soft type for information structures created when a service product is created. Set only if using a custom information structure soft type.
• Publication Structure Search Types List
Specifies the types listed in the Search On field when inserting content. By default, it’s set to Dynamic Document and Parts List when choosing Insert Existing Information Element.
The object type’s fully qualified name must be supplied; for example, com.ptc.arbortext.windchill.softtypename.
• XLIFF Soft Type (Optional)
Specifies the soft type for .xlf dynamic documents created when the user chooses Generate Translation Document. Set only if using a custom XLIFF soft type.
• Structure Population
Controls the configuration settings for the structure population feature in service structures.
◦ Create Group or Section preference creates a group or a section if it does not exist in the structure.
◦ Use the Configuration file location preference to specify the location of the configuration file for structure population. If the value for this preference is empty, the Populate Structure action will be disabled on the user interface.
• Create Primary Information Structure on Product Creation
Controls the creation of a primary Information Structure root when a product is created using the Service Information Manager General Product template. By default, it is set toNo.
The Service Parts Category
• Automatic Update Notification
Controls the Update Required notifications generated for parts lists associated with an SBOM.
When the preference is set to Yes, the Update Required status is assigned to all parts lists associated with an SBOM after any change to the SBOM is made.
When set to No, changes to the root node of the SBOM are ignored. A parts list associated with the SBOM will not be marked as Update Required following a change to the root node of the SBOM.
The default value is Yes.
• Default Parts List Type
The default value is com.ptc.arbortext.windchill.partlist.PartList, but this can be changed to any sub type of parts list.
• Enable Default Unit Editing
Specifies whether the value of the Default Unit attribute can be edited in the Items tab of the Parts List Editor.
|
|
Default Unit is a part attribute. It cannot be applied to a usage of the part in a specific parts list. A change to the value of Default Unit perpetuates to all uses of the part.
|
• Excluded Part and Dynamic Document Subtypes
Specifies item types that should not be available for selection when creating an attribute filter for a parts list.
List the excluded types by their internal name, in a comma separated list.
• Illustration Source Folder Location
Specifies a folder location in the current container to output the Illustration Source objects (Graphic Dynamic Documents/GDDs) generated when creating parts list illustrations from the Parts List Editor.
When the preference has a value, GDDs for the parts list and illustrations generated from the Parts List Editor are output to the specified location.
By default, the preference is blank —generated GDDs are hidden.
|
|
Folder locations defined in any OIRs configured for GDD/EPMDocument are disregarded when this preference has a value. Folder locations defined in publishing rules are also ignored, since publishing rules are not used to generate an illustration from the Parts List Editor.
|
This preference is not analyzed when creating parts list illustrations using Windchill Workgroup Manager.
• Include / Associate Non-Serviceable Parts to Parts Lists
Determines if non-serviceable parts are included in parts lists automatically generated from SBOM parts (see above).
The default value is Yes.
Note the following implications of each of the possible values:
◦ If set to Yes:
▪ All the parts available under the Part are automatically added to the Parts List, even if they are marked non-serviceable (if the value of the Serviceable attribute is No).
▪ Both serviceable and non-serviceable parts are included in the Parts List when the Serviceable attribute is set to Yes, No or Null.
▪ The value of the Serviceable attribute for a resulting Parts List Item corresponds to the value of the Serviceable attribute set for the Part. If the attribute was not set for the Part, the attribute has a value of Yes for the Parts List Item.
◦ If set to No:
▪ Only parts that are serviceable (Serviceable attribute is set to Yes) are added to a Parts List.
▪ Non-serviceable (Serviceable attribute set to No) parent parts are included if they have serviceable child parts.
▪ Non-serviceable child parts are not included in the Parts List.
▪ If both the parent part and its children are non-serviceable, the Generate Parts List action is disabled in both menu options.
▪ Parts whose Serviceable attribute is set to Null are classed as serviceable, and are included in the Parts List.
• Item Number From Template
Determines how Item Number values are generated for the items in a product parts list generated from an information structure template
The default value is Yes.
◦ Yes — Item Number of original configurable parts is used as the Item Number for the parts list items in the product parts list
◦ No — new Item Number values are generated for the parts list items in the product parts list
• Parts Lists Auto-Regeneration
Specifies how spare part parts lists are regenerated after an update to their source generic parts list (template).
The default value is No.
◦ Yes — spare part parts lists are regenerated automatically when the update to the generic parts list (template) is complete.
◦ No — spare part parts lists can only be regenerated as part of a Regenerate action from the information structure.
• The Save As sub-category
Preferences in this category control the saving of parts lists and related objects with a
Save As action. Refer to
Saving Parts Lists as New Objects for further information.
◦ The Collector sub-category
▪ Display collected objects
Controls the default display of objects that are set to be collected with an object being saved from the Save As window. The default setting is As a List.
▪ Include related Illustrations
Determines which of the illustrations associated with a parts list are collected by default when the parts list is saved as a new object. The default setting is None.
▪ Include Related Service Objects
Determines which of the service objects associated with a part are collected by default when the part is saved in a service structure. The default setting is None.
◦ Inherit FileName from Name
Controls how the file name of a new illustration created using the Save As command is assigned. The default setting is No, meaning that a prefix and a suffix are applied to the original file name to produce a new name. The additions are controlled by the Illustration Filename Prefix and Illustration Filename Suffix preferences.
If this preference is set to Yes, the new file name is set to the same value as that of the new illustration, plus an appropriate extension.
◦ Inherit FileName from Number
Controls how the file name of a new illustration created using the Save As command is assigned. The default setting is No, meaning that a prefix and a suffix are applied to the original file name to produce a new name. The additions are controlled by the Illustration Filename Prefix and Illustration Filename Suffix preferences.
If this preference is set to Yes, the new file name is set to the same value as the number of the new illustration, plus an appropriate extension.
◦ The Naming Patterns sub-category
Preferences in this sub-category set the pattern for prefixes and suffixes added to the file name, number or name of parts lists and their associated illustrations when they are saved as new objects with a Save As action. Settings made here apply when preferences such as Inherit FileName from Name are not enabled.
◦ Save Selected Objects Only
Defines what objects are saved when a parts list is saved as a new object with a Save As action. The default value is No, meaning that both selected and dependent objects are saved.
If the preference is set to Yes, only selected objects are saved. Dependent objects are reused.
◦ Use Location of Source Object
Specifies the default target location for new objects generated when a parts list is saved with a Save As action. The default value is Yes, meaning that the new object is saved in the same folder location as the original source object.
Set the preference to No to save new objects in the root folder of the context in which the Save As action was taken.
