5.6 Alerts & Messaging
USAF Application Styles
Alerts & messaging are specific to applications, though their triggers, appearance, and behaviors should follow
best practices.
Machine Learning
![5.6 Machine Learning](../../_assets/5.6_ml_notification_status_red.png)
Engines Health Management
![5.6 Engines](../../_assets/5.6_engine_health_management_error.png)
Log Common Operating Picture
![5.6 LCOP](../../_assets/5.6_log_error_notification.png)
Positive Inventory Control
![5.6 PIC](../../_assets/5.6_pic_install_step_error_02.png)
![5.6 PIC](../../_assets/5.6_pic_modal_loading.png)
![5.6 PIC](../../_assets/5.6_pic_results_alert.png)
![5.6 PIC](../../_assets/5.6_pic_error_link_database_down.png)
![5.6 PIC](../../_assets/5.6_pic_assetslocation_tool_tip.png)
Alpha Standard
The following example component illustrates the best practices outlined previously, with the practical choices that make it so.
- Clear. Alerts state in clear language, and with obvious color cues that they are positive / negative / neutral, the reason for the alert, and the action required of the user in order to resolve it.
- Consistent. Alerts follow web or application-standard patterns that are repeating and predictable. If a user were to perform the same triggering action twice, they would receive the same alert twice.
- Actionable. Alerts & messages offer clear next steps to resolve or address them. When appropriate to the context, alter text offers inline links, or anchor links to the offending component.
Disclaimer: Please default to your application’s and USAF styles; the following component standards are to be used only if those assets are not applicable or not available
![5.6 alpha](../../_assets/5.6_as_form_field_symbol_and_color_01.png)
![5.6 alpha](../../_assets/5.6_as_form_field_error.png)
![5.6 alpha](../../_assets/5.6_example_information.png)
![5.6 alpha](../../_assets/5.6_as_banner_information.png)
Reference