Introduction:

This workflow transition action sets the flight details for the inbound flight leg and sends movement messages to the debtor, operator, and trip support provider (if they have email addresses and the 'arrival notification required' field is set)

Example HandlingArrive transition screen:

Configuration

Fields can be made visible or mandatory with the following parameters:

• AtaMandatory (default = true).
  • Indicates if the actual time of arrival must be entered or may be left blank.
• FromStationMandatory  (default = true).
  • Indicates if the origin station must be entered or may be left blank.
• InboundFlightTypeMandatory (default = true).
  • Indicates if the inbound flight type is mandatory.

• InboundPaxMandatory (default = true). 
  • Indicates if the pax count field can be left blank or not
• InboundCrewMandatory- 
  • Indicates if the crew count box must be filled in or can be left blank. The default value follows the application setting IsCrewCountMandatoryUponArrivalAndDeparture. 
• parkingVisible (default = true). 
  • Indicates if parking position field is displayed in the screen.
• sendMovementMessage default = true.
  • Displays and sends an arrival movement message. Note that for the debtor, operator and trip support provider, you can specify if sending a movement message upon arrival and departure is needed.
• departureSectionVisible (default = true)
  • Indicates if the fields are displayed that allow the user to enter updated estimated departure times.
• ShowBaggagePiecesIn (default = false)
  • Adds the possibility of specifying the number of baggage pieces
• OnOffBlocksMandatory=None; 
  • (Default) None of the fields are required to have a value. In the arrival screen, the parking section fields are not required.
• OnOffBlocksMandatory=OnBlocks; 
  • This setting requires the user to enter an on-block date/time after the aircraft has arrived so that the on-block fields are filled in accurately. This setting pre-fills the current date and clears the time part (if any) so users are required to enter a time.
• OnOffBlocksMandatory=OffBlocks; 
  • This setting requires the user to enter the off-block date/time. Before the aircraft departs, both on-block and off-block time fields can be filled in accurately. This setting pre-fills the current date and clears the off-block time (if any) so users are required to enter a time.
• OnOffBlocksMandatory=Both;
  • This setting requires all parking fields to be filled. Before the aircraft departs, both on and off block time fields are required. This setting is expected in the handling depart screen to enforce the on/off block times were entered. This setting would not clear the time parts (if any) were provided during the handling workflow.

• ShowOrderInternalRemarks (default value = false). It can be used to show a text box for entering new order internal remarks when moving the order to the next workflow stage. These remarks are visible only in FBO One screens without being sent to clients.
  eg: ShowOrderInternalRemarks=true;  For example, when moving the order from Confirmed to Arrived, users can update the order internal remarks that will be visible for other FBO One users in the order screen.