Compare Web and Mobile App Alert Behavior

Alerts appear on the home page of the Life Sciences Commercial app or a specific record page, depending on configuration.

• Notifications: Alerts tab on the Notifications List Lightning component
• Recommendations: Recommendations tab on the Notifications List Lightning component
• Guided Actions: Alerts tab on the Notifications List Lightning component
• Announcement: Announcements Lightning component on the home page

Alerts appear in multiple contexts, including the home page, global notifications experience, record pages, and tabs.

Users open alerts from the bell icon in the app header. The message pane organizes notifications into the Alerts, Recommendations, and Guided Actions tabs.

• Notifications: Alerts tab
• Recommendations: Recommendations tab
• Guided Actions: Guided Action tab
• Announcement: Announcements Lightning component on the home page

The total number of alerts shown in the Alerts and Recommendations tabs depends on the number of records configured in the Notifications List Lightning component.

When the display limit is reached, older alerts are automatically removed as new alerts arrive, even if they haven’t expired.

• View alerts
• Mark alerts as read

  These actions are available by default and require no additional configuration.

• View alerts grouped by type in the message pane
• Complete tasks or actions directly from alerts
• Navigate to internal records, external websites, or external apps
• Dismiss or resolve alerts and if needed, provide a reason

  Users can mark a message as Dismissed or Resolved if you configure these actions in the Additional Message field of the alert record. Users can select a reason when dismissing the alert, either optionally or as a required step. Once the alert is dismissed or resolved, it’s removed from the list and the alert status is updated through the App Alert User Response record.

Use the Type and Valid Until Date fields to define the alert's visibility window.

Notifications, Recommendations, Guided Actions, and Announcements: Visible from their effective date until a user marks them as read or until they reach their Valid Until Date. If the Valid Until Date isn't set, the alert remains visible indefinitely.

Use the Type and Valid Until Date fields to define the alert's visibility window.

• Notifications and Recommendations: Visible for a maximum of 7 days from the effective date. If you set the Valid Until Date within this window, the alert is visible only until that date. If set beyond 7 days, the standard 7-day limit still applies. Additionally, users can manually dismiss alerts earlier if the Dismiss action is enabled.
• Guided Actions and Announcements: Visible longer than the 7-day period, with visibility determined by the Effective Date and Valid Until Date. If the Valid Until Date isn't set, the alert remains visible until the user manually dismisses the alert.

Use these fields to configure the alert content.

• App Alert: Message and Subject fields.
• Record Alert: Description and Subject fields.

Use these fields to configure the alert content.

• App Alert: Message, Subject, and Additional Message fields.
• Record Alert: Description, Subject, and Additional Message fields.

Not supported.

Alerts don't include buttons or direct links to records or external systems because the Additional Message JSON field isn’t supported.

Fully supported through the Additional Message field.

The Additional Message field supports a JSON structure for defining deep links, external URLs, action buttons, and tags. For more information, see Additional Message for App Alerts on Mobile.