Leonsoftware Wiki

User Tools

Site Tools

You are here: start » leon » notifications
leon:notifications

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
leon:notifications [2015/07/23 15:24]
rafal 		leon:notifications [2015/07/24 09:30]
rafal [Notification Properties]
Line 10: Line 10:
 For example: you changed STD at 12:00 UTC, then STA at 12:08, ADEP at 12:15, ADES at 12:22 (ADES change was the last one - the notification email about these changes would be sent out at approximately 12:32 (10 minutes after the last change). For example: you changed STD at 12:00 UTC, then STA at 12:08, ADEP at 12:15, ADES at 12:22 (ADES change was the last one - the notification email about these changes would be sent out at approximately 12:32 (10 minutes after the last change).
  
-===== New version =====+===== Notification Properties =====
  
-[{{ :manual:notifications:notifications-main-screen.png?300|Section 'Notifications' - main screen}}]+[{{ :leon:admin-notifications:Notification properties.png?350|Section 'Notifications' - main screen}}]
  
-The **main differences** between the old version and the new one are:+As you can see in the screenshot sthere are number of sections that influence the type of notification and the time when it was sent but also the content of such notification. Main areas of influence are explained below.
  
-<html> +==== Grouping ====
-<span style="color:blue;font-size:150%;">GROUPING</span> +
-</html>+
  
 You can set a notification so that added flights to Leon are grouped. The moment a single flight from the selected group is changed, the notification will include the schedule of all flights from the particular group (including unchanged flights). If more than one flight is changed, one notification will be sent containing information about the changed flights along with other flights from the same group. You can set a notification so that added flights to Leon are grouped. The moment a single flight from the selected group is changed, the notification will include the schedule of all flights from the particular group (including unchanged flights). If more than one flight is changed, one notification will be sent containing information about the changed flights along with other flights from the same group.
Line 41: Line 39:
 Both are separated trips, for different clients. If changes are made to the 1st trip, in the notification email there will be also details of the 2nd trip (as it's on the same aircraft, on the same day). Both are separated trips, for different clients. If changes are made to the 1st trip, in the notification email there will be also details of the 2nd trip (as it's on the same aircraft, on the same day).
  
-<html> +==== Format ====
-<span style="color:blue;font-size:150%;">FORMAT</span> +
-</html>+
  
   * 1. **Simplified HTML** - new flight schedule details, crew codes, status, created by - are all in bold; all changes in flights are in bold; the size of email ~5 kB.   * 1. **Simplified HTML** - new flight schedule details, crew codes, status, created by - are all in bold; all changes in flights are in bold; the size of email ~5 kB.
  
-{{:manual:notifications-new-version:simplified new flight.png?nolink|}}+{{:leon:admin-notifications:simplified new flight.png?nolink|}}
  
   * 2. **Full HTML** - deleted legs appear as <del>crossed out</del>; options are in itallics; the size of the email ~50 kB. Below an example: new flight notification.   * 2. **Full HTML** - deleted legs appear as <del>crossed out</del>; options are in itallics; the size of the email ~50 kB. Below an example: new flight notification.
  
-{{:manual:notifications-new-version:full html new flight.png?nolink|}}+{{:leon:admin-notifications:full html new flight.png?nolink|}}
  
-<html> +==== Displaying changes ====
-<span style="color:blue;font-size:150%;">DISPLAYING CHANGES</span> +
-</html>+
  
-You can now decide how you wish to receive notifications about flight changes. +You can decide how you wish to receive notifications about flight changes. 
  
-When you edit your notifications in the section $$Admin$$ > $$Notifications$$ you can find 3 checkboxes under '**Display changes as**:+When you edit your notifications in this section you can find 3 checkboxes under '**Display changes as**:
  
   * **Bold** - all changes are in bold.   * **Bold** - all changes are in bold.
Line 65: Line 59:
   * **In square brackets** - all changes in normal font, in square brackets.   * **In square brackets** - all changes in normal font, in square brackets.
  
-{{:manual:notifications-new-version:checkboxes.png|}}+{{:leon:admin-notifications:checkboxes.png?nolink|}}
  
 You can combine the above 3 options, i.e. mark all 3 checkboxes, or 2 of them, or just 1 (see examples below). You can combine the above 3 options, i.e. mark all 3 checkboxes, or 2 of them, or just 1 (see examples below).
  
-{{:manual:notifications-new-version:notifications changes.png|}}+{{:leon:admin-notifications:notifications changes.png?nolink|}}
  
-{{:manual:notifications-new-version:changes bold red brackets.png|}}+{{:leon:admin-notifications:changes bold red brackets.png?nolink|}}
  
-<html> +Also when **date of flight** is changed, the notification that is sent in **Full HTML** email format will have **a new date highlighted red** in the flight information table. 
-<span style="color:blue;font-size:150%;">FLIGHT/TRIP</span> + 
-</html>+{{:leon:admin-notifications:Change of date.png?nolink|}} 
 + 
 +==== Flight/Trip ====
  
 You can define what details of either the flight or the trip you want to be included in the notification email. You can add various checkboxes (which represent Leon 3.0 checklist) in sections such as:  You can define what details of either the flight or the trip you want to be included in the notification email. You can add various checkboxes (which represent Leon 3.0 checklist) in sections such as: 
Line 83: Line 79:
 tab **Trip**: Flight, Contract, Notes (notes added in 'PLanned Flights', tab 'Notes') tab **Trip**: Flight, Contract, Notes (notes added in 'PLanned Flights', tab 'Notes')
  
-<html> +==== Positionings ====
-<span style="color:blue;font-size:150%;">POSITIONINGS</span> +
-</html>+
  
 Leon will send a notification email if a positioning duty is added to Leon and the checkbox **Positioning** is ticked in 'Notification' screen (see below): Leon will send a notification email if a positioning duty is added to Leon and the checkbox **Positioning** is ticked in 'Notification' screen (see below):
Line 91: Line 85:
 **30-JAN NEW positioning (EGCC-EGSS)** **30-JAN NEW positioning (EGCC-EGSS)**
  
-{{:manual:notifications-new-version:positioning.png?nolink|}}+{{:leon:admin-notifications:positioning.png?nolink|}}
  
-<html> +==== Trigger for Schedule and Details ====
-<span style="color:blue;font-size:150%;">TRIGGER for SCHEDULE and DETAILS </span> +
-</html>+
  
 **Schedule** **Schedule**
Line 102: Line 94:
 For example, if you want to set trigger time for one day (24h), please enter 1440 minutes. For example, if you want to set trigger time for one day (24h), please enter 1440 minutes.
  
-{{:manual:notifications-new-version:trigger schedule.png|}}+{{:leon:admin-notifications:trigger schedule.png?nolink|}}
  
 All flight details will be sent together with the schedule but notification will be triggered **only** for schedule changes, pax number and flight status. All flight details will be sent together with the schedule but notification will be triggered **only** for schedule changes, pax number and flight status.
Line 110: Line 102:
 Specify how many minutes before scheduled departure time you want to receive reminder email + notifications about further changes in **flight details** (__all except flight schedule__). The typical value here is something short - e.g. 45 minutes (see example below). Specify how many minutes before scheduled departure time you want to receive reminder email + notifications about further changes in **flight details** (__all except flight schedule__). The typical value here is something short - e.g. 45 minutes (see example below).
  
-{{:manual:notifications-new-version:Details change.png|}}+{{:leon:admin-notifications:Details change.png?nolink|}}
  
 <html> <html>
Line 116: Line 108:
 </html><box> **Notes added in available fields, in 'Legs Info' section, will be included in the notification email ONLY if the status of the particular service is NOT set as N/A** </box> </html><box> **Notes added in available fields, in 'Legs Info' section, will be included in the notification email ONLY if the status of the particular service is NOT set as N/A** </box>
  
-<html> +==== Include/Exclude Recipients ====
-<span style="color:blue;font-size:150%;">INCLUDE/EXCLUDE RECIPIENTS</span> +
-</html>+
  
 In the new version you can **include** and/or **exclude** recipients of the partucilar notification. In the new version you can **include** and/or **exclude** recipients of the partucilar notification.
Line 128: Line 118:
 </html> if someone should not get notification emails. </html> if someone should not get notification emails.
  
-Once it's saved, you can see in the field 'People' names __included__ i.e.: {{:manual:notifications-new-version:people included.png?nolink&100|}} or __excluded__: {{:manual:notifications-new-version:people excluded..png?nolink&90|}}+Once it's saved, you can see in the field 'People' names __included__ i.e.: {{:leon:admin-notifications:people included.png?nolink&100|}} or __excluded__: {{:leon:admin-notifications:people excluded..png?nolink&85|}}
  
-Click {{:manual:notifications-new-version:delete.png?nolink&22|}}  to remove names from this section.+Click {{:leon:admin-notifications:delete.png?nolink&22|}}  to remove names from this section.
  
 ===== Managing notifications ===== ===== Managing notifications =====
Line 138: Line 128:
 You can also select a '**Client**' and save a particular notification only for this particular client. You still need to add his email address in the field '**E-mail addresses**', if you want him to receive notification emails. You can also select a '**Client**' and save a particular notification only for this particular client. You still need to add his email address in the field '**E-mail addresses**', if you want him to receive notification emails.
  
-Each notification can be deactivated (simply click {{:manual:notifications-new-version:deactivate.png?nolink&70|}} and save). You will be able to activate it back in the future, if necessary (click {{:manual:notifications-new-version:activate.png?nolink&60|}} and save). Of course, you can completely {{:manual:notifications-new-version:delete 2.png?nolink&60|}} any notification as well. +Each notification can be deactivated (simply click {{:leon:admin-notifications:deactivate.png?nolink&70|}} and save). You will be able to activate it back in the future, if necessary (click {{:leon:admin-notifications:activate.png?nolink&60|}} and save). Of course, you can completely {{:leon:admin-notifications:delete 2.png?nolink&60|}} any notification as well. 
  
 Below you can find various **examples** of notifications, which can be sent out by Leon. Below you can find various **examples** of notifications, which can be sent out by Leon.
Line 144: Line 134:
   * **New flight - schedule only** - no checklist details included.   * **New flight - schedule only** - no checklist details included.
  
-{{:manual:notifications-new-version:example 1 new flight.png?nolink|}}+{{:leon:admin-notifications:example 1 new flight.png?nolink|}}
  
  
   * **Checklist details** - both 'Flight' & 'Trip' checklist items combined.   * **Checklist details** - both 'Flight' & 'Trip' checklist items combined.
  
-{{:manual:notifications-new-version:example 4 checklist.png?nolink|}}+{{:leon:admin-notifications:example 4 checklist.png?nolink|}}
  
   * **Scheduled maintenance** - maintenance added in 'Maintenance' section.   * **Scheduled maintenance** - maintenance added in 'Maintenance' section.
  
-{{:manual:notifications-new-version:example 5 maintenance.png?nolink|}}+{{:leon:admin-notifications:example 5 maintenance.png?nolink|}}
  
   * **Movements** - sent out if 'Flight Watch' details are in the system.   * **Movements** - sent out if 'Flight Watch' details are in the system.
  
-{{:manual:notifications-new-version:example 2 movememnts.png?nolink|}}+{{:leon:admin-notifications:example 2 movememnts.png?nolink|}}
  
   * **Option** - flight status set as 'Option'.   * **Option** - flight status set as 'Option'.
  
-{{:manual:notifications-new-version:example 3 option.png?nolink|}}+{{:leon:admin-notifications:example 3 option.png?nolink|}}
  
   * **Office duty** - either the flight status in 'Edit Flight' is set as 'Office' or a duty added in 'Crew Duties' table has a type defined as 'Office'.   * **Office duty** - either the flight status in 'Edit Flight' is set as 'Office' or a duty added in 'Crew Duties' table has a type defined as 'Office'.
  
-{{:manual:notifications-new-version:example 6 office.png?nolink|}}+{{:leon:admin-notifications:example 6 office.png?nolink|}}
  
   * **Reminder** - enable the trigger for schedule or/and details, define time and tick 'Send reminders'. The email header will appear (screenshot below) and the schedule/details will be included as well.   * **Reminder** - enable the trigger for schedule or/and details, define time and tick 'Send reminders'. The email header will appear (screenshot below) and the schedule/details will be included as well.
  
-{{:manual:notifications-new-version:reminder.png?nolink|}}+{{:leon:admin-notifications:reminder.png?nolink|}}
  
   * **Local time** - tick the checkbox 'Use local time' to get notification emails in local time.   * **Local time** - tick the checkbox 'Use local time' to get notification emails in local time.
  
-{{:manual:notifications-new-version:LT.png?nolink|}}+{{:leon:admin-notifications:LT.png?nolink|}}
  
   * **"From” e-mail address** - all notifications will appear to be sent from this address, so all replies will be directed there. If this field is not filled out, unaccessible mail address do-not-reply@servers.leon.aero will be used instead.   * **"From” e-mail address** - all notifications will appear to be sent from this address, so all replies will be directed there. If this field is not filled out, unaccessible mail address do-not-reply@servers.leon.aero will be used instead.
  
-<box nav-left>[[manual:profile-settings|< Profile Settings]]</box> <box nav-right>[[manual:managing-users|Managing users >]]</box> 
  
  

Page Tools

© 2021 LEON SOFTWARE ALL RIGHTS RESERVED | Leon Software