You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On creation or edit of a departure-type flow measure (MDI, ADI, Rate per Hour), user is issued a warning and asked confirm before being able to submit if the ADEP is anything other than a custom value with 4 non-wildcard characters. i.e. can submit without confirming for "EGLL", but multiple values, airfield groups, or use of any wildcard triggers the warning.
Suggested example warning text:
WARNING
You have submitted a departure flow restriction applying to multiple airports. This is usually incorrect as it requires the flow measure to be coordinated across multiple airports. If you have arranged/agreed this with a flow manager to coordinate on the network, you may proceed.
The more likely situation is that you are trying to apply the departure flow restriction separately to multiple airports. For this you must issue separate flow measures
Return and Edit
Ignore warning, issue flow measure
The 'return and edit' option should be first and ideally more prominent.
The text was updated successfully, but these errors were encountered:
Part of ADEP logic plan.
On creation or edit of a departure-type flow measure (MDI, ADI, Rate per Hour), user is issued a warning and asked confirm before being able to submit if the ADEP is anything other than a custom value with 4 non-wildcard characters. i.e. can submit without confirming for "EGLL", but multiple values, airfield groups, or use of any wildcard triggers the warning.
Suggested example warning text:
The 'return and edit' option should be first and ideally more prominent.
The text was updated successfully, but these errors were encountered: