About the Event Manager
The Event Manager allows you to check and act on the log messages generated in your Creo or Windchill sessions. You can access the Event Management page by clicking the console status icon in the status bar, or by clicking File > Manage Session > Event management <server>. The Event Management page that opens is the console of the server to which you are connected.
The Event Management page chronologically lists the Windchill PDM events for that server and assists you in viewing and resolving conflicts that arise from PDM events. You can also see the status of a given task and other details related to that task on this page.
The list of events on the Event Management page include workspace events that are recorded as frames. You can set the filter to only view workspace events and their associated frames. The Workspace column of the Event Management table lists the workspaces to which the events and their associated frames belong. You can then select and restore frames. Restoring frames restores the associated workspace events or actions at that point in time. You can also access the detailed information about frames, such as their attributes and related options, in the Event Management page.
Events with frames have the following actions:
• Apply this event
• View additional information
• Lock
• Unlock
These actions are also available in the Event information page action area.
For client messages such as those related to an object download or object check in, you can obtain a set of properties for the task that originated the message. If a task fails, then depending on the type of conflict, you may retry the task using the conflict resolution options.
The following types of messages are displayed by the Event Management page:
• Information/Log—Only for the information of the user. For example, Check Out succeeded.
• Warning—Does not stop you from continuing the operation but you may take further action to correct the issue. For example, if you have defined a designated parameter in the Creo application, but a similar definition does not exist in Windchill, then the upload operation warns you that the parameter and its value will not be passed on to Windchill.
• Conflicts
◦ Overridable Conflicts—The Creo application can override such conflicts by providing you with suitable actions to resolve the conflicts. For example, if an administrator tries to delete an object that has been checked out by another user, then the result is an overridable conflict with an option to retry the delete action from the Event Management page. To override the conflict, the administrator must first perform an undo check-out operation on the object and then delete it from the database.
◦ Non-overridable Conflicts—The Creo application cannot override such conflicts and user interaction is required to resolve them. You must perform some other operation to resolve the conflict. For example, if you try to upload an object that does not have a unique file name, then the upload operation fails and you get a non-overridable conflict.