Display error messages with different severity levels in a Visualforce page

-

To display error messages with different severity levels in a Visualforce page using ApexPages.addMessage, you can follow the same approach as before but with different severity levels. Here's how you can add messages with different severity levels and display them in a Visualforce page:











Add Messages with Different Severities in Apex Controller:

In your Apex controller, add error messages with different severity levels using ApexPages.addMessage.

public class MyController {

    public void someAction() {
        try {
            // Perform some action
            if (someCondition) {
                // Add error message with severity
                ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.ERROR, 'An error occurred: Some error message'));
            } else if (anotherCondition) {
                // Add warning message with severity
                ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.WARNING, 'Warning: Some warning message'));
            } else {
                // Add info message with severity
                ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.INFO, 'Information: Some information message'));
            }
        } catch (Exception e) {
            // Add error message with severity
            ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.ERROR, 'An error occurred: ' + e.getMessage()));
        }
    }

}

In this example, we're adding messages with different severity levels (ERROR, WARNING, INFO) based on certain conditions.

Display Messages in Visualforce Page:

In your Visualforce page, use <apex:pageMessages> to display the error messages with different severity levels.

<!-- MyPage.page -->
<apex:page controller="MyController">
    <apex:form>
        <apex:pageMessages />
        <!-- Other page content -->
    </apex:form>
</apex:page>

The <apex:pageMessages> component automatically displays messages added using ApexPages.addMessage with the specified severity levels.

With this setup, error messages with different severity levels (ERROR, WARNING, INFO, CONFIRM, FATAL) added in the Apex controller will be displayed in the Visualforce page accordingly. You can customize the message content, severity levels, and placement on the page as needed.

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more