--- schema_version: "1" id: 35c5d21b9e103d09542269b8f8bedb896e0ddd3cd80b9a075ded3320415c6bc5 title: Message Screen Output Component collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_ref_elements_screencmp_message.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screencmp_message.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 0a6161d95d9f3c7b99efba31fb7179b5589cb67688733881f4b4fe332d6c5626 description: Show screen reader-compatible status messages with different message types that each have their own styling. The types include informational, success, warning, and critical. products: - Flow Builder - Salesforce Platform release: "264" --- # Message Screen Output Component Show screen reader-compatible status messages with different message types that each have their own styling. The types include informational, success, warning, and critical. ### Required Editions
View supported editions.
The Message component allows you to create accessible status messages that display to users when specific criteria are met. These messages are designed to be screen reader-friendly and follow Salesforce Lightning Design System standards. This is how an informational Message component looks at runtime. ![Message screen component at runtime](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/flow/message_screencmp_runtime.png) ![Example Use Cases](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_example.png) Example Use Cases - Display a critical error message when a user enters a duplicate social security number that already exists in the system. - Show a warning when data entry exceeds allowed thresholds or limits. - Present a success message when a form is completed correctly. - Provide informational messages to guide users through complex form requirements. ## Configure the Message Component
Attribute Description
API Name

The API name of the component.

An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can’t end with an underscore. It also can’t have two consecutive underscores.
Message Type

Select the visual style that determines the look and feel of the message. Available types include:

  • Informational
    Display helpful or descriptive text to users.
    Icon: Icon for information message
    Color: Gray
  • Success
    Notify users that something worked correctly.
    Icon: Icon for success message
    Color: Green
  • Warning
    Tell users they might want to reconsider their input.
    Icon: Icon for warning message
    Color: Orange
  • Critical
    Notify a user that there is a problem.
    Icon: Icon for critical message
    Color: Red
Message Content The text to display to the user. To reference a component's value from the same screen in the message, use a formula resource.
## Multiple Messages You can configure multiple messages with different criteria and message types for a screen. For example, add a success Message component, and set it to show when a user does something correctly. Then add a critical Message component that's set to show if they do something incorrectly. ## Set the Component Visibility Specify the logic that determines when the flow displays the component.
Option Description
When to Display Component

Configure when the component is displayed by using conditional logic.

You can set the components to:

Always
Always display the component.
When all conditions are met (AND)
Display the component when all of the conditions that you define are met. Define at least one condition.
When any condition is met (OR)
Display the component when at least one of the conditions that you define is met. Define at least one condition.
When custom conditional logic is met
Display the component when the condition logic that you define is met. Define at least one condition and specify condition logic.
## Specify the Behavior of Values on Revisited Screens Specify what this component does when a user enters a value, navigates to a previous screen, and then returns to the screen with this component.
Option Description
Use values from when the user last visited this screen The component retains the values that the user specified and doesn’t update the values to reflect changes made on previous screens.
Refresh inputs to incorporate changes elsewhere in the flow

The component updates the user-specified values to reflect changes made on previous screens.

If you pause and then resume the flow, the flow retains user-specified values only in Checkbox, Checkbox Group, Currency, Long Text Area, Multi-Select Picklist, Number, Password, Picklist, Radio Buttons, and Text components.
## Considerations - Only reactive formula operators are supported for conditions that evaluate components on the same screen. For supported operators, see [Reactive Screen Flow Formula Operators](https://help.salesforce.com/s/articleView?id=platform.flow_build_reactive_screen_flow_formula_operators.htm&release=264.0.0&type=5 "A subset of the formula operators supported in screen flows support reactivity."). - Messages are read by screen readers with appropriate ARIA alert roles for accessibility. - To show a message when the screen loads, use the Information type. Success, Warning, and Critical message types cause a screen reader error on screen load. Always set conditional visibility for Success, Warning, and Critical message types, otherwise they can cause issues with screen readers.