Event Management Utility
Event Management allows you to check and act on the log messages generated in your Windchill Workgroup Manager or Windchill session. You can access the Event Management page by clicking the console status icon in the status bar, or by clicking > and then clicking the server name.
The Event Management page chronologically lists the 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.
For client messages, such as those related to an object download or object checkin, 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 utility:
• Information/Log—Messages that pertain to status of an event, such as Check Out Succeeded.
• Warning–Messages that indicate a possible problem. Warning messages do not stop you from continuing the operation, but you may need to take further action to correct the issue.
• Conflicts–Messages that indicate that a conflict has occurred. There are two types of conflict messages:
◦ Overridable conflicts—Windchill Workgroup Manager 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, the result is an overridable conflict with an option to retry the delete action from Event Management. To override the conflict, the administrator must first perform an undo checkout operation on the object and then delete it from the database.
◦ Non-overridable conflicts—Windchill Workgroup Manager 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.