Configure - Restrict Editing of Past Crew Pairings

Historic Pairing Warning prevents users from creating or manipulating pairing data after a certain time period has passed with the goal of maintaining historical data.

Step-by-step guide


Security and System Configurations

Security Options:

  • Crew.Build
  • Crew.Follow
  • Crew.Plan
  • Crew.Roster
  • Crew.Monitor


User Preferences:

ElementValue

Application

All
Preference GroupConfig
PreferenceHistoric Pairing Override Hours
ValueInteger value, Default to 24
DescriptionRestrict users without the security option "Historic Pairing Override" from editing past crew pairings, duties and events for such event older than the hour amount specified


A. For users that do not have the security option enabled, and for any change to a pairing with last sign-off more than the number of hours from the present time, the following actions will be prevented in all the applications mentioned above:

Modification of pairings

    • Save button in the pairing details panel
    • Repair button in the pairing details panel

Deletion of pairings

    • X in the Actions column of the activity panel

When a user clicks any of the above-mentioned buttons, a message displays stating that the user does not have the correct security permissions to edit pairings in the past. When the user acknowledges the message, the change will NOT be committed to the database.

B. For users with the correct security access to modify duties, and where the duty is outside the time frame, click on the above-mentioned buttons and an override window will display asking the user to supply a reason for the change. 

Crew Editing Restrictions

A. For users that do not have the security option enabled, and for any change to a crew member's duty allocation which last sign-off is more than the number of hours from the present time, the following actions will be prevented in all the applications mentioned:

Allocation of pairings

    • Via drag and drop from the pairing activity panel
    • Via drag and drop from another crewmember

De-allocation of pairings and courses

    • Via right-click and choosing the Deallocate option
    • Via drag and drop to another crewmember

When a user performs any of the above-mentioned actions to a crew member in the past, a message will display stating that the user does not have the correct security permissions to edit a crew member's past duties. All changes will be ignored and no data will be committed to the database.

The following Gantt right-click options is disabled:

  • Allocate Sick Leave
  • Edit roles
  • Mark as Pre-Planned
  • Mark Request
  • Mark as Support (For a course)

B. For users with the correct security access to modify duties, and where the duty is outside the time frame, when doing the above-mentioned actions, the user will be presented with an override option, asking the user to supply a reason for the change.

Historic Pairing Warning

When a user with the appropriate access modifies a pairing, the Historic Pairing Warning window displays. 

This new window consists of the following elements:

ElementValue

Reason text box

A mandatory field intended for override justification.
OKCommits the update and keeps the reason against the pairing.
CancelCancels the update, thus not committing the scheduled time change.