The following areas of the Avianis Web Application have been updated:

This update includes the first aspects of operational control that need to be in place for the MVP. This feature refers to Certificates so users in the same accounts, but on different certificates, can’t create or edit data that does not correlate to their assigned certificate. This will only apply when the Certificate Segmentation module has been enabled. Below are a few examples of when multiple certificates have been applied to an Avianis account and where the Certificates designated on the Personnel profile and/or the Aircraft profile allow or do not allow certain actions to be performed by the user.

If the logged-in user does not have a Certificate assigned to their profile and they are attempting to do any of the below they will receive an error message stating: "Error: You do not have the certificate designation to make this change"

The same error message will also display for any user attempting to make the above actions if the logged-in user has a different certificate assigned to their profile than the personnel they are attempting to create an event for, duty entries for, or crew onto trips where the assigned tail number(s) have a different certificate.

Related Articles:

Certificate Segmentation

In order to see these updates, the Atlas Reservations module must be enabled and can only be viewed within the Schedule Board. Within the Schedule Board, two new fields have been added to the Filters > Templates > Flight Legs. They are Reservations Continuation and Reservation Tech Stop

Note: If the Atlas Reservation value is NO then the flight card displays nothing.

A new filter has been added to the Schedule Board > Filters > Templates called "Show Flights on Multiple Days". This new setting is only available on the Schedule Board when the user has Show Event Length By Fixed selected. After selecting Fixed from the templates a new field will be displayed called "Show Flights on Multiple Days".

When set to Yes, multiple flight cards for the same flight leg display on the Schedule Board when the flight leg crosses over to the next day, and the bottom-left and/or right corner is flagged with a triangle to indicate the continuation. This is the default setting

When set to No, only one flight card is shown on the Schedule Board on the day it departs. The triangle still displays in the bottom left and/or right corner to indicate a continuation into the next day even though the flight card does not duplicate when the flight leg crosses over to that next day.

Note: This does NOT affect events or any other schedule object other than flight. All other schedule objects would repeat on all days they occur.

When adding a new trip on the Schedule Board and the user clicks "Save and Close" the new trip is included in the view but the page will not need to undergo a full reload.

Additionally, if the user updates the time of a flight by clicking and dragging the edge of the object and the user proceeds to approve/save the change the page no longer needs to perform a full reload.

New values are present that can be included in the Fleet templates from within the Schedule Board Settings. The new fields that can be selected will appear in the drop-down in alphabetical order.

Additionally, the Fleet Name within the Fleet resources has been updated to display in bolded text and is now hyperlinked. When clicked the user is directed to the associated Fleet Profile page in a new window.

Related Articles:

Schedule Board: Filters

Schedule Board: Settings

Schedule Board: Personalizing Event Display Settings (User)

This update includes three new endpoints within the Connect v2 API for the user to be able to get, create and update Job Cards. For the API call to be successful the user must include all required fields. The Job Card's ID (GUID) is required to pass in, if applicable, and must match a Job Card in the organization.

GET Job Card Details - GET/connect/v2/JobCard/{id}

The only parameter passed in is the ID (GUID) of a Job Card, and when the call is made it returns the following information:

CREATE new Job Cards - POST/connect/v2/JobCard

The data the user is able to pass into this endpoint is as follows (the items marked with an asterisk are required):

Note: When the Job card is created, the Aircraft out of Service form defaults to automatically check the Take Aircraft Out of Service checkbox, and the return to service option defaults to Manual.

UPDATE Job Cards - PUT/connect/v2/JobCard/{id}

The data the user is able to pass into this endpoint is as follows (the items marked with an asterisk are required):

When preforming all the above calls and the Actual Return to Service Date/Time is passed in, then the Job Card gets updated to Completed: YES and the Completed Date is updated to the Actual Return to Service Date/Time value. Should a call be made without an Actual Return to Service Date present, then the Job Card is updated to Completed: No and the Completed Date is cleared out. An activity feed record is captured in the job card with all of the information that was passed into the API.

Updates have been made to the Connect API for Atlas ‘continuation’ and ‘tech stop’ information to display in the Atlas data table. When there is a Continuation or a Tech Stop for a flight in Atlas, then a new column is displayed in the FlightLegDemandRequest table of Continuation and Tech Stop. If the PriorFlightLegID (GUID) for a flight is also set in Atlas, then the table will also include PriorFlightLegID (Int).