Access Roles: Operations Filter by Aircraft

Users > User Settings > Access Roles; and
Users > User Search > {select user} > Change Role (button)

Access Role aircraft filters (Managed Aircraft and Vendor Aircraft) are now enforced across Operations pages so users with limited aircraft access only see and select aircraft they are authorized to view in that area of Avianis.

• Trip Search, Flight Leg Search, and Feasibility Search respect aircraft filters
• Trip/Quote Create and Trip page aircraft drop downs show only permitted aircraft
• Ops Board and Fleet Map display only aircraft the user is permitted to see
• Access Role edit page shows a "filtered by" indicator with aircraft icon for Trips + Operations Management pages

Access Role permission now with Aircraft filtering

Aircraft filters on the user profile

FlightBridge Updates

Operations > Trip > Service Requests

FlightBridge service requests now display only vendor replies in the REQUEST / VENDOR column, using Summary Notes from the FlightBridge API.

• Vendor replies show vendor name, representative name and timestamp (MM/DD/YYYY HH:MM), and message text
• Organization-sent messages are not shown in the REQUEST / VENDOR column
• When multiple vendor replies exist, the most recent is displayed
• Applies to FlightBridge services except "Other" (Outside Bookings)

FlightBridge service

Expense Updates

Finance > Expense Reports > Create

Expense creation and reporting improvements for trip-based expenses.

• Personnel drop downs (Payable To, Paid With, Owner) now show email next to the name
• Crew on the selected flight leg appear at the top of personnel drop downs
• Trip search for expense reports: type 3 characters to search by trip number, date, or itinerary; all non-pending, non-locked trips are available (not limited to trips the user is crewed on)
• Payable To field now displays correctly when set to a user

Full name and email now in Expense create form

Other Updates

Additional enhancements and fixes across trips, notes, feasibility, and flight logs.

• Critical flag for terminated personnel: Feasibility & Tools shows a red critical warning when crew with a past termination date are assigned: "[Name] was terminated on [Date]".
• Inactive trip read-only: When a trip is set to Inactive, the Trip page and Flight Log page display in read-only mode; all fields are disabled until the trip is set back to Active.
• Note description format: Line breaks and formatting in trip notes are preserved when viewing the note summary from the overview page.
• Quote crew feasibility for IFR: Quote Feasibility & Tools Crew section now evaluates IFR limitations (Approach, Holding, Tracking) for directly-assigned crew and shows red critical or blue info flags.
• Error when cancelling or deleting logged flight legs: Users receive a red toast error ("Flight log must be removed") when attempting to set a logged leg to Cancelled, delete the leg, or set the trip to Inactive; the record remains unchanged until the flight log is removed.

Notes formatting update

Unable to cancel/delete trip with logged flight legs

Connect API Updates

Connect API related improvements:

• GET /v1/Quote response now includes tripNumber.
  
• POST Opportunity response now includes opportunityId (GUID) and opportunityNum (display number).
  
• GET /connect/v2/Aircraft and GET /connect/v2/Aircraft/{id} now include an accounts array (accountId, accountName).
  
• Trips can be linked to an Opportunity via opportunityId on POST/PUT /connect/v2/Trip; response includes opportunityId.
  

Fixes

• Daily Minimum fee no longer incorrectly applied when charging by Flight Time and arrival crosses to the next local day when FT requirements are met
• APIS departure airport now uses geographically appropriate airport when the departure airport lacks an IATA code, instead of matching an unrelated airport by identifier
• ForeFlight sync now succeeds when updating flight legs whose original scheduled departure time has passed but have been rescheduled to a future date
• Currency can now be set when creating or updating an Opportunity via the API
• eu-LISA submission validation no longer rejects valid submissions due to extra fields; when submission fails due to passenger/travel document data, the error identifies which passenger(s) are at fault