|Bookshelf Home | Contents | Index | PDF|
This scenario provides an example of a process flow performed by end users. In this scenario, the end user is an event planner who, like the administrator described in Administrator Event Definition Scenario, works for a company holding a user week conference for a software product used by astronomers.
The event planner uses Siebel Events Management to define the event by entering information about the event, such as its name, whether it's a conference or seminar, timing, location, and so on. Typically, the event planner waits until the administrator has defined all of the fields and selections necessary before entering this information. In such cases, the event planner provides the administrator with enough information to define the event fields. However, due to the unusual topic of this event, the event planner decides to work in tandem with the administrator to define the fields and enter the event information.
Events often involve featured topics or themes, such as climate change, water pollution, and the ozone layer. In Siebel Events Management, these are called tracks. Therefore, as part of event definition, the event planner adds any such themes or topics as event tracks. If desired, in order to add additional continuity to the event plan, the event planner also associates related events.
|Siebel Events Management Guide|