Leonsoftware Wiki

User Tools

Site Tools

You are here: start » leon » settings-handling-requests
leon:settings-handling-requests

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
leon:settings-handling-requests [2018/03/19 08:54]
bartek [Sending rules] 		leon:settings-handling-requests [2021/12/03 10:03] (current)
rafal [Attach documents by default]
Line 1: Line 1:
 ====== Handling requests ====== ====== Handling requests ======
 +<box tutorial>[[videos:getting-started:step-4.-handling-requests|Video tutorial]]</box>
 +
 +
  
 This tool allows you to configure default handling requests and GAR patterns which will be used in preparing and sending emails to handling agents or GAR offices (see [[leon:handling-requests|Handling Requests]] and [[leon:gar|GAR]]). This tool allows you to configure default handling requests and GAR patterns which will be used in preparing and sending emails to handling agents or GAR offices (see [[leon:handling-requests|Handling Requests]] and [[leon:gar|GAR]]).
Line 9: Line 12:
 A tab **Settings** is divided into a few sub-sections desribed below. A tab **Settings** is divided into a few sub-sections desribed below.
  
-==== General Settings ====+==== General settings ====
  
-  * **Opr ICAO** - an operator code which needs to be recognize by Eurocontrol in order to get flight times imported to Leon. +  * **Operator name** - it will appear on Handling Requests sheet, next to Flight No. & Aircraft.
-  * **MyHandling GUID** - This id is required if you want to integrate Leon with MyHandling software. If you are an existing customer of Leon Software, please contact MyHandling support (contact@myhandling.com) in order to obtain this identifier. For more information check a section [[leon:handling-requests|Handling Requests]]. +
-  * **HR available** - this checkbox must be ticked to enable sending out HR emails.+
   * **Test settings** - if marked, HR will be sent to user's email address instead of handling agent.   * **Test settings** - if marked, HR will be sent to user's email address instead of handling agent.
   * **Approval date** - if the approval date of handlers/fbo expires in less than 14 days, Leon will send an email to the inserted email address.   * **Approval date** - if the approval date of handlers/fbo expires in less than 14 days, Leon will send an email to the inserted email address.
Line 20: Line 21:
 <box>We strongly recommend making a thorough familiarisation with 'Handling' module by using **'Test mode'** to avoid mistakes or confusion.</box> <box>We strongly recommend making a thorough familiarisation with 'Handling' module by using **'Test mode'** to avoid mistakes or confusion.</box>
  
-**Matching flights**+==== Matching flights ====
  
 Including options by default when matching flights in HR Sheet when sending an email to a handling agent. Including options by default when matching flights in HR Sheet when sending an email to a handling agent.
  
 +==== Callsign ====
 +
 +[{{ :leon:settings:handling-requests:HR_example.png?240|Example of callsign use}}]
 +This configuration allows you to choose one of three options: 
 +
 +  - **Flight number** - in a Handling Request the original flight number is used, as specified for the particular flight. It is the default setting. 
 +  - **Operator IATA** - if the flight number begins with the ICAO designator, it is replaced by IATA code in the Handling Request message.
 +  - **Operator ICAO** - if the flight number begins with the IATA code, it is replaced by ICAO designator in the Handling Request message. 
 +
 +An example of the Handling Request with "Operator IATA" set in the Handling Request configuration presented in the screenshot on the right-hand side. ICAO designator "YYY" is replaced by IATA code "T7".
 +
 +Both codes must be defined in the operator's General Settings.
 +
 +{{:leon:settings:handling-requests:Callsign setting.png?nolink|}}
 ==== HR status changes ==== ==== HR status changes ====
  
Line 103: Line 118:
  
 Transport to/from HOTAC Transport to/from HOTAC
-^          Billing Info           ^ +
-Please forward all invoices to: address, VAT No., Company Reg.+
 ^  Footer  ^ ^  Footer  ^
 Please provide us with an estimated cost and email your confirmation to @email or fax @fax . Please provide us with an estimated cost and email your confirmation to @email or fax @fax .
Line 113: Line 127:
  
 ---- ----
 +==== Attach documents by default ====
  
-At the bottom of the window, you can tick a checkbox **Attach GenDec** to add General Declaration document to Handling request email.+Here you can select the documents that should be attached to the Handling request by default.
  
-----+The documents listed are the documents with 'Handling Request Manifest' and ' General Declaration' types.
  
-==== Default requested items ====+Once the documents are selected, they will be automatically ticked in the HR email, as per the below screenshot:
  
