This article is about adding, enabling and editing event types.
Dozens of different Event types already exist on the Nepton service. This guide describes how to add, enable, and edit new event types directly in the service, for example, if you need to get a name for an event type that differs from the default event types. Guidance also describes how the visibility of the event types is managed.
The configuration is made in the menu Work time > Administration > Working community settings > Work hours > Event types.
Click Add Event Type.
Enter a name for the new event type. This text will appear in the event list when a new event is added or an event is edited.
Enter a code for the event type. The code should be the same as the salary type code. The code is used in integration rule sets.
Select the behavior for the event type, i.e. how the calculation with the new event type is performed. For example, if you select work as the behavior, the new event type behaves computationally in the same way as the work event type.
At the moment it is not possible in the service to create an event type from Travel invoice so that it would include the supplements and calculations of a Travel invoice.
When all the fields have been entered, click Save.
Editing an event type and setting it's visibility
When a new event type is added, it will appear in the list. The listing is in alphabetical order. The new event type must be activated at either the Working community settings level or the Setting groups level, depending on how widely the event type is used in the work community (i.e. the new event type can be visible and selectable to all or only to a specific group). Activation of the event type is done by ticking the selection (at the Working community settings level) or by selecting the "Yes" option from the menu (at the Setting groups level).
The removal of event type visibility is done by removing it from use. This does not affect the history of created events. This prevents new events being created with this event type.
The setting is saved from the Save button at the bottom of the page.
Working community settings options:
Setting groups options:
At the working community settings level, the pen image in front of the event type indicates that this is a new event type added directly to the service, not a standard transaction type. At the setting groups level, this is indicated by the * sign. From the pen image, you can also edit event type information and behavior. Event types can only be edited at the Working community settings level.
Defining an event type for shift planning
The event type can be set to appear in the shift planning. The event type is activated by checking the 'Show in planning view' option.
Note! The event type is displayed in the planning view after the activation is done and saved. Old events created before activation are not automatically updated in the planning view. If the old event is modified after activation, then it will be updated in planning.
The name, code, and behavior of an existing event type can be modified in the listing on the left with the pencil button. Only the Working community's own event types can be edited.
Changes made here also have a retroactive effect - if you want the changes to take effect only from today, you must create an entirely new event type instead of editing it and change the deployment settings for both event types in both the working community settings and each of the setting groups.
If the event type you are editing has the same behaviour as one of the types listed in behaviour selection, it will be shown as behaviour:
The default event type when creating a new event
When creating a new event, "Job" is always entered in the event type menu by default. This can be changed to any of the available event types in either the working community settings level or setting groups level settings in the Work hours -> Event types section:
If, for example, it is necessary to create an event only to display a certain type of event by default on certain days, it can be done via the validity function (small calendar button after the setting) with an exception setting, e.g. as follows:
In the example above, on Saturdays and Sundays, the Remote work event type is selected by default. For more information on all possible exception configurations that can be used in Nepton, see Configure Exceptions to Settings.