Salesforce feature release lifecycle

-

Salesforce application features go through multiple states in their life-cycle. It's crucial to understand terms related to feature research and activation, as they determine a feature's release status.

Salesforce feature release lifecycle

Pilot - Usually the first phase of public testing, Pilots normally include a small subset of participant Organizations. These Organization’s must request to opt in to a Pilot and then be nominated for participation. Oftentimes, Pilot nomination requests will require additional information be provided to ensure proper eligibility for the Pilot feature in question. 


BETA - Features with successful Pilots will often transition to the BETA phase. This involves rolling the feature out publicly for testing. BETA features might require additional enabling by a System Admin and are accompanied by verbiage that clarifies the feature is in BETA status. BETA features are normally unsupported or given very limited Support as they are not yet fully functional or finished features. 


Generally Available (GA) - Once a feature has passed the Pilot and BETA testing phases it will be formally included in a Salesforce release. This is considered Generally Available (GA). GA features are considered fully functional and, in most cases, fully supported. They will not be accompanied by Pilot or BETA labels or warnings and are treated as officially released Salesforce functionality. 


Developer Preview - Developer Preview or Sandbox Preview is available ahead of a major Salesforce release when all preview sandboxes are upgraded to the next major Salesforce release so that the new features can be tested thoroughly in a Sandbox org.


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