Custom values (Glossary)

In FBO One, the tables that store products, aircraft and contacts have a default set of properties. These properties are also known as fields or columns.  For example, a contact has a name property, a short name and two address lines.

The need may arise to assign a new property to a table. For example, you may want to add a color property to the aircraft table, or a discount category to the contact table. FBO One allows you to define these custom properties at will. 

Once defined, you can use the value of a custom property to create a special price agreement, or list it in an Excel-based report. For example, you can define those customers that have a ‘disbursement category’ property with a value of ‘8%’ get an 8% disbursement, or you can create a general declaration report that includes the aircraft color. 

Custom properties can be added to the tables containing orders, FBO locations, Administrations, customers/suppliers, products, aircraft and aircraft types.

For each custom property, for example aircraft color, you can define:

  1. The table to which the property applies (in this case, the aircraft type and aircraft registration tables).
  2. A list of allowable values (e.g, red, green and blue), or indicate that the field is a free text or numerically formatted field.

The values for custom properties can be edited using the ‘custom values’ tab. See the example below for the custom values tab of the aircraft screen.

 

Showing the custom property in the Edit screen

The the custom property is configured to apply to a specific table, it will also show up in the Edit screen for records of that table.

For example, to configure a custom property 'Aircraft color' so that it shows up in the Edit screen of the aircraft registration, you have to add the AicraftRegistration table to the list of 'Tables applicable to the custom property' in the administration below:

Once done, the Edit screen for an aircraft shows the new color property as shown below.

 

Example 2 - Custom Value linked to the Order table

At some locations, it may be necessary for a Custom Value to be set on a per order basis. For example, whereby a Handling fee is based on a fare type to be defined per order.
In this example, the Handling fee needs to be calculated based on whether a flight is considered 'Fuel Stop', 'Technical', 'Medical' or 'Standard'. The pre-defined flight types differ from these classifications and therefore an Order Custom Value needs to be created to allow this.
The fare type must be defined by front office users creating and managing the order.

1) Under Administration > Custom Values, a new Custom Value is created called 'Order fare type'.
2) The four values to be available for selection in the order screen have been defined:  'Fuel Stop', 'Technical', 'Medical' or 'Standard'
3) The custom value setup has been linked to the order table. A warning message has been added to prompt users should they fail to select one of the Order fare Types. Finally, the check-box 'Block hand over to the back office if value is missing' has been checked.This ensures that the order does not reach the back office without a front office user having defined an order type.

Note: Under the section marked with a 1 in the above image, the check-box 'Is visible in Order' has been checked so that the selected 'Order fare type' shows in the Order screen:

The created Custom Value now appears in the create/edit order screens

This Order Fare Type Custom Value can be used to define Price agreements. In the below example, Handling price agreements for Handling Category-1 type aircraft have been defined per Order Fare Type (Custom Value).

Now, the Handling fee for the order will be calculated based on the selected fare type (and handling category). 
For the below example, the rate of EUR 160.00 has been applied for Handling based on the 'Order Fare Type' set to 'Standard' and the 'Handling Category' defined for this Aircraft 

 

For as long as the Order remains open in the Front Office, Users may choose to leave the Custom Value blank. The below warning will show, in order to indicate that this value is missing

When no value is set the Order Fare Type will show a ? within the order:

Once the order is to be handed over to the back office, this warning can no longer be ignored, and a user must set a value before the order can be 'Registered' (This optional feature is managed by the setting 'Block hand over to the back office if value is missing' as set during creation of the custom value - see above step 3)

 

Additional Settings:

Icon & Icon Colour:

In more recent versions of FBO One, whereby the New 2017 User Interface is being used, icons and colours may be assigned to each custom value to make them stand out.
Available icons are dependent on those setup under the 'Ops Category Icons' setting in FBO One. Colurs can be inserted as HTML Colour codes 

Example:

Is free-hand text field:

This allows for free-hand text to be added in the Custom Value field. A default text may still be assigned using the 'Default Custom Value' setting, but additional text may also be added.
In the below example, a set of default notes pertaining to Landing Permits should be shown in the Order screen and when confirming handling to the client (setup to show in Handling Confirmation email), however this text on occasions, needs modifying. This free-hand option allows users to add / remove text as necessary.

Input Box Height (Lines):

This setting defines how many lines should show by default during input of the value (for multi-line custom values)

Example 1:
Input Box Height setting: 3 Lines

 

Example 2:
Input Box Height setting: 8 Lines

Display box max height (Lines)

This setting defines how many lines should display by default (for multi-line custom values) on the Order screen - this only applies for display within the 2017 UI

Example 1:
Input Box Height setting: 1 Line

Example 2:
Input Box Height setting: 3 Lines



See also:

Export values (Glossary)

Custom values (Administration)

Custom value (Fields)

How to use custom values in price agreements

Using custom values in reports and email templates