Actions

This section shows the Actions available in the Event Flow workspace.

Top Tab

Field	Description
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. Initial Events — The first time you run the action on a manually created event flow, Maconomy creates an event per initial event template in the event plan of the flow and assigns it to the current flow. An initial event template is an event template on which no condition template has been specified. As an event plan can contain several initial event templates, this action can cause the creation of several events in the flow. Maconomy copies the contact mode, event type, employee number, starting date and various other information from the event template in question to each new initial event. Secondary Events — When you run the action on an event flow that is part of a campaign or you select the action for the second time (or more) on a manually created flow, Maconomy will create secondary events for certain events in the current flow. In the description of this process, the term “basis event” is used about any event assigned to the current flow. However, if the field “Include only Closed Events” is marked in the card part of the flow, only closed events in the flow are considered basis events. When the action is selected, Maconomy checks each basis event to see if the event plan assigned to the event flow contains one or several event templates where: The condition number matches the event template number on which the basis event was based, and The condition result matches the result specified in the field “Result” on the basis event in question. No events have been created in the current flow based on the event template in question. 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.
Attach Document to Event Flow	This action allows you to attach a document to the event flow in the card part.
Create Note	Use this action to create a note. Maconomy derives the note type for the note from the event flow type of the event flow. This note’s note number is referenced from the event flow number field.

Bottom Tab

Field	Description
Attach Document to Event	This action allows you to attach a document to the event in the table part.