Fundamentals > Working with Windchill Objects > Notes
  
Notes
A note allows you to document additional information for a part, providing a simple method to communicate between design and production. Unlike Windchill documents, notes are authored directly in Windchill and do not have an external authoring application (such as Microsoft Word or Excel).
Notes have the following features and available functionalities:
You can provide attachments for a note and include up to 500 characters in the note text.
A single note can be associated with multiple parts, and a single part can have multiple notes added to it.
Notes can either be created on an individual basis or by using a defined template.
A note is iterative and can progress through life cycle phases.
Notes can also contribute to change processes, allowing you to create change objects from the note information page.
A note can either stand alone or be added to a part or part structure.
The location and manner in which you create or add a note might impact its functionality. Notes can be created in the following locations:
Folder Contents table
Notes created in the Folder Contents table are not immediately associated to a part or part structure. These notes can provide general information, and later be added to one or more parts.
Notes table
Notes created or added in the Notes table can have two types of associations:
Notes Associated to a Part
To directly associate a note to a part, you must create or add the note from the information page of that part. You can create a direct association with either a component part or an assembly part that has lower-level components. The association between the note and part is established in a specific iteration of that part. The iteration must be checked out.
Notes Associated to a Part Structure Usage Relationship
Notes about assembling parts together are associated to the usage relationship between a child and parent part. This is done from the information page of the assembly part, and is only possible for its immediate children (a single-level segment of a more complex structure). The assembly part must be checked out, but it is not necessary to check out the child part.
Because a note added to a part usage relationship applies to the use of a part within an assembly, it does not appear in the Notes table on the information page of the child part.
* 
Create a table view that contains the note status column in the Structure tab on a part information page. The note status icon indicates the existence of notes on parts or usage relationships. For more information about creating table views, see the description of the Views action in Viewing Action Set - Parts.
You can also view the notes associated to an assembly or part structure by generating the Single-Level BOM with Notes report. For more information, see Viewing the Notes for a BOM.
The association between a note and a part is automatically carried forward to any new iterations, revisions, and versions of the part. If a note is modified, the Notes table is automatically updated with the most recent iteration. However, if you create a revision of a note, the new revision does not automatically maintain any previous associations.