Event hierarchy
Because the events are organized in a hierarchy, you can catch multiple events at the same time. You select this event in your call to Subscribe or SubscribeAsync.
For example, by catching BluePrint events, you catch both Localize events and Unlocalize events, while catching only Localize events, only those are handled. So, the higher in the class hierarchy you go, the more events are handled by the implemented event handler.
You can subscribe to the following types of events (you can find all of these under the Tridion.ContentManager.Extensibility.TcmEventArgs class, in the Tridion.ContentManager.Extensibility.Events namespace in the API documentation):
- BluePrint events
- User actions that are related to BluePrinting, such as localizing and unlocalizing.
- Taxonomy events
- User actions that are related to classifying and unclassifying items.
- Data modification events
- Typical edits of an item: creating, reading, updating and deleting. This also includes changes to lists of items.
- Publishing events
- User actions that change the published Web site, such as publishing or unpublishing
- Versioning events
- User actions that changes the version of an item.
- Workflow events
- User actions or automated processes that change the Workflow status of an item, or are otherwise related to Workflow.
In addition, one type of event, SessionDisposeEventArgs, is in the Tridion.ContentManager and has Microsoft's System.EventArgs as its direct parent class. (This is because this class is also used internally in the product.) This event type refers to the system event of disposing of a Content Manager Session object, an end-of-life notification triggered by a call to Session.Dispose().