| Create Events From Plan
|
When you select this action, Maconomy creates events for those events in the current flow that cause the creation of events according to the event plan selected in the flow. However, the first time the action is run on a manually created event flow, the action creates initial events instead.
For a further description of the concepts of condition results and condition numbers, please see the description of the fields “Condition Result” and “Condition No.” in the table part of the window Event Plans.
In those cases where the above conditions are met, an event is created. Maconomy also creates an event for each event template in the event plan where no condition number and result has been specified, provided that no events have already been created in the current flow based on the event template in question. Maconomy copies the contact person and/or contact company from the event flow to each automatically created event, while contact mode, event type, employee number, starting date and various other information is copied from the event template which, in combination with the basis event, gave rise to the automatically created event.
For an example illustrating how Maconomy finds out whether a given event should cause automatically created events, please see the description of the action “Create Secondary Events” in the window Campaigns.
Please note that since several event templates may have a condition result and condition number that match the same event, the result of one event may cause the creation of several events.
For a further description of the concept of secondary events, please see the section “Introduction to the Contact Management Module” and the description of the window Event Plans.
|
| Close Events
|
When you select this action, Maconomy closes all open events assigned to the current event flow. If the flow is assigned to an event plan, this may cause the creation of events in the flow, as described in the field “Close” in the table part of the window. If one or several of the open events in the flow cannot be closed, for example, because they have open subflows assigned to them, the action is cancelled, and none of the events in the flow are closed.
|
| Transfer to Time Sheet
|
When you select this action, Maconomy transfers the time consumed on each event in the table part to a time sheet belonging to the employee specified on the event in question. Time on a given event can only be transferred if the window Time Sheets contains a time sheet belonging to the employee and covering the closing date of the event if the event has been closed, or today’s date if the event is still open.
For each event in the event flow, Maconomy transfers the value in the field “Accumulated Time” to a new time sheet line with a job number, activity number, dimension values and task corresponding to the information specified in the event. The time consumption is registered on the closing date if the event has been closed and on today’s date if the event is still open.
If there are more than one event with the same combination of employee number, job number, activity number and task, a separate line is created for each event. However, if the field “Duplicate Lines on Time Sheet” has not been marked in the window System Information, multiple time sheet lines with the same combination of job number, activity number, task and dimension values are not allowed, and Maconomy will show an error message if more than one event with the same combination exists.
Please note that since time is only transferred to one day on the time sheet, the maximum number of hours that can be transferred is 24. If the field “Accumulated Time” contains a greater number of hours, Maconomy will therefore show an error message when you use this action.
|
