Data Management Capabilities > Managing Change > About Change Notices > Creating a Change Notice
  
Creating a Change Notice
You can create a change notice in the following ways:
• Select New > New Change Notice from the actions menu on the information pages of objects that can be changed, such as parts and documents.
• Select New > New Change Notice from the actions menu on the information pages of change requests
• Select New > New Change Notice from the toolbar or row action menu of the Folder Contents table, available from Products or Libraries.
• Select New Change Notice from the toolbar of the Change Notices table.
• Click New Change Notice on the toolbar of the configured Variant Baselines table on the part information page.
* 
The action is disabled if the Impact association rule is not created.
• Click New Change Notice on the shortcut menu displayed in the configurable module pane in Matrix Editor.
* 
If your administrator has configured your change process to allow creation of change notices without the authorization of an approved change request, you can select New Change Notice directly from the actions list of the object you want to change, without having to first create a change request. See Automatically Creating a Change Notice from a Change Request.
If your site has security labels enabled, you may see the Set Security Labels step. For more information about setting security labels, see Setting Security Labels while Creating an Object
In the event that the context is not known, you may have a Set Context step preceding the following steps:
1. Set Attributes—Identifies change notice attributes that determine its identity and control its behavior. A checkbox, controlled by a preference, may allow you to propagate information from the change request.
If a valid change notice template exists, you can create a new change notice from a change notice template. From the Template drop-down menu, select the change notice template you want to use. The change notice template attributes, change notice template attachments, and change task templates are propagated to the new change notice.
* 
Depending on your system configuration, you may get default attachments from the change notice template or the associated change request.
2. Define Implementation Plan—Identifies the tasks necessary to satisfy the change notice. A default change task is created when the New Change Notice window is launched for the first time.
3. Set Attachments—Manages associated file attachments. Files in the context of the change notice can be added, updated, deleted, or viewed.
4. Select Associations—Identifies associated process and reference objects.
* 
• Steps do not necessarily need to be completed in the order in which they are listed. You may navigate to any step for which the link is enabled.
• A message displays asking if you want to Submit Now or Submit Later. You might want to consider submitting later if there is a chance that you might want to modify the change notice before submitting it into the workflow process.
Related Topics