Element Presets
Element Presets
Create reusable affected-element filter profiles and use them in dashboards and alerts.
Element presets are saved affected-element filter profiles. They let you define operational relevance once, then reuse the same rule logic in Notamify workflows.
Use them when the same filter shape appears in more than one place: runway closures, fuel service outages, navaid unserviceability, restricted aerodromes, alternate monitoring, or operation-specific review.
What a preset contains
An Element preset is made from one or more affected-element rules. A rule can include:
- Element type, such as aerodrome, runway, taxiway, approach, navaid, airspace, route, apron, lighting, service, procedure, or other.
- Effect, such as closed, restricted, hazard, unserviceable, work in progress, or caution.
- Published assertion, such as activated, deactivated, available or unavailable. Assertions are independent of effects; an availability statement can have no effect.
- Subtype, when the selected element type has a subtype list.
- Identifier, for cases where the operational name matters.
- Applies to scope, such as aircraft type, traffic type, operational use, or operation phase.
- Change subjects, such as declared distances, operating hours, frequency, minima or firefighting category.
Keep each preset tied to one operational question. If a preset is hard to explain in one sentence, split it into smaller presets.
Creating presets
Open Element presets from the dashboard sidebar.
You can start from:
- Blank preset when you know exactly which affected elements to match.
- Template when an existing operational profile is close to the workflow you need.
Name the preset after the job it performs, not after the UI settings inside it. Good names include Core runway closures, Fuel service watch, or IFR alternate relevance.
Presets can be private or team-shared. Team presets are visible to team members. If you edit a preset that is already used elsewhere, the updated rules apply anywhere that preset is selected.
Element presets are currently marked Preview in the UI while the affected-element model continues to evolve.
Using presets in dashboards
Open a dashboard and use the affected-element filter in the dashboard header. The saved-presets button lets you choose an Element preset for that dashboard.
Selecting a preset replaces the manual affected-element filter for the dashboard baseline. The dashboard then applies the preset across its monitored locations, alongside the dashboard's time mode and any other active global settings.
Use a preset when several dashboards should answer the same question consistently. Use a manual affected-element filter when the dashboard is temporary or the filter is only useful once.
Some NOTAMs may remain visible even when a preset is active because they do not include enough structured affected-element metadata to evaluate the rule safely.
Common conditions all apply. Alternative branches are joined by OR, with all conditions within a branch required. A compound exemption applies only when every prerequisite is established. Missing permission qualifications, timing, object identity or spatial membership remain unknown, so the NOTAM stays visible. Reported activity describes the announced context rather than selecting which aircraft are affected.
Multiple values selected within a profile field are alternatives. For example, selecting both takeoff and landing keeps a restriction visible when only landing is exempt. A NOTAM is hidden only when none of the selected alternatives remains relevant or uncertain.
The Hide confirmed mismatches flight-profile mode retains unknown cases. Published requirements, observations and surface reports remain attached to their source statement; a failed obligation does not make a restriction disappear. Multiple statements about one object can have different qualifiers.
Using presets in alerts
Element presets are also available while configuring affected-element alert rules.
In an alert, choose Affected element(s) as the additional filter. Add or edit an affected-element rule, select exactly one element type, then use Scope preset to choose a saved Element preset and apply it.
Notamify copies compatible Applies to scope and Change subjects from the preset into the alert rule. You can review and edit those copied fields before saving the alert.
The alert does not automatically inherit every preset setting, and the preset does not choose recipients, lifecycle notifications, time windows, or delivery settings. Treat the preset as a rule-building shortcut, then verify the final alert configuration before saving.
Alert delivery currently supports flat conditions and exceptions. It does not yet evaluate compound branches, spatial scopes, dependencies or qualified permission prerequisites. Published-assertion filters and other unsupported preset criteria cannot be imported. The editor explains the incompatibility instead of simplifying the preset. Dashboard/profile results and delivered alerts can therefore differ.