-[{{ :leon:settings:HR items per aircraft.png?150|Default requested items per aircraft}}]+{{:leon:settings:handling-requests:attach_default_hr_dcuments2.png?nolink|}}
  
-In the settings you can also define the **Requested items** which will then show in the Handling Request email by default. +----
- +
-It is also possible to assign the Handling Request **default requested items to a specific aircraft**. +
- +
-Any changes made to the list of requested items will only apply to the newly added flights and not the existing flights. +
- +
-The items per aircraft will overwrite the operator default requested items in Handling Request email. +
----------+
  
 ===== Sending rules ===== ===== Sending rules =====
Line 139: Line 147:
 By clicking a link **Add rule** you can select the aircraft registration, an airport, whether HR emails should be sent or not and the order. By clicking a link **Add rule** you can select the aircraft registration, an airport, whether HR emails should be sent or not and the order.
  
-[{{ :leon:handling-requests:sending rules.jpg?200|Defining of sending Handling Requests emails}}] +[{{ :leon:handling-requests:sending rules.jpg?200|Defining Handling Requests email sending for the fleet}}] 
-{{:leon:handling-requests:sending rules pop up.jpg|}}+{{:leon:handling-requests:sending rules pop up screen.jpg|}}
  
 If for a particular airport there should not be sent any HR emails at all, leave aircraft field as 'Select' - Leon will show **Any** in the column 'Registration'. In such case, when adding a new flight to the airport where it is defined that no HR email should be sent, in a tab 'Checklist' Leon will show handling's status as 'Not Applicable' and will not select any handler. Also, when hovering the mouse over the 'Note' icon, Leon will show an information:"Handling is not required on selected airport for current aircraft". You can, of course, still select a handling agent manually and send HR email, if necessary. If for a particular airport there should not be sent any HR emails at all, leave aircraft field as 'Select' - Leon will show **Any** in the column 'Registration'. In such case, when adding a new flight to the airport where it is defined that no HR email should be sent, in a tab 'Checklist' Leon will show handling's status as 'Not Applicable' and will not select any handler. Also, when hovering the mouse over the 'Note' icon, Leon will show an information:"Handling is not required on selected airport for current aircraft". You can, of course, still select a handling agent manually and send HR email, if necessary.
 +
 +{{:leon:handling-requests:sending rules note.jpg|}}
  
 The **order** defines which setting is more important if it comes to defining the rule for the same airport.  The **order** defines which setting is more important if it comes to defining the rule for the same airport. 
  
-For example, no HR emails should be sent to EGGW, apart from the aircraft A-BCDE - the order for A-BCDE should be higher then for 'Any' rule, so that sending HR emails for this tail is enabled. It is not possible to add the same order to 2 different rules. If you try to do so, Leon will **increase** the order to already defined rule.+For example, no HR emails should be sent to EGGW, apart from the aircraft A-BCDE - the order for A-BCDE should be higher then for 'Any' rule, so that sending HR emails for this tail is enabled. It is not possible to add the same order to 2 different rules. If you try to do so, Leon will change the order of previously added rule (either increase it or decrease it, depending on numbers of rules and order-number you add). 
 + 
 +---------- 
 + 
 +===== Requested items ===== 
 + 
 +[{{ :leon:settings:HR items per aircraft.png?150|Default requested items per aircraft}}] 
 + 
 +In the settings you can also define the **Requested items** which will then show in the Handling Request email by default. 
 + 
 +It is also possible to assign the Handling Request **default requested items to a specific aircraft**. 
 + 
 +Any changes made to the list of requested items will only apply to the newly added flights and not the existing flights. 
 + 
 +The items per aircraft will overwrite the operator default requested items in Handling Request email. 
 +--------- 
 +===== Billing Info =====
  
 +[{{ :leon:settings:handling-requests:billing-info.png?200|'Billing info' tab view}}]
  
 +This section is divided into two sections:
  
 +  * **Default** - information inserted here will be displayed by default in the 'Billing info' section in the 'Handling request' email.
  
 +  * **Billing info specified per aircraft** - information from this section will be displayed in Handling Requests as Billing Address and it will overwrite information from the 'Default' section. It is useful if you want to use the information that is different from the default for the rest of your fleet (i.e. owner's address). 
  
  
 +-------------------------
  
  
  
leon/settings-handling-requests.1521449687.txt.gz · Last modified: 2018/03/19 08:54 by bartek

Page Tools

© 2021 LEON SOFTWARE ALL RIGHTS RESERVED | Leon Software