Notification Configuration Properties
The wt.properties file includes the wt.notify.subscriptionConfigFiles property. This property contains all the supported subscription configuration files and their location. The default file can be found at:
<Windchill>/codebase/wt/notify/subscriptionConfig.xml
* 
Changing the subscriptionConfig.xml file is not recommended.
The XML specified in the file contains the following sections:
Type to Events
This section lists all events that the Notification Policy Manager must subscribe to and listen for.
This section applies to both notification rules, as well as the events that appear as options to users when creating a new subscription.
Category to Events
This section applies only to user subscriptions and lists the events associated with each subscription category. Categories include one or more events, and provide a way to group related events in order to simplify the subscription user interface.
Each category includes the following information:
Resource Name—The path of the resource bundle.
Subscription Type—Specifies whether the associated category is for an object-based subscription or a context-based subscription. The value can be either Object or Context. If the subscription type is not specified, the associated category is for both object-based and context-based subscriptions.
If the subscription is not for the type specified, then the given category is not displayed. For example, if a user subscribes to a specific document (which is an object-based subscription) and the category NEW_OBJECT has Context set as its subscription type, then NEW_OBJECT is not displayed as an available event category.
Exclude Type—Specifies which object types are excluded from the event category. This includes types that have a parent/child relationship with the specified object type.
Override Type—Specifies the object types to which the event category applies. If one or more override type values are specified for a category, the category is only displayed for objects of those types for object-based subscriptions, and only displayed if one of those types is selected for context-based subscriptions.
If no override type is specified, the object types associated with a category are determined by the Type to Events configuration as well as any other existing configurations in the Category to Events section.
Migrated Event to Category—This section is used if your system is being upgraded. During the upgrade of your system, all specified subscription events are converted to subscription categories.
Was this helpful?