| Field | Description |
|---|
| Event No.
|
In this field, you can enter the number of the event. The number can consist of both figures and letters. If you do not enter a number yourself, a number will be allocated automatically from the window Number Series.
|
| Event Type
|
In this field, you can specify an event type which can be, for example, a lead, an analysis of customer satisfaction, support, and so on. If the event was created by means of the window Campaigns, the value is copied from the corresponding field in the event template on which the event was based.
|
| Description
|
In this field, you can enter a short description of the event.
|
| Pl. Starting Date
|
In this field, you can specify the date on which the event is to start according to plan.
|
| Pl. Starting Time
|
In this field, you can specify the time at which the event is to start according to plan.
|
| Pl. Closing Date
|
In this field, you can specify the date on which the event is to end according to plan.
|
| Pl. Closing Time
|
In this field, you can specify the time at which the event is to end according to plan.
|
| Start Date
|
In this field, you can specify the date on which the event was actually started. Maconomy suggests the date of the event’s creation, but you can specify an earlier date.
|
| Started
|
In this field, you can specify the time at which the event was actually started. Maconomy suggests the time of the event’s creation, but you can specify an earlier time.
|
| New Job Processing Status
|
In this field, you can specify the job processing status to be assigned to the current job when the event is closed by marking the field “Closed.” You can choose from the options in the option list specified in the job parameter assigned to the current job. However, the status is only updated on the job if the event is not assigned to an event flow. If the event is assigned to an event flow whose event flow status type is the same option list as the job processing status type of the job, the job’s job processing status will instead be updated with the value in the field “New Event Flow Status” in the window Events, when the event is closed.
The job processing status can, for example, be used for indicating the progress of the job or the person or function responsible for the next step. The field “Job Proc. Status” on each line in the table part shows the job processing status assigned to the job when the event in question was closed, allowing you to trace the course of the job processing.
|
| Closed
|
In this field, you specify whether the event has been closed.
When an event is closed, the event can no longer be changed in this window. However, the description of the event can be changed in the table part of the window Events. Closing an event also means that if the event is assigned to an event flow, any new event flow status in the field “New Event Flow Status” is transferred to the event flow to which the event is assigned. Similarly, if the event is not assigned to an event flow, any new job processing status in the field “New Job Processing Status” is transferred to the job to which the event is assigned.
Furthermore, if the event is assigned to an event flow where the field “Create Secondary Events when Closing” has been marked, the closing of the event can cause the automatic creation of new events in the flow in question. For more information on this process, see the description of the field “Create Secondary Events when Closing” in the card part of the window Event Flows.
A closed event cannot be reopened. When an event is closed, Maconomy automatically stops the timer if it is currently activated.
|
| Result
|
This field shows the result of the current event. The result must be an option in the option list specified in the field “Result Type” for the event in question. The result can be specified in the window Events. If the event has been assigned to an event plan, the result can determine whether the current event will cause secondary events, as the event plan may contain templates where a given result is part of the condition for creating secondary events. For a further description of event plans, event templates and conditions for the creation of secondary events, please see the fields “Condition No.” and “Condition Result” in the window Event Plans, as well as the action “Create Secondary Events” in the window Events.
|
| Activity
|
In this field, you must specify the number of an activity which the event concerns. When the action “Transfer to Time Sheet” is selected in the window Events, the registered time consumption is transferred to a time sheet line containing the activity in this field and the job number and task (if any) which the event concerns. If the event has been closed, the time consumption is transferred to the time sheet belonging to the employee of the event which covers the ending date of the event. If the event has not been closed, the time consumption is transferred to the time sheet covering today’s date.
|
| Task
|
In this field, you can specify the number of a task which the event concerns. When the action “Transfer to Time Sheet” is selected in the window Events, the registered time consumption is transferred to a time sheet line containing the job number and activity which the event concerns, and any task specified in this field. If the event has been closed, the time consumption is transferred to the time sheet belonging to the employee of the event which covers the ending date of the event. If the event has not been closed, the time consumption is transferred to the time sheet covering today’s date.
|
| Empl. No.
|
In this field, you can enter the number of the employee who should carry out the event. When using the action “Transfer to Time Sheet” in the window Events, the time consumed is transferred to a time sheet belonging to this employee. When you create an event, Maconomy suggests the employee number of the current user if this user is also registered as an employee.
|
| Name
|
This field shows the name of the employee specified in the field “Employee No.” on the line.
|
| Include Templates
|
If you mark this field, the printout will show the templates assigned to each printed job.
|
