Notifications

With the Notifications feature, Vertec can send notifications, automatically notifying users of defined tasks and thus supporting workflows.

In the title line, the bell symbol indicates reminders or tasks that need to be completed (e.g. pending or absences that need to be cleared).

Clicking on the icon opens the list of notifications:

In the list of notifications, you can navigate directly to the desired entry by double-clicking on an individual notification.

• Shift+Doppelklick opens it in a new window
• Use the Trash button to delete a notification directly from the list

Notifications supplied by Vertec

Additional Features are available that implement the following notifications:

• Notifications for activities: A notification with the title of the activity is created if certain conditions are met. If the owner of the activity is changed, the new owner receives a notification and the notification on the old owner is deleted. For
  more information, see Notifications for activities .
• Notifications for absence approvals: As soon as a user enters an absence or changes an existing absence, the team leader receives a notification and it is shown in the Absences subfolder for approval. For
  more information, see Absence Approvals .

• Notifications for monthly approvals: If approvals are missing, team leaders or HR can send reminders to the appropriate users at the push of a button. For
  more information, see Monthly Releases .

Show notifications when starting Vertec

In the system settings under General , you can use the option Benachrichtigungen beim Start anzeigen configure whether the dialog should be automatically shown after login when notifications are present. The default value is False.

If the checkbox is checked, the following dialog will automatically appear after login:

With a double click you can navigate directly to a notification or the dialog with the Schliessen button be closed.

Create notifications

Notifications are created by scripts. For this purpose, two Python features are available on the user, with which notifications can be created, modified and deleted. The notifications are created by the triple of user, category and optional link uniquely identified. If write access to one of the members is missing, the features report an error.

• setnotification(category, text, link): adds a notification with the specified category, text and optional linked object. If the user already has a notification with the same category and linked object, the text will be updated.
• deletenotification(category, link): deletes the notification on the user with specified category and linked object. If no corresponding notification is found, nothing happens. No error message appears.

The notifications are: UserEinträge with the following attributes:

• category is a string indicating the category (type) of the notification. This is freely selectable.
• text is any text that describes the notification and usually also contains information about the linked object.
• link(optional): is a Vertec object (UserEntry). If specified, the notification is displayed with the corresponding icon and the string representation of the object (counterlink: linkedNotifications)
• owner: The user to which the notification belongs (counterlink: notifications)

Example

Double-clicking on the first slope opens the activity for router switching. With the following event script it can be configured that when the checkbox is checked Erledigt on the activity the notification automatically disappears from the list:

Script text:

#
zustaendig = argobject.zustaendig
if zustaendig and argobject.erledigt:
    zustaendig.deletenotification('pending_activity', argobject)

if zustaendig and not argobject.erledigt:
    zustaendig.setnotification('pending_activity', argobject.titel, argobject)

Before completion:

After completion:

User rights for notifications

The rights of the notifications (notification objects) are as follows:

• Read access: The text of notifications can only be read by the owner of the notification.
• Write access: No one has write access. Since notifications are always set via Python method, write access is not necessary.
• The methods setnotification() and deletnotification() for creating and deleting notifications check the read/write access to the bearbeiter.notifications Member.