Action Layout Editor: Just as object record pages have page layouts that can be customized, actions have action layouts that can be customized. When you create an action, Salesforce populates its layout with a default set of fields. You can add, remove, or reorder fields on the action layout to present only the essential items your users need when they use the action.
Action Layout Editor Considerations: When you create an action, Salesforce populates its layout with a default set of fields. You can add, remove, or reorder fields on the action layout to present only the essential items your users need when they use the action.
Action Link Templates: Create action link templates in Setup so that you can instantiate action link groups with common properties from Connect REST API or Apex. You can package templates and distribute them to other Salesforce orgs.
Create Action Link Templates: Create action link templates in Setup so that you can instantiate action link groups with common properties from Connect REST API or Apex. You can package templates and distribute them to other Salesforce orgs.
Delete Action Link Group Templates: When you delete an action link group template, you delete its associated action link templates and all action link groups that have been instantiated from the templates. Deleted action link groups disappear from any feed elements they've been associated with.
Design Action Link Templates: Before you create a template, consider which values you want to set in the template and which values you want to set with binding variables when you instantiate action link groups from the template.
Edit Action Link Templates: You can edit all fields on an unpublished action link group template and on its associated action link templates.
Action Overrides in Aura Experience Builder Sites: Personalize your site users’ experience in Aura Experience Builder sites by adding a custom Lightning component to replace standard forms when users click the New or Edit button. Use action overrides when your site and portal users require a more customized user experience than the Salesforce standard page provides.
Action Overrides in Managed Packages: In a managed package, overrides specified by the package developer are included as default overrides. The package subscriber can specify local overrides for each user experience to use instead of the package default overrides. Package default overrides impact the options and behaviors of local overrides.
How Predefined Actions Are Ordered in the Salesforce Mobile App Action Bar and List Item Actions: Your org’s page layouts and publisher layouts control the order in which actions appear in the Salesforce mobile app action bar and list item actions. If you don’t customize the actions in the action bar on a page layout or global publisher layout, Salesforce predefines the location of key actions.
How Actions Are Ordered in the Salesforce Mobile App Action Bar: The Salesforce Mobile and Lightning Experience Actions section of a page layout and global publisher layout drives which actions appear in the Salesforce mobile app action bar. You can also customize the order of quick actions, productivity actions, and standard and custom buttons that are available as actions.
List Item Actions in the Salesforce Mobile App: List item actions give you access to your actions in list views, task lists, and related record lists. You can use list item actions to update records directly from lists.
Salesforce Mobile App Action Bar: The productivity actions, standard and custom record buttons, and quick actions appear in the action bar and the action menu.
Quick Actions and Record Types: Using record types in your organization can affect the availability of quick actions for your users.
Standard Chatter Actions: Standard Chatter actions are available only when Chatter is enabled. The standard Chatter actions are Post, Poll, Question, and Announcements (groups only). Salesforce Classic standard actions also include File, Link, and Thanks (WDC). Standard actions are supported in both the full Salesforce site and in the Salesforce mobile app.
Custom Success Messages for Quick Actions: For Create a Record, Update a Record, and Log a Call action types, you can create a custom message that displays when the action executes successfully.
Actions in Lightning Experience: In Lightning Experience, actions appear in the Global Actions menu in the header, on related lists, and on list view items. Actions also appear on a record page, in one of several places depending on the action’s type.
How Actions Are Ordered in Lightning Experience: In Lightning Experience, the actions on record pages are derived from the list of actions in the Salesforce Mobile and Lightning Experience Actions section of the page layout for that object. The same section on global publisher layouts determines the global actions that appear in the Global Actions menu.
Action Limits and Limitations: Actions can work differently than you expect in certain situations and for different objects. Keep these limits and limitations in mind when working with actions.
Quick Actions: Quick actions enable users to do more in Salesforce and in the Salesforce mobile app. With custom quick actions, you can make your users’ navigation and workflow as smooth as possible by giving them convenient access to information that’s most important. For example, you can let users create or update records and log calls directly in their Chatter feed or from their mobile device.
Global Quick Actions: You can add global quick actions to almost any page that supports actions. Use global actions to let users log call details, create or update records, or send email, all without leaving the page they’re on. Global create actions enable users to create object records, but the new record has no direct relationship with other records.
Object-Specific Actions: Object-specific actions let users quickly create or update records, log calls, send emails, and more, in the context of a particular object.
Productivity Actions: Productivity actions are predefined and attached to a limited set of objects. Productivity actions include Send Email, Call, Map, View Website, and Read News. Except for the Call action, you can’t edit productivity actions.
Action Types: There are several categories of actions, such as standard Chatter actions, default actions, mobile smart actions, custom actions, and productivity actions. The types of actions that you see depend on the age and configuration of your org.
Add Metadata Manually: The Change Management tab uses source tracking to automatically track metadata files in your org. However, when you require the flexibility to include additional metadata files that source tracking hasn’t pulled automatically, you can add metadata manually.
Add Translated Languages and Translators: Add languages for translation, assign translators for each language, and activate or deactivate a language’s translations.
Add Default Custom Links: Update predefined custom links for account, contact, lead, campaign, and solution detail pages.
Create a Custom Field: Capture your unique business data by storing it in custom fields. When you create a custom field, you configure where you want it to appear and optionally control security at the field level.
Add a Single User: Depending on the size of your organization or your new hire onboarding process, you may choose to add users one at a time. The maximum number of users you can add is determined by your Salesforce edition.
Remove a Picklist Value: Remove or replace custom picklist values to update the records that have the picklist field.
Delegate Administrative Duties: Use delegated administration to assign limited admin privileges to users in your org who aren’t administrators. For example, let’s say you want the Customer Support team manager to manage users in the Support Manager role and all subordinate roles. Create a delegated admin for this purpose so that you can focus on other administration tasks.
Explore Guidance Sets: Salesforce admins, Enablement admins, and all Starter Edition users have access to guidance sets in the Guidance Center. Guidance sets offer personalized setup and learning resources that align with your experience level and the products you’re using. Each guidance set includes suggested resources to help you successfully complete your job.
Guidance Center: The Guidance Center panel in Lightning Experience provides a convenient location for showing content that's assigned to or recommended for the current user. The Guidance Center includes not only suggested content that's authored by Salesforce but also custom content that you manage. With Learning Paths, you can manage the learning items—custom links, videos, and Trailhead modules—that are available in the Guidance Center and assign those items to specific users with optional due dates.
Customize Content in the Guidance Center: To add your own learning items in the Guidance Center, assign content with Learning Paths. Or, optionally hide Learning Home or Salesforce suggestions.
Troubleshoot Field Access Issues: Your users can experience access issues or insufficient privileges errors if field permissions or other features that control fields aren’t configured correctly.
Troubleshoot Object and Record Access Issues: Your users can experience access issues or insufficient privileges errors if object permissions or record-access features aren’t configured correctly.
Troubleshoot Feature Access Issues: If your users have issues completing a task or accessing a feature, review their assigned permissions.
Create a User Role: In the role hierarchy, users have access to records owned by or shared with users in roles below them. Roles within the hierarchy affect access on components such as records and reports.
Set Your Internal Organization-Wide Sharing Defaults: Internal organization-wide sharing defaults set the baseline access for your internal users for your records. You can set the defaults separately for different objects.
Mass Transfer Records: Use the Mass Transfer tool to transfer multiple accounts, leads, service contracts, and custom objects from one user to another.
Troubleshoot Access Issues for Guest Users: If unauthenticated guest users don’t see the correct data in your Experience Cloud sites, work through these steps to identify and fix the problem.
Troubleshoot Access Issues for High-Volume Users: If your high-volume community or site users don’t have the expected access to data, work through these steps to identify and fix the problem. High-volume users don’t have roles and are limited in what features can be used to grant them access.
Troubleshoot Access Issues for External Users: Review this guidance if your external Experience Cloud site users are experiencing insufficient or unexpected access. The data access management features available depend on the type of external user.
User Permissions: User permissions specify what tasks users can perform and what features users can access. For example, users with the View Setup and Configuration user permission can view Setup pages, and users with the API Enabled user permission can access any Salesforce API.
Profiles: Profiles define default settings for users. When you create users, you assign a profile to each one.
View and Manage Users: In the user list, you can view and manage all users in your Salesforce org and Experience Cloud sites and portals.
Own from Salesforce Administration: Own from Salesforce provides identity and access management, security, and other settings for Anonymize, Archive, Backup and Recover, Discover, and Seed. Manage global settings such as single sign on (SSO), multi-factor authentication (MFA), and role based access controls (RBAC). You can also access settings that help you respond to data privacy requests, manage your users, and more.
Export a Backup to an Amazon S3 Bucket: You can export backup data to an external Amazon S3 bucket. You can export a full backup or a backup of selected objects.
Create and Manage Endpoints for Backup Export: In the Endpoints tab of the Account Settings page, you can view existing endpoints, as well as create a new endpoint to export your backup.
Manage Scheduled Exports for a Data Backup: Schedule an export of your backup data to your existing endpoints in the Schedule Exports menu. When the Scheduled Export runs, it will export your last successful backup (either full or for specific objects).
Export a Backup to an SQL Database: You can export manually backup data to an SQL database using a generated SQL script which inserts all data and relationships into the database. You can export a full backup or a backup of selected objects.
Bring Your Own Key (BYOK) for Recover: Bring Your Own Key (BYOK) gives you more control over your encryption keys. You can create your own encryption keys to encrypt your cloud data. Your data will be encrypted using these keys, not derivative or composite keys. Encrypted, dedicated data tenancy helps you meet advanced security requirements. Schedule key rotation, or rotate keys on demand. If needed, you can also immediately revoke keys.
Bring Your Own Key Management Service for Recover: Encrypting the S3 bucket used to store your data using your AWS Key Management Service (KMS) gives you sole access and management capabilities of the key used to encrypt the bucket. BYOKMS enhances Bring Your Own Key (BYOK) activities. Backups are stored in AWS Simple Storage Service (S3) with a separate S3 bucket for each customer.
Bring Your Own Key Vault for Backup & Recover: Install the enterprise application to store your data using your Azure Key Vault. This gives you sole access and management capabilities of the key used to encrypt the storage account where your data is stored. Bring Your Own Key Vault (BYOKV) is an enhancement to Bring Your Own Key (BYOK).
Build a Content Approval Workflow in Agentforce Operations: Build a content approval blueprint in Agentforce Operations to automate your team's review and sign-off process. This example walks you through creating fields, configuring stages and tasks, testing the workflow end to end, and publishing the blueprint.
Agent Quick Actions: Agent quick actions are AI-powered, and allow your users to take advantage of Agentforce directly from record pages. Clicking an agent quick action opens the Agentforce panel and directs Agentforce to use the subagent underlying the utterance in the agent panel.
Create an Agent Quick Action: Create agent quick actions to give your users the ability to streamline their work by using AI-powered actions.
Legal and Ethical Considerations with Headless Functionality: Working with Salesforce beyond the browser expands what agents and third-party tools can do—so it also expands your responsibility. Review these legal and ethical considerations before you build and deploy headless experiences.
Security and Governance in Headless Experiences: Headless capabilities enable users, apps, and AI agents to reach Salesforce data and processes outside the traditional Salesforce interface. That flexibility opens more places where access gets requested, but it doesn't change how you govern that access. Learn how identity, permissions, and monitoring work together to keep headless access to your org secure.
Get Connected to AIforce: Connect an AI tool such as Claude to Salesforce, or use the AI features built into Salesforce. Both inherit the same Salesforce security, permissions, and data governance.
Welcome to AIforce: AIforce isn’t a single product or tool. AIforce brings all of your Salesforce context to the interface where you want to work. It provides the flexibility to meet you where you do business: in Slack, your Salesforce org, or your favorite agentic tool.
Anonymize: Safeguard sensitive information by creating custom templates that mask sensitive data fields, such as phone numbers and addresses. With Anonymize, you can mask data when sharing sandbox data with other product teams for development, testing, or training. You can also populate empty fields with unique synthetic data. Anonymizing data reduces risk and helps your organization adhere to compliance and privacy regulations.
Salesforce Authenticated User Permission Requirements for Anonymize: In a Salesforce data environment, the Anonymize application uses an authenticated user to access a particular sandbox and execute its various processing tasks. In order for an authenticated user to successfully execute these tasks, assign the required Salesforce processing permissions to the authenticated user used by the Anonymize application.
Handle Compliance Categorization and Data Sensitivity Level of Salesforce Fields: For Salesforce fields assigned a Data Sensitivity Level or a Compliance Categorization, the Anonymize application sets a data sensitivity level for the field and identifies if the field needs to be anonymized. The status of the field is shown in the anonymize template.
Custom Field Replacement Values in Anonymize Templates: Custom value generation gives you more control to create unique values that comply with regulations or testing prerequisites. Using custom values helps prevent errors when the automatically generated values don't comply with your business logic.
Define and Execute Anonymize Jobs: After your anonymize templates are created and configured with the objects and fields, you can proceed to execute anonymize jobs. The Anonymize application enables you to select the service data to be anonymized. The service data to be anonymized can be retrieved either from the live service or from service backups.
Anonymize FAQs: If you encounter issues related to Anonymize for Salesforce, the answers to frequently-asked questions can sometimes help you.
Anonymize Feature Highlights: The Anonymize application provides its users with the ability to mask sandbox data. Masking data using Anonymize is accomplished by first creating and then configuring an anonymization template. There are several key Anonymize features that can help you configure the template.
Get Started with Anonymize for Salesforce: The Anonymize application enables you to create anonymization templates for sandboxes. These templates disguise sensitive information by allowing you to select objects and fields for anonymization. A range of replacement options are available, tailored to the field type, for anonymizing the field data.
Anonymize Job Reporting: Anonymize application processing generates reports about each executed, anonymize job. The Anonymization Report provides an overall summary about anonymization job processing and a breakdown of any specific warnings and errors that occurred. The Salesforce Automations Report reports about the Salesforce automations that were selected to be temporarily disabled for execution of the anonymize job, as well as automations that were not selected. Warnings and errors that occurred are also reported.
Anonymize Limitations: Review the limitations that affect the Salesforce data environment before you start working with Anonymize.
Protect the Privacy of Sandbox Data with Anonymize: Maintain data privacy and regulatory compliance when sharing sandbox data with other product teams for development, testing, or training. Gain stakeholder trust by protecting sensitive, classified, and personal identifier information with Anonymize.
Configure an Anonymization Template for Salesforce: After you create an anonymization template for Salesforce, then the new template is empty of objects to anonymize, and is in Edit mode. Configure the new template with the necessary objects and configure the fields to anonymize, with a replacement value.
Create an Anonymization Template for Salesforce: When you create an anonymization template for Salesforce, then the new template automatically displays in the My Templates page, is empty of objects to anonymize, and is in Edit mode, meaning that its content can be modified.
Dependent Picklists: When a field of type picklist (level 1) has one or more dependent child fields of type picklist (level 2 - level <n>), the UI updates the child fields' Replace with field option.
Object Record Filters in Anonymization Templates: For each object listed in the Anonymized objects panel of an anonymize template, you can define filters that are applied to the object's fields during an anonymize job to filter the object’s records. Filtering object records enables you to refine the anonymization to be more precise by instructing anonymize processing to select for anonymization only the most relevant or essential records of a given object. Object record filters are only applied during standalone anonymize jobs.
Manage Anonymization Templates: From the Anonymize Templates tab, perform administrative actions on anonymization templates: Clone and Delete.
Anonymize As Part of a Seeding Job in Salesforce: The Anonymize app can be used as part of a seeding job which enables you to anonymize the seeding source's data - personally identifiable information (PII), sensitive information, classified information - before that data is copied to (seeded in) the destination.
Use Custom Values in Anonymization Templates: Define custom anonymization patterns when masking data to replace sensitive information with realistic, yet fictitious, data. Create custom patterns across multiple fields for data such as email addresses, phone numbers, or social insurance numbers.
Work with Anonymization Templates for Salesforce: Anonymization templates in Own’s Anonymize application for Salesforce can be managed through various actions such as creating, configuring, cloning, deleting, and exporting. Objects that are included in both the seeding and anonymization templates can be anonymized as part of the seeding process..
Custom Adapter for Salesforce Connect: Connect to any data anywhere for a complete view of your business. Use the Apex Connector Framework to develop a custom adapter for Salesforce Connect.
High Data Volume Considerations for Salesforce Connect—Custom Adapters: If your org hits rate limits when accessing external objects, consider selecting the High Data Volume option on the associated external data sources. Doing so bypasses most rate limits, but some special behaviors and limitations apply.
Apex Hammer Test Results: With the Hammer process, Salesforce runs your org’s Apex tests in both the current and new release, and compares the results to identify issues for you.
API Catalog for Salesforce: Bring your APIs and Model Context Protocol (MCP) servers into API Catalog for Salesforce. Your catalog is a single place to view your APIs and MCP servers from different sources and make them available to use in Salesforce.
Activate Agent Actions: In API Catalog, you can activate agent actions for APIs. If you activate invocable actions for an API that has annotations for agent actions, the associated agent actions also activate.
Activate Invocable Actions for APIs: Activate invocable actions for APIs. You can then use activated actions in your automations, such as those in flows, agents, and Apex code. You can activate actions by using API Catalog for MuleSoft, Heroku, and Apex REST APIs.
Bring Apex APIs into API Catalog: Bring Apex REST and AuraEnabled APIs into API Catalog to take advantage of the automatic agent action activation and make your APIs more discoverable.
Bring Heroku APIs into API Catalog: Publishing your Heroku APIs into Salesforce automatically adds them to your org’s API catalog. Heroku APIs shown in your catalog are available as a Heroku action type that you can use to create a custom agent action.
Bring MuleSoft APIs into API Catalog: Connect your Anypoint Platform and Salesforce orgs, and enable the API Catalog capability. You can then sync MuleSoft APIs into your API catalog. API Catalog makes it easy to create secure connections for your MuleSoft APIs. You can stay up to date on new API versions as they sync into the catalog, and request API access when you need it.
Bring Named Query APIs into API Catalog: Named Query APIs are automatically shown in API Catalog when you create them in Salesforce. This makes them more discoverable by others and makes it easy for admins to activate agent actions for these APIs.
Create and Manage Connections for Your APIs: Create connections to authorize the use of actions you activate for MuleSoft APIs and HTTP callouts in Salesforce. You create connections for other external API sources from outside of API Catalog, and then you can view the connections from the catalog.
Create Custom Salesforce MCP Servers in API Catalog: If you have the Salesforce Hosted MCP servers feature enabled, you can create custom Salesforce MCP servers. Use API Catalog to create the server, add assets to it, and then activate it to use with Agentforce and other supported MCP clients.
Deactivate Actions: Deactivate actions for APIs if you no longer need the actions.
Manage APIs in API Catalog: API Catalog gives you a central place to view and manage your APIs and make them available to use in Salesforce automations. With just a few clicks, activate actions based on API operations to use in your Salesforce automations, such as agents, flows, and Apex code.
Manage External MCP Servers in API Catalog: Manage MuleSoft and other external MCP servers in API Catalog. Sync MuleSoft MCP servers from Anypoint Platform to make them discoverable in Salesforce. Register other external MCP servers in API Catalog or Agentforce Registry by creating connections to authorize them. Then, add the tools you allow. You can also view MCP servers installed from AgentExchange.
Register External MCP Servers in API Catalog: Register external MCP servers manually in API Catalog to make their tools available for use in Agentforce agents. Create connections to authorize the servers in Salesforce and specify the tools they can access. You can also view MCP servers installed from AgentExchange. Then, add tools the servers can use.
Manage MCP Servers in API Catalog: View and centrally manage MCP servers in API Catalog and use them with Agentforce or other supported MCP clients. Use MCP servers to give standardized access to your existing Salesforce and external services without custom integrations.
Manage MuleSoft MCP Servers in API Catalog: Discover MuleSoft MCP servers to use in Agentforce. Sync eligible new and updated versions of MCP servers from Anypoint Platform into your catalog. Then, create connections for them and add tools you allow the servers to use.
Deploy API Catalog Data Using Change Sets: After you create, test, and debug your API Catalog configuration in a sandbox, use a change set to send the catalog and its associated dependencies, such as external services entries and named credentials, to production when you’re ready to deploy.
Remove APIs from API Catalog: You can remove entire APIs from API Catalog for all supported sources. You can also remove specific MuleSoft API versions. Keep your catalog current to use the latest APIs, including their associated actions.
Remove MCP Servers from API Catalog: You can remove custom Salesforce, MuleSoft, and manually registered external MCP servers from API Catalog.
Example of Using MuleSoft for Agentforce: Consider a scenario where a fictitious company called Enchanted Entertainment wants to create a service agent to manage theme park reservations and experiences. They've developed APIs using MuleSoft Anypoint Platform to integrate with external systems. Now, they need to connect these APIs to their service agent. Here’s how API Catalog can help with that.
Example of Using Actions in Flow: Consider a situation where you want to connect Salesforce to a credit service that has an API that’s managed in MuleSoft Anypoint Platform. The credit service retrieves the customer’s credit score, determines whether the customer qualifies for the credit service, and provides the payment terms. You want to extend the credit service to a Salesforce account so that you can view the payment terms in Salesforce.
View Agents That Use an External MCP Server: See which Agentforce agents use tools from an external MCP server. Open an agent from the Usage tab to review it in Agentforce Studio.
View APIs in API Catalog: After you bring APIs into your API catalog, view and search the list views. Use your catalog as a central place to find APIs and actions to use in Salesforce.
Classic Approval Process History Reports: If you create a custom report type for classic approval process instances, users can view the historical details of completed and in-progress classic approval processes and their individual steps.
Fields Available for Classic Approval Process History Reports: If you create a custom report type with Process Instance as the primary object and Process Instance Node as the related object, you can create approval history reports with various combinations of fields that enable you to view a detailed history of executed and in-progress classic approval processes and their individual steps.
Add Automated Actions to a Classic Approval Process: You can associate actions to approval steps, initial submission, final approval, final rejection, or recall. Classic approval processes support four automated actions.
Groups of Automated Actions in a Classic Approval Process: Each classic approval process is organized into groups of actions based on when the actions occur, such as initial submission. To add an automated action to your classic approval process, determine which group of actions to add it to.
Let Users Respond to Classic Approval Process Requests from Chatter: If your users don’t need in-depth information to decide how to respond to an approval request, enable Approvals in Chatter. That way, they don’t have to leave their feed to continue with their day-to-day tasks.
Considerations for Configuring Classic Approval Processes: When creating or editing a classic approval process, keep in mind how approvals are compatible with other features. Before you start, draw out the steps of your classic approval process.
Merge Fields for Classic Approval Processes: Approval merge fields include {!ApprovalRequest.fieldName} and {!Approval_Requesting_User.fieldName}. They’re supported in certain email templates and return different values based on the status of the classic approval process instance.
Design the Approval Request Page for Classic Approval Processes: The approval page is where an approver responds to an approval request from a classic approval process. Customize which fields appear on that page and in which order. This page is used only for this classic approval process.
Choose an Automated Approver Throughout a Classic Approval Process: Associate a hierarchy field—such as the user’s manager—with a classic approval process. When selected, the field is available as an assigned approver option for approval steps. You can always select a hierarchy field here but not use it for any approval steps.
Specify Who Can Edit Locked Records in a Classic Approval Process: When a record is submitted for approval, it’s locked to prevent users from editing it during the classic approval process. Use the record editability properties to determine who can edit records that are locked in this classic approval process.
Choose Request Notification Templates for a Classic Approval Process: When a classic approval process assigns an approval request to a user, Salesforce sends the user an approval request email. If Approvals in Chatter is enabled, Salesforce also posts the approval request to Chatter. Choose templates for each of these notifications.
Add an Approval Step to a Classic Approval Process: Approval steps define the chain of approval for a particular classic approval process. Each step determines which records can advance to that step, who to assign approval requests to, and whether to let each approver’s delegate respond to the requests. The first step specifies what to do if a record doesn’t advance to that step. Later steps specify what happens if an approver rejects the request.
Enable Classic Approval Processes in Chatter: If your organization has both Approvals and Chatter enabled, administrators can turn on Approvals in Chatter. Users then receive approval requests as posts in their Chatter feeds.
Prepare to Enable Classic Approval Processes in Chatter: Because Approvals in Chatter relies on both Chatter and the Classic Approval Processes feature, getting your org set up involves more than just turning on the feature. Before you enable Approvals in Chatter, understand the limitations and considerations for Approvals in Chatter and post templates.
Enable Approval Notifications for Classic Approval Processes in Slack: If your org uses both classic Approval Processes and Salesforce Digital HQ app, approval notifications are automatically enabled in Slack. Users receive approval requests as messages on the Salesforce Digital HQ’s Messages tab.
Set Up a Classic Approval Process: If classic Approval Processes is the right automation tool for your business process, follow these high-level steps to create one for your org.
Classic Approval Processes Limits: Salesforce limits the number of classic approval processes in your org, as well as the number of steps and actions in each classic approval process.
Prepare Your Org for Classic Approval Processes: Make sure that your users can submit their records for approval using classic approval processes, and consider how you can make it easy for approvers to respond to approval requests.
Respond to an Approval Request from a Classic Approval Process via Email: If your admin enabled email approval response, you can approve or reject requests by responding to the email notification. It doesn’t matter which Salesforce experience or mobile email client you’re using. Delegated approvers can also respond to approval requests by email.
Respond to an Approval Request from a Classic Approval Process: When you receive an approval request, respond to it by approving, rejecting, or reassigning it. Depending on which Salesforce experience you’re using, you have different options. Approval request comments are limited to 4,000 characters. In Chinese, Japanese, or Korean, the limit is 1,333 characters.
Job Candidates Classic Approval Process Example: When your company interviews candidates for a position, you can have several levels of approval before you can send an offer letter. Use this example to create a three-step classic approval process that requires approval from multiple management levels.
PTO Requests Classic Approval Process Example: Most companies require employees to file a PTO (Paid Time Off) request and have their manager approve it. In three phases, here's how to automate a simple one-step PTO request process using Salesforce Classic Approval Processes.
Withdraw a Approval Request That Uses a Classic Approval Process: If you submitted a record for approval but suddenly must update information in the record, recall the approval request. However, whether you can recall an approval request depends on how your admin configured the classic approval process that the record was submitted to.
Subtab Apps in Salesforce Classic: An app is a group of tabs that work as a unit to provide application functionality. Similarly, a subtab app is a collection of tabs that appears on the Chatter profile page. A subtab app can include both default and custom tabs.
Salesforce App Considerations: Keep these considerations in mind when working with apps in either Lightning Experience or Salesforce Classic.
Create Lightning Apps: As in Salesforce Classic, you can create apps in Lightning Experience, but with even more bells and whistles. You can brand and customize Lightning apps to help your users work more efficiently. For example, you can create a Lightning app for your finance department that includes all important items, including tabs, for users to complete common tasks. You can customize the navigation bar color, brand it with a logo, and make the app available in the App Launcher for the user profiles associated with the finance department.
Customize Lightning Apps with the Lightning App Builder: When you edit a Lightning app from the App Manager in Setup, you’re brought into the Lightning App Builder to manage the app’s settings. Update app branding, navigation, and other options, and manage the Lightning pages assigned to that app all in one place.
Tips for Creating Apps in Lightning Experience: It’s time for the fun part: deciding how to set up Lightning apps for your users. Here are some tips for planning Lightning apps for your org.
Upgrade Classic Apps to Lightning Apps: You can upgrade a Classic app to a Lightning app in Lightning Experience, enhancing it for your Lightning Experience users with a customized color, logo, utility bar, and more items like Lightning pages supported in the navigation bar.
Add a Utility Bar to Lightning Apps: The utility bar is a specialized type of Lightning page that gives your users quick access to common productivity tools, like Notes and Recent Items. It appears as a fixed footer that users can access to open utilities in docked panels. Some utilities support pop-out, which lets them open in a new browser window.
Build Your Own Salesforce App: An app is a collection of items that work together to serve a particular function. Salesforce apps come in two flavors: Classic and Lightning. Classic apps are created and managed in Salesforce Classic. Lightning apps are created and managed in Lightning Experience. You can customize both types of app to match the way your users work.
Lightning Apps: With apps in Lightning Experience, members of your org can work more efficiently by easily switching between apps. Users can open apps you’ve created from the App Launcher. What’s most important to sales reps? Accounts, events, and organizations. How about sales managers? Reports and dashboards make the top of the list. Lightning apps take things to another level past Classic apps by letting you brand your apps with a custom color, logo, and utility bar.
Archive Managed Package: Archive by Own from Salesforce helps you manage growing data volumes and improve system performance by automatically archiving old or inactive data. You keep only important and reliable information in production. The Archive managed package not only enhances system performance by reducing data volume but also helps you maintain accurate and consistent data.
Archive Dashboard: The Archive managed package dashboard provides a comprehensive overview of your data, file storage capacity, and other essential metrics.
Archive Field Level Security (FLS) Reports: Field-level security (FLS) settings in Salesforce are used to prevent access to specific fields in the Archive managed package.
Archive Incremental Export: Rather than exporting the entire dataset from the Archive managed package every time, export only the data that was changed or added since the last export.
Archive Limitations: Various limitations and unsupported features for archiving, unarchiving, and other functionalities within the Archive managed package, including policy record limits, object exclusions, and operational constraints.
Use the Archive Mobile Widget: Easily use the Archive managed package from mobiles and tablets. To use the mobile widget, you must enable the settings on the Lightning web page.
Archive Managed Package Activities Tab: View your archive and purge action history from the Activities tab in the Archive managed package. Download logs and reports for the different activities generated, initiate actions, and set up your own customized view.
Archive SDK Data Query: The Archive SDK Data Query enables programmatic access to archived Salesforce data in the Archive managed package. These data queries automate business processes, support third-party system integrations, create custom views and reports, and can cross-reference archived data with active records.
Archive SDK—Right to Be Forgotten (RTBF): Data privacy regulations grant individuals the Right to Be Forgotten (RTBF), requiring organizations to erase personal data securely upon request. Archive SDK enables compliance by identifying and deleting specific data from the Archive managed package, ensuring thorough removal while preserving the integrity of other archived data.
Archive SDK Testing: Before working in your production environment in the Archive managed package, test your Apex Class Wrapper in the Archive SDK. This article explains creating and running tests to ensure the Apex Class Wrapper behaves as expected.
Archive Search: Search for and view the records you've archived in the Archive managed package. Archive Search doesn't enforce role hierarchy, sharing, or visibility rules, so limit access to admins. Standard users use the Archive Widget.
Archive Settings: Configure Archive Managed Package 24 Settings and later. You can access all settings outlined here from the Settings tab in the Archive Managed Package.
Archive Storage Analyzer: Analyze data and file storage consumption in your org to identify archiving opportunities and create policies directly from the analysis workflow.
Archive Widget Restriction Rules: Control end user visibility in Salesforce of specific archived records according to Object Sharing tables. Applicable to CustomListRelatedRecordArchivedWidget and CustomSingleRelatedRecordArchivedWidget in the Archive managed package.
Archive ContentDocuments by Using Parent Object Filtering Criteria: Archive ContentDocument records by using filtering criteria based on parent objects in the Archive managed package. For example, you can archive files associated with Opportunities when the opportunity stage is Closed Lost. You can use this business case to archive specific files while retaining essential Opportunity records in the system. This approach identifies duplicate records.
Export Archive Search Results: Set criteria to find target archived records in the Archive managed package and export the search results. You can download these search results as a CSV file.
Export to Azure Blob Storage: Export archived data in the Archive managed package to Azure Blob Storage and include it in your external reports. Azure Blob Storage, part of Microsoft's cloud platform, is designed to handle large volumes of unstructured data, such as text files and binary data. This export capability supports Azure Data Lake Storage Gen2 for enterprise-level big data analytics.
Export to Amazon S3 Bucket: Export data from the Archive managed package to an Amazon S3 bucket. A S3 bucket covers prerequisites, important considerations, and detailed steps for setting up the export process. These steps include entering AWS credentials, choosing export settings, scheduling automatic exports, and verifying the export.
Get Started with Archive Policies: Create automated jobs on a regular cadence to either archive data from Salesforce according to your needs, or purge from the Archive managed package for compliance or other requirements.
How Purge Policies Work: A purge policy permanently deletes archived records that match your query conditions, up to 1,000,000 records in each run. It doesn't delete records under legal hold or records protected by Archived Data Protected from Purge.
Manage Staged Data: View or clear records in the staging area before archiving them.
Restrict Visibility for Imported Data in the Archive Managed Package: Secure sensitive archived records by manually enabling Archive Widget Search Restriction Rules and uploading custom sharing entries for specific objects. This configuration prevents unauthorized users from accessing imported data in the Archive widget while maintaining visibility for record owners.
Manage Archive Widget Controls and Layout: Enables Archive managed package administrators to centrally manage the display and configuration of objects within widgets, enhancing user visibility and interaction. This functionality allows for defining both root and child objects that end users can query. Additionally, the layout provides insights into parent-child object relationships via the "Is Root" identifier.
Manage Index Fields in Archive: Efficient management of index fields in the Archive managed package is essential for optimizing search and query performance. The Index Fields Setup feature shows admins which fields are indexable so that they can manually select fields to improve search performance. While Archive automatically indexes certain fields based on internal algorithms, some fields can't be indexed at all, and you configure others manually.
Manage Legal Hold Requests in Archive: Place archived records on legal hold by creating a legal hold request in the Archive managed package. Records can be placed on hold multiple times. For example, if a company is facing litigation, any archived records mentioning the involved individual can be placed on legal hold.
Migrate to the Archive App: Migrate your production org from the Archive managed package to the Archive App. The migration process copies your archiving policies, user permissions, and historical logs. The process takes up to one hour, and your Archive managed package remains fully operational during the data copy.
Onboard Archive Customers to Azure Regions: Organizations can expand their data residency options by onboarding to Azure regions. Installing or upgrading to the Archive Managed Package version 24 or higher provides immediate access to the latest regional availability for new and existing environments. You can quickly complete this setup by using the provided package installation link to ensure that your archiving services align with your preferred geographical region. This process streamlines your data management by integrating your Salesforce archiving workflow directly with Azure infrastructure.
Purge Policies: Meet data removal rules by setting purge policies in the Archive managed package that go over the original data expiration set when archiving. These policies permanently delete data.
Archive Regions and IP Addresses for Allowlisting: Find the AWS and Azure data center locations where Archive stores data. To ensure successful connection requests, add the IP addresses for your specific region to your organization's allowlist.
Resolve Archive Page Display Issues: A recent display issue in Salesforce Lightning causes the Activities List View and the Policies (Deprecated) pages in the Archive managed package to display as empty, preventing access to options such as View and New.
Search with the Archive Agent: This article provides guidelines for effectively searching for archived records using the Archive Agent in the Archive managed package. It covers the most critical step of specifying an object directly in your search phrase, how to add criteria for accuracy, and how to work within system limitations to find the records you need.
Self-Service Onboarding for the Archive Managed Package: The Archive managed package helps businesses remove unnecessary data and minimize storage usage, reducing costs, and enhancing operational efficiency. Archive helps you keep old data that is no longer useful, but must be stored for data retention rules or legal reasons.
Set Up the Archive Widget for Lightning: Display archived data as related lists within Salesforce. Even though the data has been archived and is no longer stored directly in Salesforce, end users can still access and view the data in the familiar Salesforce interface in the Archive managed package.
Unarchive SDK: Programmatically unarchive records in the Archive managed package based on specific filters and retrieve search results that match your request.
Update Archive Security Control for Hyperforce Customers: When your Salesforce org migrates from Salesforce-managed first-party data centers to Hyperforce, which runs on public cloud providers, the Archive managed package no longer supports IP allowlisting. To stay connected after migration, turn on Archive Use MTLS Settings.
Upgrade the Archive Managed Package: When a new version of the Archive managed package is available, a notification appears in the Archive Dashboard.
View Archived Records: How archived records are displayed in the Archive managed package, focusing on how Record Types, Page Layouts, and Dynamic Forms affect the user experience. Also, how users can access archived records through Archive Search and the Archive Widget.
View Archived Content Documents Under Non-Archived Emails: Configure a Visualforce page that displays email messages alongside their related archived Content Documents within the CustomListRelatedRecordArchivedWidget and CustomSingleRelatedRecordArchivedWidget in the Archive managed package.
View the Archive Console: View multiple Archive instances and their statuses from one platform in Archive Console.
Assign Action Overrides: To assign a Visualforce page or Lightning component as an override, first create the page or component (or use one created by a Salesforce developer in your org). It’s important to understand the action override options for each user experience and how your selections for each one can affect the others.
Assign a Lightning Record Page Override for the View Action: When you create an override for the View action for Lightning Experience, you can use either a Lightning record page or a Lightning component. To use a Lightning record page as an override, you must activate the page in the Lightning App Builder and choose the type of override you want.
Add Skill Requirements for Work Types in Salesforce Scheduler: Define skill requirements for work types to ensure that an appointment is assigned to a service resource with the right skills. A service resource can be assigned to an appointment only if the resource has all the skills that are required for the work type associated with that appointment. Adding skill requirements to work types saves you time and keeps your business processes consistent.
Assign Global Publisher Layouts to User Profiles: After you finish creating a global publisher layout, you can assign it to different user profiles. For example, a Marketing User and a Standard User need different actions in the Chatter publisher or in the Salesforce mobile app. Create multiple global publisher layouts and assign them to different user profiles to customize the actions for each profile.
Salesforce Connect SQL Adapter for Amazon Athena: Provide your users access to Amazon Athena’s capability to analyze data directly in Amazon Simple Storage Service (Amazon S3) and integrate AWS-hosted data in Salesforce applications.
Map Salesforce External Object Field to Amazon Athena Data Types: External object fields of Salesforce Connect SQL adapter for Amazon Athena can be mapped to columns with scalar types such as strings and numbers. External object fields can’t be mapped to columns containing complex or nested data types such as an array, map, or struct.
Manage Qualifiers for Salesforce Connect SQL Adapter for Amazon Athena: Tables and databases in Amazon Athena contain the metadata definitions for the underlying source data schema. To be able to make queries to Amazon Athena, use qualifiers to specify the key columns that identify records in the Amazon Athena data source.
Enable Debug Mode for Lightning Components: Enable debug mode to make it easier to debug JavaScript code from Lightning components. Only enable debug mode for users who are actively debugging JavaScript. Salesforce is slower for users who have debug mode enabled.
Lightning Component Framework: The Lightning Component framework is a UI framework for developing single-page web apps for mobile and desktop devices.
Authorization Form Objects: Keep track of data related to authorization forms, such as terms of service, privacy policy, and other consent forms. Each authorization form object stores different data. You can use them together to create a full picture of your customer’s consent to the authorization form.
About Automation with Salesforce Flow: Salesforce Flow tools like Flow Builder, Flow Orchestration, and MuleSoft for Flow help you quickly set up and change automation solutions to meet your business needs. These tools combine task and process automation with easy integration solutions, helping you bring together and action on data changes in any system all without writing code.
About Agentforce Operations: Agentforce Operations is a workflow automation platform where you design, run, and track structured business processes. Teams complete tasks by using email, a web form, or the workspace. AI agents can handle specialized tasks automatically.
Add Users to Agentforce Operations: Add new users to Agentforce Operations by assigning them tasks, adding them directly, or adding multiple users in bulk.
Agentforce Operations Tour: Learn the main areas of the Agentforce Operations interface, starting from the Home page. From the Home page, you can view, filter, and manage workflows, and access other areas of Agentforce Operations by using the navigation sidebar.
Document Agent in Agentforce Operations: Use the Document Agent to extract more complicated information from documents, such as images and tables, in Agentforce Operations.
Flash Agent in Agentforce Operations: Use the Agentforce Operations Flash Agent to route and triage work, approve or reject tasks, extract simple information from documents, and fill out forms.
Get AI Agent Tasks Ready for Run Time in Agentforce Operations: Before you publish a blueprint, make sure that your AI agent tasks are tested and producing reliable results. This section walks you through how plans work, how to test them, and how to lock them for consistent run-time behavior in Agentforce Operations.
Excel Agent (Beta) in Agentforce Operations: Use the Excel Agent (beta) as an automation engine in Agentforce Operations. Upload a spreadsheet to drive formula-based calculations, or pass CSV files for row-level operations across tabular data.
Formula-Based Tasks with the Excel Agent (Beta): In formula-based tasks, the Excel Agent uses an existing or generated Excel file to calculate results from stored field values of upstream tasks. The agent stores the results in the task's output fields when Agentforce Operations runs a workflow based on the blueprint.
Tabular Data Tasks with the Excel Agent (Beta): In tabular-data tasks, the Excel Agent processes a CSV file from an upstream task and stores tabular results as a CSV file. It can also store individual values, such as a total or count, in single-value fields.
Generalist Agent (Beta) in Agentforce Operations: Use the Generalist Agent (beta) to automate a broad range of tasks in Agentforce Operations. Supported tasks include routing decisions, calculations, data source queries, table operations, and document processing.
Getting Work Done with Teams in Agentforce Operations: Use teams in Agentforce Operations to group users for task assignment and collaboration. When you assign a task to a team, all team members can see and work on the task. You can also give blueprint and workflow access to teams for collaboration. Set up teams from the Admin page or the People & Teams page, then grant access or assign tasks to teams, or involve them as approvers or as cc'd participants.
Blueprint Limits in Agentforce Operations: Blueprints have limits on the number of tasks, fields, and form items they can contain. These limits help you avoid the performance issues that come with oversized blueprints.
Import a Blueprint from Another Workspace: Export a published blueprint from one workspace and import it into another workspace in Agentforce Operations. During import, review and map the blueprint's dependencies to your workspace.
Build a Blueprint with Conditional Branching in Agentforce Operations Example: Walk through a supplier onboarding blueprint that routes work down different paths based on contract value. This example shows how to set up conditional branching so high-value suppliers go through a compliance review and executive approval while standard suppliers follow a streamlined path.
More Conditional Branching Examples in Agentforce Operations: Use these examples to see how different field types, operators, and values create branches in a blueprint. Each row shows a condition that you can set on a stage and explains what happens when that condition is met.
Customize Blueprint Behavior in Agentforce Operations: Customize how a blueprint behaves at run time. Configure naming conventions, reference IDs, variants, and other settings to standardize and control the workflows that run from a blueprint.
Build Complex Processes with Linked Blueprints in Agentforce Operations: Build complex, multi-stage processes by linking multiple blueprints together in Agentforce Operations. Reuse existing blueprints as building blocks so one workflow can automatically trigger and track another as part of a larger operation.
Add a Linked Blueprint in Agentforce Operations: Nest a child blueprint inside a parent blueprint to trigger a subprocess and pass data between workflows at run time. You can only link blueprints that are in the same workspace.
Track a Linked Child Workflow in Agentforce Operations: When a linked child workflow task starts, Agentforce Operations creates the child workflow. Track child workflows from the Home page or through the parent workflow.
Manage Blueprints in Agentforce Operations: Maintain and evolve your blueprints over time in Agentforce Operations. Learn how versioning works, when to use collaborative editing, and what happens when you delete blueprints.
Manage Workflow Reference IDs in Agentforce Operations: Set up unique reference IDs so Agentforce Operations automatically assigns a trackable identifier to every workflow created from a blueprint, or turn off reference IDs when you no longer need them.
Split a Blueprint's Path in Agentforce Operations: Route workflows down different paths based on field values from earlier stages. Use conditional branching when different inputs lead to different stages, approvals, or outcomes.
Turn on and Manage Blueprint Variants in Agentforce Operations: Turn on variants for a blueprint to collect the same data but run different stages and tasks based on conditions you define in Agentforce Operations. Then create, update, and unlink variants as needed.
Start and Track a Workflow from a Blueprint with Variants: Start a workflow from a standard blueprint with variants. Agentforce Operations automatically selects the matching variant based on the conditions that you defined. Use columns on the Home page to filter and track workflows that Agentforce Operations created from blueprint variants.
How Blueprints, Workflows, and Tasks Connect in Agentforce Operations: In Agentforce Operations, blueprints, workflows, stages, tasks, and fields each play a specific role and work together in a clear hierarchy to automate business processes. Understanding how they connect helps you plan your processes before you start building blueprints and running workflows.
Add and Update Multiple Users in Bulk in Agentforce Operations: Upload a CSV file to invite users to the workspace, add roles to existing users, or update their names. A CSV file can include up to 10,000 rows, including the header row. You can add roles to users. You can't remove or create roles by uploading a CSV file.
Bulk Edit Tasks in Agentforce Operations: Update assignees, CC recipients, or due dates on multiple tasks at a time from the Tasks page or from a user's profile in Agentforce Operations.
Collaborating with External Partners in Agentforce Operations: Invite suppliers, vendors, and other external partners to participate in your workflows in Agentforce Operations. External users can complete tasks through email, forms, or the workspace, with visibility restrictions that protect workspace data.
Complete Tasks in Agentforce Operations: Complete your assigned tasks in the workspace, reply to tasks by email, or use task list views to focus on the tasks that need your attention.
Tasks in Agentforce Operations: Tasks are the individual units of work in a blueprint. Configure tasks to collect the right information, route work to the right people, and shape how each step behaves at run time.
Connect to External Systems in Agentforce Operations: Connect Agentforce Operations to the external systems that your business uses. Bring in reference data for users to work with, or automate data exchange with other systems during workflow execution.
Create an Automation Template with a Blueprint in Agentforce Operations: Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.
Create and Start a Workflow from a Blueprint in Agentforce Operations: Create a workflow from a blueprint to begin automating your business process. You can start a workflow from anywhere in Agentforce Operations, including from a blueprint list, or from inside an open blueprint.
Data Sources in Agentforce Operations: Data sources are tables of structured reference data, such as supplier lists, customer catalogs, or parts databases. Admins import data sources into Agentforce Operations so users can look up and validate that data in workflows and tasks.
Send Reminders and Escalate Tasks in Agentforce Operations: If a task has escalations configured, Agentforce Operations automatically adds assignees or CCs to a task before or after the due date to ensure task completion and to keep key stakeholders informed.
Create Custom Fields in Agentforce Operations: Create custom fields to collect information from users. You can create custom fields from the Fields page, a task, or the Form Builder.
Get Started with Agentforce Operations: Agentforce Operations automates structured business processes by using blueprints, workflows, and AI agents. Learn the concepts and set up your workspace for the first time.
Integrations in Agentforce Operations: Integrations connect Agentforce Operations to external systems and run automatically during workflow execution. Use integrations to send workflow data to an external system, get data from an API, or save files to cloud storage without any user interaction.
Custom HTTP Integrations in Agentforce Operations: With Custom HTTP integrations Agentforce Operations can call HTTP APIs to exchange data with external systems during workflow execution. Use them to send workflow data to an API, get data from an API for use in a workflow, or search external datasets based on workflow parameters.
Example Simple Custom HTTP Integration in Agentforce Operations: Walk through an end-to-end example of creating a custom HTTP integration that looks up city and state information for a US postal code, and then adding it to a blueprint as an automation task.
Manage Users in Agentforce Operations: Add users to your workspace, assign roles that control access, and manage user accounts. Users can be internal employees or external partners.
Pause, Resume, or End a Workflow in Agentforce Operations: Pause a workflow to temporarily stop the workflow from running. Then, resume the paused workflow when you’re ready for it to start running again. Or end a workflow to stop it permanently.
User Roles and Access Levels in Agentforce Operations: Assign specific roles to users that define what they can do in Agentforce Operations. You can use the system roles, or create custom roles. Grant granular access levels to blueprints and workflows.
Set Up a Team in Agentforce Operations: Create and configure teams in Agentforce Operations. With teams, you can group users together for easier task assignment and collaboration. When you assign a task to a team, all team members can see and work on the task.
Set Up Your Workspace in Agentforce Operations: After you get access to your workspace, complete these setup steps to prepare Agentforce Operations for your team. Configure settings, add users, build a blueprint, and start your first workflow.
Logging In to Agentforce Operations: Log in to Agentforce Operations by using your invite email, and learn when you need to log in and when you don't need to log in.
Stages in Agentforce Operations: Stages organize the tasks in a blueprint into logical phases. Use stages to break a process into manageable milestones and control when each part of the workflow runs.
Turn On Starting a Workflow from an Email: Configure the blueprint so stakeholders can start workflows by sending an email without signing in to Agentforce Operations.
Task Assignee Types in Agentforce Operations: You can assign tasks to multiple people, teams, roles, and AI agents. Determine the correct assignee based on task requirements and assignee type behavior.
Work with Tasks Through Email in Agentforce Operations: Reply to, complete, and approve Agentforce Operations tasks from your email. A summary of the task details and what's required is in the task assignment email. If you're logged in to Agentforce Operations, clicking a button in the email takes you directly to the task in the workspace instead of a web form.
Task Types in Agentforce Operations: Choose the task type that matches the work you want to accomplish. Learn how to create standard tasks, approval tasks, and email notification tasks.
Save Task Data as a PDF in Agentforce Operations: Configure a task to save a copy of the submitted data as a PDF. Use the PDF to save the information, to share with form fillers, or to pass to downstream tasks.
Complete Multiple Tasks at a Time in Agentforce Operations: When you have 5 or more tasks of the same name and type from the same blueprint, Agentforce Operations creates a smart view. From the smart view, you can enter information and complete multiple tasks at a time.
Track Workflows in Agentforce Operations: Monitor workflow activity, status, and progress so you can spot bottlenecks, manage due dates, and keep work on schedule. Use the Home page, list views, and filters to focus on the workflows that matter most to you.
How Workflows Lock to a Blueprint Version in Agentforce Operations: When a workflow starts, it pins itself to the blueprint version that was current at the time. Learn how version locking affects running workflows when updating a blueprint in Agentforce Operations.
Run and Manage Automated Workflows in Agentforce Operations: Workflows are the running instance of your process that move through stages and tasks until they complete. Most workflows run from blueprints, but you can also create them directly. Learn how workflows progress, how to track and edit them, who can access them, and how to pause or end them.
Write Effective Instructions for AI Agent in Agentforce Operations: When configuring a task assigned to an AI agent, use these guidelines to write effective instructions in the Description field in Agentforce Operations. Clear instructions lead to more reliable results.
Automation App: Monitor and manage your existing flows and orchestrations from the Automation Lightning app.
View and Search Invocable Actions (Beta): Quickly find standard and custom invocable actions used in Flow Builder. Agentforce Builder, and Prompt Builder by using the Action Hub tab in the Automation Lightning app. Search the list of actions or filter them by action type, and then select an action to review its details and identify where it’s used.
Monitor Flow Performance with Flow Logs: Use the Flow Logs tab in the Automation Lightning app to set up Data 360 and configure flow logging. Then track performance metrics for your enabled flows.
Flows Tab of the Automation App: The Flows tab includes various standard list views or any list views that you create. Search for keywords in flow labels or descriptions. Filter or sort flows by fields like type, status, last modified date, last modifying user, and associated record fields. If you have the appropriate permissions, create flows in Flow Builder right from the Flows tab.
Home Tab of the Automation App: The Home tab includes list views of your most recently modified flows and flows that are configured with errors. Search for flows using a keyword in the flow label or description. Additionally, find direct links to helpful resources.
Monitoring and Managing Paused and Failed Flow Interviews: Easily track and manage all your failed and paused flow interviews in the Automation Lightning app. The Monitor tab shows all failed and paused flow interviews and why they failed or paused.
Orchestrations Tab of the Automation App: The Orchestrations tab includes a number of standard orchestration list views and any list views that you create. Search for keywords in orchestration labels or descriptions. Filter or sort orchestrations by fields like trigger type, status, or last modified date. View and manage related orchestration runs for a selected orchestration.
Manage Orchestration Runs: Cancel, debug, suspend, and resume orchestration runs from the Automation Lightning app.
View Orchestration Runs Related to an Orchestration: View orchestration run records that are related to an orchestration. You can also view the orchestration stage run, orchestration step run, and orchestration run log records related to a selected orchestration run.
Accelerate Integrations with Templates and AI Pre-Built Flows: Use a MuleSoft for Flow: Integration template to configure connectors or use AI pre-built flows to build your flow logic. These tools eliminate starting from scratch, so you can accelerate integration and customize automation for your business.
Automate Your Approvals with Flow Approval Processes: As your company grows, so does the complexity of your approvals, often requiring input from multiple people in different departments across different time zones. This complexity can mean that you spend more time waiting for each person to complete their review in the right order. Flow Approval Processes helps you coordinate multistep reviews that involve users, systems, and conditional paths.
About Flow Approval Processes: Review Flow Approval Processes permissions, editions, limitations, considerations, and entitlements.
Handle Stage Errors in Flow Approval Processes: Set up fault paths to handle errors in flow approval processes. Create fault paths for each stage and add elements that trigger when errors occur in that stage or its steps. This approach minimizes the likelihood of approval submissions failing due to stage errors.
Add Recall Actions to a Flow Approval Process: To run steps when an in-progress flow approval process is recalled, add a Recall path. A recall path can contain a single stage with background steps. When the submission is recalled, the stage that was in-progress and all of its steps that haven’t been completed are canceled. Open approval work items are also canceled. The stage in the recall path then runs. When the stage in the recall path is completed, the approval submission is recalled.
Approval Submissions and Orchestration Runs: Salesforce creates an approval submission when a record is submitted for approval by using a flow approval process. Each approval submission has an associated orchestration run.
Build a Flow Approval Process: It’s easier to automate an approval process when you understand how the approval pieces fit together. Before you create a flow approval process, talk to your stakeholders to understand the requirements. You can save draft flow approval processes without knowing all the required information, but you must specify all associated flows and configuration details before you can activate and run your flow approval process.
Add an Approval Work Item List Object Page to an Experience Cloud Site: Internal users can view and manage their assigned work from the Approvals app or the Approval Work Items list view. Add the Approval work item List object page to your Aura or LWR site so that credentialed site visitors can see and access their assigned approvals work items.
Make Assigned Approval Work Items Accessible on a Record Page: Add the Orchestration Work Guide component to the record page layouts for record types referenced by approval steps. Configure the component so that assigned users can access and complete their approval work items.
Use Automatic Output in Flow Approval Processes: A flow approval process has access to output for its stages, steps, and decisions. Query the status of any stage or step in the flow approval process. Use output parameters from any step’s associated flow. In a flow approval process, referenced automatic outputs that contain a record or a record collection are refreshed with their latest values each time the orchestration run associated with an approval submission resumes.
Create a Flow Approval Process: Create autolaunched flow approval processes in the Approvals app. In Setup, create autolaunched or record-triggered flow approval processes.
Create a Step to Interact with Approvers: Create approval steps to assign flow approval processes to specific people, groups, or queues. Approval steps generate work items that assigned approvers can approve or reject with or without running the associated flow. Approvers can complete approval work items via email when you enable email approval response in Process Automation Settings.
Control Which Element Runs Next in a Flow Approval Process: Flow approval processes use Auto-Layout in Flow Builder. In Auto-Layout, elements on the canvas are spaced and connected automatically. Use Go To connectors when you have elements that don’t follow the usual consecutive auto-layout path.
Add an End Element to a Flow Approval Process Path: All elements in a flow approval process are connected automatically, or they’re connected by Go To connectors that you add manually. To finish a path in your flow approval process, add an End element.
Make Approval Work Items Accessible to Assigned Approvers: When an orchestration run associated with an approval submission runs an approval step, by default, it emails a notification to the assigned approver, group, or queue and their delegates. Internal users and credentialed Experience Cloud site visitors can complete their assigned work in multiple ways.
Define Requirements for Stages and Steps in a Flow Approval Process: Use requirements to resume an orchestration run when a record changes. Define up to 10 requirements to determine when a step is ready to start or when to mark a stage or an approval step as completed.
Route Approval Work Items with Omni-Channel: To use Omni-Channel routing in Service with approval work items, you must have at least 1 queue associated with the Approval Work Item object. When you assign an approval step to that queue, members of the queue receive notifications via the Omni-Channel widget based on your routing logic. Unless you disable default email notifications for approval work items, queue members also receive email notifications.
Work with Flow Approval Process Templates: Create a template based on an existing flow approval process or turn an existing flow approval process into a template. Then use the template as a starting point for creating other flow approval processes in Flow Builder. You can also distribute the template via a managed package so that subscribers can create flow approval processes based on it.
Cancel an In-Progress Approval Submission: Cancel an approval submission from the Approval Submissions list view. You can cancel only in-progress approval submissions.
Flow Approval Processes: A flow approval process contains stages, steps, and decisions to organize complex approval sequences. Create flow approval processes by using the Flow Approval Process tiles in the New Automation window. Create autolaunched flow approval processes in the Approval app. Build flow approval processes in Flow Builder.
Record Locking in Flow Approval Processes: Record locking controls who can change a record associated with an in-progress approval submission. The way you implement record locking depends on whether the approval steps in a flow approval process stage run consecutively or concurrently.
Flow Approval Processes Concepts: Learn about what a flow approval process is made of and how it relates to orchestration runs, flows, approval submissions, and approval work items.
Approval Steps: Approval steps require user interaction and create approval actions that assigned approvers or delegates can complete asynchronously. Approvers can complete reviews without running the associated flow, so include only actions directly relevant to the approval work item. Use a background step after the approval step to update related records or send other notifications.
Flow Approval Process Notification Emails: By default, a flow approval process sends email notifications to approval submitters, assigned approvers, and approvers’ delegates.
Background Steps: A background step launches an active autolaunched flow and has no user interaction. You can control when a background step is ready to start. Use background steps to carry out actions that are related to an approval submission but aren’t part of an approval work item. For example, use a background step to update records or trigger other notifications related to the approval.
Flows in Flow Approval Processes: Each background and approval step in a flow approval process runs an associated flow. If the logic for controlling stage and step execution calls for more than 10 requirements, use an evaluation flow to create more complex criteria.
Evaluation Flows for Flow Approval Processes: When you need more than 10 requirements to control stage and step execution, use an evaluation flow. Select the Evaluation Flow tile in the New Automation window to create an evaluation flow.
Running Context of a Flow Approval Process: The running context determines the access that a flow approval process has to Salesforce data and the context used by a paused flow approval process to resume. By default, the running context of an autolaunched or record-triggered flow approval process is the Automated Process User in system context.
Stages in Flow Approval Processes: A stage groups related steps, organizing them into a logical phase. Stages are executed sequentially, and only one stage in a flow approval process can be in progress at a time. You configure the conditions that must be met for the stage to be considered complete.
Steps in Flow Approval Processes: Steps are grouped in stages and can be run sequentially, concurrently, or when specified requirements are met. Approval steps assign the completion of an active screen flow to a person, group, or queue and require user intervention. Background steps run an active autolaunched flow synchronously or asynchronously and have no user interaction.
Triggers for Flow Approval Processes: Creating or updating a record can start a record-triggered flow approval process. In the Start element of a record-triggered flow approval process, configure the conditions for the trigger. Use Flow Trigger Explorer to order record-triggered flow approval processes, orchestrations, and flows.
Flow Approval Process Types: The type of a flow approval process determines how it's triggered and who can start it. Determine which type to use based on what starts the approval process and how much control you need over when it runs.
Flow Approval Process Versioning: Flow approval processes have two levels of versioning: the version of the flow approval process and the version of a flow called by a flow approval process.
Approval Work Items and Orchestration Work Items: Approval steps create work items assigned to users, groups, or queues. Approval steps also automatically send email notifications to approvers. Approvers complete approval work items through the Orchestration Work Guide component, email responses, or the Approval Work Items list view. Each approval work item is linked to an orchestration work item.
Considerations for Evaluation Flows for Flow Approval Processes: An evaluation flow is an autolaunched flow with a process type of Evaluation Flow that contains a predefined Boolean output variable. Use evaluation flows to define complex entry or exit conditions in flow approval processes. Before you use an evaluation flow, review the general guidelines and how to manage the predefined output variable.
General Flow Approval Processes Limits: When using flow approval processes, keep flow approval process limits, flow limits, and Apex governor limits in mind.
Considerations for Migrating from Approval Processes: Before you design flow approval processes with Flow Approval Processes to replace approval processes created with Approval Processes, get familiar with the known gaps between the features.
Considerations for Flow Approval Processes: Consider entry and exit condition requirements, events triggered by record changes, input values, and email notifications when you design and use flow approval processes.
Create a Flow Approval Process from Scratch: You can create flow approval processes in Flow Builder, including autolaunched flow approval processes from the Approvals app and autolaunched or record-triggered flow approval process from Setup.
Customize Emails to Approvers: By default, each time an orchestration run associated with an approval submission creates an approval work item, assigned approvers and their delegates receive a notification. To change the email notification sent to both approvers and their delegates, customize the associated approval step.
Add a Custom Button to Run an Autolaunched Flow Approval Process: After you create a button that runs an active, autolaunched flow approval process, add it to the Lightning Experience record page layout for the affected object. After it’s added to the record page layout, users can manually submit records for approval.
Make Autolaunched Flow Approval Processes Available to Users: Approvals based on an active, record-triggered flow approval process automatically run when a record is added or updated and meets the flow approval process’s entry criteria. However, approvals based on an active, autolaunched flow approval process aren’t run automatically. Before a user can manually submit an approval, create a button that calls an active autolaunched flow approval process and add the button to the relevant record page.
Configure a Single Flow Approval Process for a Record Page: Add the Request Approval component to a record page layout in Lightning App Builder. Submitters can submit a record for approval by using the component. Configure the component so that submitters can select an approver and add submission comments. You can configure only one flow approval process in the Request Approval component.
Configure a Single Flow Approval Process for an Experience Cloud Site: Add the Request Approval component to an object details page layout in Experience Builder. Credentialed Experience Cloud site visitors can submit a record for approval by using the component. Configure the component so that submitters can select an approver and add submission comments. You can configure only one flow approval process in the Request Approval component.
Configure Multiple Flow Approval Processes for a Record Page: Add the Request Approvals component to a record page layout in Lightning App Builder. Configure up to 10 flow approval processes in the component so that submitters can select the process they prefer for submission. You can configure each flow approval process so that submitters can select an approver and add submission comments.
Deploy a Flow Approval Process: After you’ve designed and tested your flow approval process, you’re ready to put it to work.
Activate or Deactivate a Flow Approval Process: You can have multiple versions of a flow approval process in Salesforce, but only one version of each flow approval process can be active at a time. You can activate or deactivate a flow approval process in Flow Builder or from the flow approval process’s detail page in Setup.
Error Handling in Flow Approval Processes: Error handling addresses how to manage unexpected issues that can occur when a flow approval process runs. Configure fault paths for stages to define actions to take if issues occur, ensuring that approval submissions are approved or rejected instead of failing.
Manage Approval Submissions and Approval Work Items: Manage approval submissions and approval work items with list views. Recall an in-progress approval submission. Reassign approval work items that have been assigned but not completed.
Add the Automation Usage Component to View Flow Approval Process Dependencies: The Approvals app shows the flows that a flow approval process version uses and the flow versions that use a flow approval process. The Approvals app uses the default Orchestration Version and Orchestration pages to show this information. If you customized either page, add the Automation Usage component and save the updated page as your org default.
Control Approver Emails for a Flow Approval Process: To stop sending email notifications to approvers and their delegates for approval submissions based on a specific flow approval process, use the advanced setting Don’t send approver notifications.
Manage Approval Email Notifications: By default, a flow approval process sends email notifications to assigned approvers, their delegates, and approval submitters. Use approval email settings to manage emails sent to these groups.
Control Email Completion of Flow Approval Processes Approval Work Items: By default, assigned approvers and their delegates receive email notifications when an approval work item is created or reassigned. When approvers and their delegates receive email notifications, you can make it possible for them to complete approval work items associated with Flow Approval Processes approval submissions by replying to their email notifications.
Delete Approval Submission Records: Delete approval submission records to fulfill GDPR and other data deletion requests. Deleting a parent record also deletes its related terminal-state approval submissions. Salesforce cancels related in-progress approval submissions so that you can delete them later.
Determine Flow Usage in a Flow Approval Process Version: Flow approval process versions use flows to run approval and background steps. Flow approval process version stages and steps can use flows to evaluate complex criteria. Those criteria can determine when a background or approval step starts and when to mark a stage or approval step as completed. View the flows that a flow approval process version uses to understand these relationships.
Determine Flow Approval Process Usage in Flow Versions: Flow versions can call a flow approval process from an Action element using the Request Approval action. View the flow versions that use an autolaunched flow approval process before making changes to the active flow approval process version.
Reassign an Approval Work Item: Reassign an assigned approval work item to a different user, group, or queue. You can reassign an assigned work item for an approval orchestration that’s still in progress.
Recall an In-Progress Approval Submission: Recall an approval submission from the Approval Submissions list view. You can recall only in-progress approval submissions.
View Approval Submissions: Use approval submissions list views to see lists of and details about approval submissions.
View Flow Approval Process Dependencies in the Approvals App: Flow approval processes rely on flows to run steps and evaluate complex conditions. Flows can also use an Action element to call a flow approval process. To understand the relationships between a flow approval process and the flows that it call and that call it, view the Usage tab of the Orchestration Version page or the Orchestration page in the Approvals Lightning app.
View All Approval Work Items: Use approval work item list views to see details about approval work items. Use the quick menu to approve or reject an approval work item without running the associated screen flow.
View Approval Work Items on a Record: Assigned approval work items appear directly on record pages in the Orchestration Work Guide component. Sort items by date, prioritize tasks, and track completion status.
Flow Approval Processes Reference: Bookmark this page for quick access to information about flow approval process elements, resources, events, and more.
Flow Approval Processes Connectors: Connectors determine the available paths that a flow approval process can take at run time. On the canvas in Flow Builder, a connector is a line that connects one element to another.
Flow Approval Processes Elements: Each element represents an action that the flow approval process can execute. Flow approval processes can contain Decision and Stage elements.
Decision Flow Approval Processes Resource: Evaluate a set of conditions, and then route users through the flow approval process based on the outcomes of those conditions. This element performs the equivalent of an if-then statement.
Flow Approval Processes Operators: In conditions and filters, use operators to evaluate information and narrow the scope of a flow approval process operation.
Flow Approval Processes Version Properties: A flow approval process version’s properties consist of its label and description. These values drive the field values that appear on the flow approval process’s detail page.
Global Variables Flow Approval Processes Resource: System-provided variables store information that you can reference throughout a flow approval process. For example, it can contain information about the Salesforce org, running user, or triggering record.
$Flow Global Variables Flow Approval Processes Resource: Some $Flow global variables provide information about the orchestration run associated with a parent approval submission. Some variables contain system-provided values. You can update the other variables throughout the flow approval process by storing output values in the variables. Because flow approval processes don't support Assignment elements, flow approval processes don't support any global variables that are assigned values with the Assignment element.
Troubleshoot Approval Submissions: When an approval submission fails, the orchestration run associated with it fails and sends a fault email. To view details about a failed approval submission, use the orchestration run fault email.
Debug a Flow Approval Process and Keep Data Changes: Test and troubleshoot your flow approval process with database updates. Set a start point to skip earlier stages, an end point to stop before later stages, or both to isolate a middle segment. You can also set mock outputs for steps. A step that uses mock output doesn't run its referenced flow or make changes to the Salesforce database. You're the assigned user for all approval steps without defined mock output that meet their entry conditions.
Debug a Flow Approval Process Without Changing Your Data: Debug your flow approval process in Flow Builder to ensure that it runs as expected or to determine the cause of unexpected errors. Use rollback mode to debug your flow approval process without making changes to your Salesforce data.
Emails About Flow Approval Process Errors: When an approval submission's orchestration run fails, Salesforce sends an error email. The email is sent to either the admin who last modified the associated flow approval process or the Apex exception email recipients.
Create a Flow with a Connector as an Action: To integrate your flow with an external system, add MuleSoft for Flow: Integration connectors as actions to all existing flow types. You can add connectors to flows that trigger external system changes, records, schedules, Data Cloud-triggered flows, or autolaunched flows.
Create a Flow with a Connector as a Trigger: To trigger a flow when a change happens in a third-party system, use an External System Change-Triggered flow. A poller checks for new records on a schedule and creates flow interviews when records are found. Create the flow from scratch or from a template.
Connecting to an External System with a Connector: You can use MuleSoft for Flow: Integration connectors in any flow type to connect a flow's actions to an external system. To trigger a flow when an external system changes, select the External System Change-Triggered flow type.
About Flows and Flow Builder: Using Flow Builder to automate routine tasks, like creating follow-up tasks, sending reminder emails, or updating records, makes work more efficient and productive so employees can focus on more strategic work.
Advanced Screen Flow Options: Add advanced capabilities to screen flows, such as displaying record fields directly on screens and translating content for international users.
Defining Screen Component Options With Choice Resources: Define options for users to select from in screen flow components like picklists, radio buttons, and checkbox groups. Create choices to control the options users see and the values stored when they make selections.
Copy an Audience Flow: Save an audience flow as a copy without disrupting live campaigns.
Get a Basic Screen Flow Ready for Users: Create a basic screen flow and get it ready for your users to run. Add screen elements and screen components to gather information, set up what happens with that information, test that everything works, and roll it out to your users.
Create a Broadcast Flow: Use broadcast flows with dynamic segments to quickly reach large, targeted audiences. For example, notify affected customers about flight delays or reservation changes.
Create a Segment Flow: Create a segment-triggered flow that runs on a schedule and sends messages to a segment of people. You can set a segment-triggered flow to run once, either immediately or at a specific time and date, or you can set the flow to run on a recurring schedule.
Customize Screen Style and Layout in a Screen Flow: Get the look that you want by changing the style of your entire screen or individual components. Organize your screen components into columns, and adjust component width and vertical alignment to control spacing and positioning. Style changes override the theme styling for your org or Experience Cloud site. If you enter an invalid value for a style property, the screen flow uses your theme’s style property instead.
Create a Child Flow to Clone a Record: Build a reusable autolaunched flow that accepts a record as input and creates a clone with all field values the running user can edit. A parent flow calls this child flow using a Subflow element and receives the cloned record as output. Complete this task before building the parent flow.
Create a Parent Flow to Clone a Record Using a Child Flow: After you create and activate the child flow that clones a record, build the parent flow that gets the source record and passes it to the child flow using a Subflow element. The Subflow element's output gives you access to the cloned record for use later in the parent flow.
Global Model Data Opt-In and Opt-Out for Flows Created by Agentforce (Beta): Agentforce intelligence is built on data. The more data Agentforce has, the more powerful the resulting predictions. Most companies don’t have enough data to build their own models. To give you more meaningful generative AI, Salesforce builds global generative models that generate and edit flows and answer flow-related questions. To protect your customer data, your account is opted out of the global data model by default.
Use Records to Trigger Actions in External Systems Example: This example creates a flow that uses a third-party connector to take action in an external system, such as creating a sales order in NetSuite after an order is created or updated in Salesforce.
Evolve a Flow with Agentforce (Beta): Improve and modify your existing flows by using natural language in the Agentforce panel. Through conversational prompts, add new elements, update properties and conditions, and remove outdated components.
Bulkified Record Processing to Avoid CPU Limits Example: Learn how to refactor flows to use bulkification patterns that prevent APEX_CPU_TIME_LIMIT_EXCEEDED errors. This example demonstrates the difference between inefficient and optimized flow design.
Keep Users Informed With a Message Screen Component: Use a screen flow to collect contact and company information, then call an autolaunched flow to create account and contact records. Show a message to the running user about the new records by using a Message screen component. Then send the contact an email.
Creating Records with Required Field Validation Example: Build a screen flow that captures all required fields and creates records without REQUIRED_FIELD_MISSING errors. This example demonstrates techniques for identifying required fields and managing errors in flows.
Identify Required Fields: Before building a flow, identify the required fields for the object's records. There are two options: use Schema Builder or create a record on the object, but don't save it. Either option shows the required fields, but Schema Builder also shows system populated fields that you don't include in a flow.
Email Contacts that a User Selects on a Screen Example: This example uses an automatically triggered screen action to let users select an account and instantly view or select related contacts—all within a single screen. Then, it sends the selected contacts an email.
Create Multiple Records with a Repeater Screen Component Example: This example creates screen flows that use Repeater components to collect information for multiple related items and perform bulk actions on that data. Use Repeater components when you need to gather the same type of information for multiple records, such as collecting product information for multiple items. The flow can then automatically create and link related records based on the collected information.
Send Follow-Up Email Using an Email Template Example: Walk through a complete example of a record-triggered flow that automatically sends a follow-up email to a case contact when a case is closed. This example uses the Send Email action with an existing email template that includes recipient merge fields.
Send a Custom Notification with a Flow: Create a flow that sends a custom notification to users when a specific event occurs. Custom notifications appear in the notification bell and can be delivered to the Salesforce desktop or mobile app.
Send an Email from a Flow Example: This example uses the Send Email action to send an email to a new contact. Your sales reps might forget to email new customers to welcome them, so you want to email the new contacts automatically with a flow.
Send and Log Your Email Example: This example uses the Send Email action to send and log an email to a contact. Your sales reps might forget to email your customer when an opportunity's stage is updated, so you want to email the customer and log it automatically with a flow.
Send an Email from a Flow with an Attachment: Create a flow to send an email from a flow with an attached file. This allows you to include files stored in Salesforce in your emails.
Send an Email with Attachments in a Record-Triggered Flow Example: When your sales team is ready to send out proposal documents to the contacts involved with the opportunity, use this example flow to automatically send an email with the attachments to those contacts. This flow stores the attachment IDs in a collection variable and then passes the collection variable into the Send Email action's attachment ID collection field.
Update Records and Send Reminders on a Schedule Example: This example creates schedule-triggered flows that automatically update records and send notifications to contacts based on your business schedule. Use flows to replace manual processes, such as spreadsheet tracking, with automated workflows that check record status, send timely reminders, and update data when conditions are met. This method maintains data accuracy and timely customer communication while reducing manual work.
Use an Online Form to Create a Record Example: Create a screen flow that collects information about a new opportunity and then automatically creates an opportunity record. For example, on customer calls, your reps scramble to capture notes about customer interest in new products. They often use sticky notes, which are hard to read or get lost. Create an online form embedded on the case record page so they can quickly capture and confirm basic information. When they submit the form, the screen flow creates a new opportunity on the Account record that’s related to the case.
Decide Between Before-Save and After-Save Record-Triggered Flows: Record-triggered flows run when someone creates, updates, or deletes a record in Salesforce. Before-save flows run before Salesforce saves the record. After-save flows run after Salesforce saves the record. Use this guide to pick the right type for your automation.
Create a Simple After-Save Record-Triggered Flow: Learn how to build an after-save record-triggered flow that automatically creates a record. This example creates a follow-up task whenever a user creates a lead record, ensuring your team never misses an important next step.
Getting Started with Record-Triggered Flows: Record-triggered flows automatically run when someone creates, updates, or deletes a record in Salesforce. After they’re triggered, they perform actions such as updating records, creating records, and sending emails. There are two types of record-triggered flows. Learn how they differ so you can use the one that works best for your situation.
Start an Automation When a Record Is Created or Changed: Record-triggered flows automatically run when someone creates, updates, or deletes a record in Salesforce. Think of them as helpful assistants that work behind the scenes to automate tasks, check data, and keep your records up to date—without you doing anything.
Getting Started with Screen Flows: Create interactive screen flows that guide users through processes by using screen elements, screen components, and other elements to process data.
Group Flow Elements in Auto-Layout: Organize related flow elements into named, collapsible sections to make complex flows easier to navigate and maintain.
Collapse or Expand Groups: Collapse a group of elements in a flow to hide its elements and simplify the canvas, or expand it to work with the elements inside.
Create a Group: Add an empty group to your flow to organize related elements into a named section.
Delete a Group: Remove a group from your flow, either deleting its elements along with it or keeping them on the path.
Edit a Group: Update a group's name and description to keep your flow's sections clear and accurate.
Move an Element to a Group: Move an existing element into a group, even if it's already in a different group.
Help Users Select Faster by Using Visual Cues in Choices: Associate familiar icons with choices to help users make selections faster. Choice resources with icons display as dropdown lists in Choice Lookup components and as tiles in Visual Picker components at run time. Icon-based choice resources are supported in all screen-based flows except Field Service Mobile and Discovery Framework Data Capture.
Join Collections in a Flow: Combine source collections from related flow resources into one target collection.
Make Your Screen Flows More User Friendly: Create intuitive screen flows that guide users through every step. Customize screen styles and layouts, display progress indicators, and validate input so users know immediately if they've made a mistake. Use conditional visibility to show only relevant components, and implement reactivity and screen actions to make screens respond dynamically to user input. Help users make informed choices with visual cues, and translate screen components for multilingual audiences.
Create and Manage Value Maps: Create, update, and delete value maps from the Global Flow Resources page to reuse mapping logic across flows.
Send Personalized Marketing Emails from a Flow: Add content variables to a marketing email template to capture personalized information, such as the recipient name and date. When building a marketing flow, map the variables to flow resources in a Send Email Message element to provide the personalized information.
Preview Screen Layout and Styles: See how your screen flows appear to users when the flows are added to Lightning Experience and Experience Cloud sites. Ensure that the flows match the look and feel of Lightning Experience or Experience Cloud sites before you activate the flows. Additionally, preview how your screen looks on different screen sizes.
Show Screen Flow Stages in a Progress Indicator Example: This example creates a custom progress indicator stage that guides users through a multi-step process. By creating clear stages and assigning them to screen elements, you can enhance user experience and ensure that users understand their progress and next steps.
Create the Autolaunched Flow and Setup the Action: Create and activate the autolaunched flow that you want to be triggered by a screen action. You want to create the autolaunched flow before configuring the screen action because you select the active autolaunched flow when you set up the screen action.
Screen Flow Examples: Follow step-by-step examples that show you how to build common screen flow solutions.
Configuring Screen Elements: Configure the overall screen properties to control what text users see and how users interact with the screen by configuring the header, footer, navigation buttons, and help text.
Send and Log an Email from a Flow: Send and log an email to a contact record or a related account record from a flow using an email template that's created before you create the flow .
Send an Email from a Flow Using an Existing Email Alert: If you're using an email alert in a Workflow Process or Process Builder process, you can use the existing email alert in a flow. The email alert works the same whether it's triggered by a flow, a Workflow Rule, or a Process Builder process.
Send an Email with an Attachment in an Autolaunched Flow Example: Use the Send Email action to send an email with an attachment to all employees living in a city. For example, you want to send an important update to all employees living in San Francisco and add attachments to your email.
Send an Email Using a Text Template Flow Resource Example: Use the Send Email action to send an email to your customers each time the status of their order changes using a text template flow resource. For example, your sales reps don't have time to keep sending emails to customers to update them on their orders. You want to email the customers automatically with a flow.
Send a Plain Text Email from a Flow: Send a quick internal plain text email from a flow. If you don't want any formatting or merge fields in your email, you can enter plain text right into a Send Email action in a flow. Your recipient can be any email address, including a secondary email address on a record.
Send an Email from a Flow Using an Existing Email Template: Use an existing email template with the Send Email action to send consistent, reusable email content from any flow type. Email templates support merge fields from the recipient, their organization, and sender records, and can be reused across multiple flows.
Send Emails with a Flow Using Text Templates: Text templates create reusable email content with dynamic merge fields from any record. Send emails to any address and reuse the same template across multiple flow actions. This approach offers more flexibility than the standard Send Email body field.
Summarize Flows with Agentforce (Beta): Use Agentforce to summarize new flows, existing flows, and even flows that Agentforce helped you create. Generate summaries of varying lengths to understand what your flows are about and what they do. Agentforce summarizes flows in as much detail as you need. Add the flow summary to the flow description, so anyone can understand how the flow works.
Working with the Triggering Record in Record-Triggered Flows: When a record triggers your flow to run, Salesforce automatically stores that record's information in the triggering record variable. This variable gives your flow instant access to all the field values from the record that triggered the flow. You can read the field values, check them, and change them.
Choosing Which Choice Resource to Use in Screen Components: Choice resources display selectable options in flow screens. Choice resources can appear as radio buttons, checkboxes, or picklist fields. There are several options for choice resources that you can use, depending on your business need. We recommend using a choice resource only when you can’t use a record choice set or a picklist choice set.
Build Flows with AI: Describe the automation that you want, and let AI draft a flow for you. Select the tool that fits where you work and what you want to do.
How Entry Conditions Work in Record-Triggered Flows: Entry conditions control when record-triggered flows run. Use AND, OR, custom logic, or formula-based conditions in the Start element to run your flow only when the relevant records change.
Audience Flows: An audience flow runs on a schedule and sends messages to a specified audience. Select a data source—segment, list, record, or campaign—when you create the flow.
Designing an External System Integration: To connect any flow to an external system without coding, use MuleSoft for Flow: Integration connectors in the flow. When no connector exists, you can use the HTTP Callout action to make direct API calls to external systems without coding. Run your flow when external system changes occur by selecting the External System Change-Triggered flow type. For legacy systems without APIs, you can use MuleSoft RPA processes published on Anypoint Platform as external services in your flow. For documents and unstructured data, use MuleSoft for Flow: IDP to extract information from PDFs, images, and forms.
Extracting Data from Digital and Scanned Documents: Extract structured data from invoices, purchase orders, forms, and other unstructured or semi-structured documents using AI-powered analysis in Flow. Automate data entry and processing workflows by converting document content into structured information that can be used in your business processes. Use human review workflows to validate extracted data and ensure accuracy for critical business decisions.
Example Document Processing Workflows: Walk through end-to-end examples that combine document extraction with human review, from a single flow path to record-triggered flows with approval and orchestration.
Automation Event-Triggered Flows: Create event-triggered flows that automatically respond to business events, such as customer orders, SMS signups, or service level changes. Choose from provided triggers, define custom triggers using Data 360, real-time data graphs, or create triggers with engagement signals.
Segment Flows: A segment flow sends messages to people in a segment at a scheduled time. When you activate the flow, it sends messages to everyone in the segment at that time.
Understand MuleSoft for Flow: Integration Features: Optimize and scale your business processes by using pre-built templates, automated versioning, and advanced trigger logic to manage MuleSoft for Flow: Integration flows.
Considerations for Screen Component Styling: Before you change the width and vertical alignment of screen components, be mindful that the style settings aren't responsive to screen size. Also understand how to lay out components of different heights and when to use sections and blank Display Text components.
Log Flow Data Persistently to Data 360: Log flow run metrics persistently to Data 360, ensuring reliable and scalable data management. Set up persistent logging for record-triggered, platform event-triggered, schedule-triggered flows, and autolaunched flows.
Designing Flows: After you know the business problem you’re trying to solve with task automation, have identified the functional requirements for the flow, and have a distribution plan, it’s time to design the solution so it can be built using Flow Builder.
Start a Flow with a Button: There are different ways to start a flow from a button. The type of button determines the type of flow you can start, where users can see the button, what variable values you can send into the flow.
Add a Flow Link to a Record Page: Add a custom link to a record page that starts an active screen flow or autolaunched flow. Use the flow's web address (URL) to set up the link.
Run a Flow from a Custom List View Button: Add a custom button to a list view that starts an active autolaunched flow or screen flow. Send the IDs of the selected list view records to the flow. Use the flow's web address (URL) to set up the button.
Run a Flow from a Custom Record Page Button: Add a custom button to a record page that starts an active autolaunched flow or screen flow. Send any variable value to the flow. Use the flow's web address (URL) to set up the button.
Embed a Screen Flow in a Navigation Tab in Your Org: Add an active screen flow to a navigation tab in your org, using the flow's web address (URL). Users can open the tab and then run the screen flow from there.
Element Error Rate in Flows: Several types of flows automate tasks in the background. As a result, if an error occurs, it can be some time before you notice that anything is wrong with your business process. See which flows need attention at a glance with the Element Error Rate field. This field shows a green success icon for healthy flows and a yellow warning icon for unhealthy flows. Learn how Salesforce calculates the error rate and which metrics it uses in the calculation.
Get Started with Flows: Plan your automation carefully to ensure a successful solution. Whether building traditional flows or using AI agents, define clear goals and specific instructions before you start. Identify business challenges and their root causes to determine which automation approach best solves your process issues.
Automate a Course Management Process Project: Use this project if your business delivers something that requires people to sign up for it, like courses, programs, seminars, trainings, or services. This flow project walks you through automating a course management system. It demonstrates how to create objects to hold custom data and build record-triggered and screen flows.
Create an After-Save Record-Triggered Flow for Changed Course Attendees: Create a record-triggered flow that runs if the Attendee Status field of a course attendee record is updated to Canceled. If the class has a waitlist, change the status of the first course attendee on the waitlist to be enrolled. Send notifications to the canceled and enrolled course attendees.
Create an After-Save Record-Triggered Flow for Course Attendee: Create a record-triggered flow that runs after a new course attendee record is saved. If the course delivery is now full, set the course delivery status to full and email the instructor. Send an email notification to the new course attendee.
Create a Before-Save Flow for Better Data Quality: Create a before-save record-triggered flow that validates data quality and enforces business rules before course attendee records are created. No matter how a course attendee is created, this flow prevents duplicate enrollments, validates course capacity, and ensures data integrity by blocking invalid records and setting appropriate statuses based on business logic.
Create After-Save Record-Triggered Flows: Build flows that run after course attendee records are saved. These flows handle notifications, update related records, and manage business processes that depend on successful record creation or updates.
Create Your Data Model: Build the foundation of your course management system by creating custom objects to store course information, course deliveries, and course attendees. A well-designed data model ensures your automations have the right data structure to work with.
Create a Button to Launch the Screen Flow: Create an action button on the account object. Reps click the button on an account record page to start the screen flow and register an attendee from that account for a course.
Create a Screen Flow to Register Course Attendees: Streamline a registration process with a screen flow. Reps can use the screen flow to make sure they get all relevant information about a course attendee and the course delivery to sign the attendee up for.
Flow Builder Examples Library: Browse Flow Builder examples organized by common jobs to be done. Each example includes a link to the full topic and a short description. Some examples appear in more than one category, but are only listed once per category.
Jump Start Your Org with Flow Projects: Create custom data models and build flows that work together to streamline complex business processes and optionally adapt the project for your business need.
Get Started with MuleSoft for Flow: Integration: Use MuleSoft for Flow: Integration to create automated connections between systems, so you can keep data up-to-date, reduce manual work, and respond faster to business events.
Compare Flow Versions to Track Changes: Quickly identify differences between any two flow versions of the same flow directly from Flow Builder or the Automation app. You can catch issues when modifying complex flows, review changes more efficiently, and maintain a clear view of changes. You can compare versions of autolaunched flows, screen flows, scheduled-triggered flows, platform event-triggered flows, and record-triggered flows. To review saves within the same flow version, use Flow Edit History instead.
View On-Canvas Element Run Data: View aggregated element run data for active and previously run flows directly on the canvas. Apply a date range filter to show metrics for a specified time period. Access more detailed performance metrics on the element’s Analytics tab and in the element record’s Analytics tab. Embedded analytics aren’t available for screen flows or orchestrations.
Screen Flows Report: See who’s running the screen flows that you build. From the Reports tab, use the Sample Flow Report: Screen Flow to discover flow interview execution counts and screen duration times and to review the status of a flow interview.
Sync Quote to Opportunity: This action syncs quote line items to opportunity line items. This action is available in flow running API version 68.0 and later
Confirm Sales Meeting Action: Confirms a selected meeting time from a list of available time slots. Inbox is required to use this action. This action is available in flows running API version 66.0 and later.
Extract Data from Document Action: Extract structured data from documents using AI-powered analysis, with optional human review before the flow continues.
Get AI-Generated Recommendations Action: Get AI-generated recommendations based on the provided context, and then save the recommendations as AI-generated action items. This action is used in the Get AI Recommendations from Call Transcripts flow as part of Agentforce Pipeline Management.
Get Available Meeting Times Action: Retrieves available meeting times for a specified lead, contact, or person account based on the record owner’s schedule. Inbox is required to use this action. This action is available in flows running API version 66.0 and later.
Get Content Note Action: Get the most recent content note data for a specified record. This action is available in flows running API version 64.0 and later.
Get or Execute Field Update Suggestion Action: Enqueue requests to get a field update suggestion from a field generation prompt template, or update a field based on a generated suggestion if the agent is configured to make updates autonomously. This action is used in the Process Field Update Suggestions flow as part of Agentforce Pipeline Management.
Get Opportunity Content Note Action: Get the most recent content note data for the specified opportunity record. This action is used in the Get Opportunity Grounding Data flow as part of Agentforce Pipeline Management.
Get Opportunity Stage Details Action: Get the names and descriptions of the stages associated with the specified opportunity record. This action is used in the Get Opportunity Grounding Data flow as part of Agentforce Pipeline Management.
Get Related Emails Action: Get a list of emails that are related to a specific record and that were logged within a specified date range. This action is available in flows running API version 66.0 and later.
Einstein RAG Flow Core Actions: Improve large language model (LLM) responses in flows with actions related to Einstein retrieval augmented generation (RAG).
Transform Query for Case Action: This action generates a natural language query for retrieval based on the case details, language, and additional context.
Transform Query for Conversation Action: This action generates a natural language query for retrieval based on the conversation text, language, and additional context.
Transform Query for Email Action: This action generates a natural language query for retrieval based on the email details, language, and additional context. This action is available in flows running API version 62.0 and later.
Request an Approval Action: Run an active, autolaunched flow approval process with the specified inputs asynchronously. This action doesn’t submit a record for approvals that use Classic Approval Processes.
Kanban Board Screen Input Component (Beta): Use the new Kanban Board component to show records as cards in columns that represent workflow stages, without custom Lightning implementations. Your users gain instant visibility into record progress and record details without leaving the flow. The Kanban Board is read-only, so users can’t drag cards between stages at run time.
Real-Time Data Graph Record Change Automation Event: Run the automation event-triggered flow when a real-time data graph data model object (DMO) or calculated insight object (CIO) is changed and meets the specified conditions.
Automation Event Library: The Automation Event Library in Flow Builder lists events you can select to trigger event-triggered flows or Wait Until Event elements.
Document Processing Limits and Quotas: Limits for document processing in flows align with Data 360 where applicable. Prompt limits and other document processing-specific quotas are documented in the MuleSoft document processing documentation.
MuleSoft for Flow: Intelligent Document Processing Actions: Use MuleSoft for Flow actions to extract structured data from documents using AI-powered intelligent document processing. These actions integrate MuleSoft's intelligent document processing capabilities into your flows, enabling automated extraction and processing of data from invoices, purchase orders, forms, and other business documents.
15Five Connector: Connect to an external 15Five account. Perform tasks like creating high fives, editing users, and retrieving check-ins. Use 15Five as a data target (action).
Ably Control API Connector (Beta): Connect to an external Ably Control API account. Perform tasks like managing apps or configuring queues. Use Ably Control API as a data target (action).
Ably Platform Connector (Beta): Connect to an external Ably Platform account. Perform tasks like publishing messages or managing push devices. Use Ably Platform as a data target (action).
Abstract Company Enrichment Connector: Connect to an external Abstract API account. Perform tasks like validating company details from a domain. Use Abstract Company Enrichment as a data target (action).
Abstract Email Validator Connector: Connect to an external Abstract API account. Perform tasks like validating email addresses. Use Abstract Email Validator as a data target (action).
Abstract Phone Validator Connector: Connect to an external Abstract API account. Perform tasks like validating phone numbers. Use Abstract Phone Validator as a data target (action).
Acronis Cyber Protect Connector: Connect to an external Acronis Cyber Protect account. Perform tasks like managing agent updates or creating tenants. Use Acronis Cyber Protect as a data target (action).
ActiveCampaign Connector: Connect to an external ActiveCampaign account. Perform tasks like managing marketing and sales automation. Use ActiveCampaign as a data target (action).
ActivityInfo Connector (Beta): Connect to an external ActivityInfo account. Perform tasks like adding database users or retrieving databases. Use ActivityInfo as a data target (action).
Adobe Analytics Connector: Connect to an external Adobe Analytics account. Perform tasks like managing calculated metrics or retrieving dimensions. Use Adobe Analytics as a data target (action).
Adobe Experience Platform Connector: Connect to an external Adobe Experience Platform account. Perform tasks like creating audiences or managing custom labels. Use Adobe Experience Platform as a data target (action).
Adobe Marketo Engage Connector: Connect to an external Adobe Marketo Engage account. Perform tasks like syncing leads and activating smart campaigns. Use Adobe Marketo Engage as a data target (action).
Adobe Sign Connector: Connect to an external Adobe Sign account. Perform tasks like creating, sharing, or retrieving agreements. Use Adobe Sign as a data target (action).
Adobe Target Admin Connector: Connect to an external Adobe Target Admin account. Perform tasks like managing A/B and Experience Targeting activities, audiences, and content offers. Use Adobe Target Admin as a data target (action).
Adobe Target Profile Connector: Connect to an external Adobe Target Profile account. Perform tasks like retrieving profiles or updating profile attributes. Use Adobe Target Profile as a data target (action).
Agilite Connector (Beta): Connect to an external Agilite account. Perform tasks like running BPM workflows or retrieving keyword data. Use Agilite as a data target (action).
Aha Connector: Connect to an external Aha account. Perform tasks like managing features and releases, and handling users and roles. Use Aha as a data target (action).
Aircall Connector: Connect to an external Aircall account. Perform tasks like managing users, teams, and contacts. Use Aircall as a data target (action).
Airtable Connector: Connect to an external Airtable account. Perform tasks like managing records and comments. Use Airtable as a data target (action).
AlertOps Connector: Connect to an external AlertOps account. Perform tasks like managing workflows, retrieving alerts, or accessing maintenance windows. Use AlertOps as a data target (action).
Alfresco Connector: Connect to an external Alfresco account. Perform tasks like creating persons and groups, adding persons to groups, deleting groups, and listing person preferences. Use Alfresco as a data target (action).
Ansible Connector: Connect to an external Ansible account. Perform tasks like running ad-hoc commands, managing job templates, scheduling workflows, and tracking execution results. Use Ansible as a data target (action).
Anthropic Connector: Connect to an external Anthropic account. Perform tasks like creating messages. Use Anthropic as a data target (action).
Asana Connector: Connect to an external Asana account. Perform tasks like creating projects or updating tasks. Use Asana as a data source (trigger) or a data target (action).
AssemblyAI Connector (Beta): Connect to an external AssemblyAI account. Perform tasks like retrieving subtitles or listing transcripts. Use AssemblyAI as a data target (action).
Aternity Connector: Connect to an external Aternity account. Perform tasks like retrieving endpoint metrics, device inventory, or user experience data. Use Aternity as a data target (action).
Attio Connector (Beta): Connect to an external Attio account. Perform tasks like getting objects or listing workspace members. Use Attio as a data target (action).
Auth0 Connector: Connect to an external Auth0 account. Perform tasks like creating users and managing user roles. Use Auth0 as a data target (action).
Automox Connector: Connect to an external Automox account. Perform tasks like creating policies or listing devices. Use Automox as a data source (trigger) or a data target (action).
BambooHR Connector: Connect to an external BambooHR account. Perform tasks like retrieving employee records and managing employee goals. Use BambooHR as a data target (action).
Beauhurst Connector: Connect to an external Beauhurst account. Perform tasks like retrieving company data, searching companies, and accessing transaction data. Use Beauhurst as a data target (action).
BeyondTrust Connector: Connect to an external BeyondTrust account. Perform tasks like retrieving jump client installers, groups, policies, and users. Use BeyondTrust as a data target (action).
Bird Connector: Connect to an external Bird (formerly MessageBird) account. Perform tasks like sending messages or listing channels. Use Bird as a data target (action).
Bitbucket Connector: Connect to an external Bitbucket account. Perform tasks like retrieving a commit or listing repositories. Use Bitbucket as a data target (action).
Bitwarden Connector: Connect to an external Bitwarden account. Perform tasks like managing members and security policies, or updating collections. Use Bitwarden as a data target (action).
Bloomfire Connector: Connect to an external Bloomfire account. Perform tasks like creating users and managing questions and answers. Use Bloomfire as a data target (action).
BoldSign Connector (Beta): Connect to an external BoldSign account. Perform tasks like managing documents or getting embedded sign links. Use BoldSign as a data target (action).
Bonusly Connector: Connect to an external Bonusly account. Perform tasks like creating, updating, or deleting users, granting or revoking bonuses, and retrieving achievements. Use Bonusly as a data target (action).
Box Connector: Connect to an external Box account. Perform tasks like creating folders, copying files, or retrieving file and metadata information. Use Box as a data target (action).
Brevo Connector (Beta): Connect to an external Brevo account. Perform tasks like creating contacts or managing account information. Use Brevo as a data target (action).
Buddy Connector: Connect to an external Buddy account. Perform tasks like managing pipelines or administering environments. Use Buddy as a data target (action).
BugSnag Connector: Connect to an external BugSnag account. Perform tasks like managing projects, collaborators, and error events. Use BugSnag as a data target (action).
Calendly Connector: Connect to an external Calendly account. Perform tasks like creating event links and retrieving invitees. Use Calendly as a data target (action).
Canvas Connector: Connect to an external Canvas account. Perform tasks like managing courses or enrolling users. Use Canvas as a data target (action).
Celigo Connector: Connect to an external Celigo account. Perform tasks like managing users and automation flows. Use Celigo as a data target (action).
Celonis Connector: Connect to an external Celonis account. Perform tasks like creating users, searching groups, or updating user records. Use Celonis as a data target (action).
Chargebee Connector (Beta): Connect to an external Chargebee account. Perform tasks like managing subscriptions or processing invoices. Use Chargebee as a data target (action).
CircleCI Connector: Connect to an external CircleCI account. Perform tasks like creating and managing projects, triggering pipelines, or approving jobs. Use CircleCI as a data target (action).
Cisco Defense Orchestrator Connector: Connect to an external Cisco Defense Orchestrator account. Perform tasks like retrieving devices or device managers. Use Cisco Defense Orchestrator as a data target (action).
Cisco Meraki Connector: Connect to an external Cisco Meraki account. Perform tasks like retrieving organization details, network event logs, and client information. Use Cisco Meraki as a data target (action).
Cisco Secure Firewall Management Center Connector: Connect to an external Cisco Secure Firewall Management Center (FMC) account. Perform tasks like creating new access rules or managing network object definitions. Use Cisco Secure Firewall Management Center as a data target (action).
ClickUp Connector: Connect to an external ClickUp account. Perform tasks like creating tasks and updating their comments. Use ClickUp as a data target (action).
Clockify Connector: Connect to an external Clockify account. Perform tasks like managing time entries and workspaces. Use Clockify as a data target (action).
CockroachDB Connector: Connect to an external CockroachDB account. Perform tasks like managing users, clusters, and databases, or retrieving organization information. Use CockroachDB as a data target (action).
Coda Connector (Beta): Connect to an external Coda account. Perform tasks like retrieving documents or managing pages. Use Coda as a data target (action).
Cognito Forms Connector (Beta): Connect to an external Cognito Forms account. Perform tasks like retrieving forms. Use Cognito Forms as a data target (action).
Community Connector: Connect to an external Community account. Perform tasks like creating, updating, and deleting subcommunities, or sending direct messages. Use Community as a data target (action).
Confluence Cloud Connector: Connect to an external Confluence Cloud account. Perform tasks like managing pages, attachments, or inline comments. Use Confluence Cloud as a data target (action).
MuleSoft for Flow: Integration Connectors: Use MuleSoft for Flow: Integration connectors in your flows for no-code connectivity to external systems. Each external system that connects to Flow Builder behaves in different ways depending on how the external system stores the information that you want to retrieve and manipulate. Review each connector's reference page to understand which triggers and actions are available.
Copper Connector (Beta): Connect to an external Copper account. Perform tasks like searching leads or retrieving accounts. Use Copper as a data target (action).
Couchbase Capella Connector: Connect to an external Couchbase Capella account. Perform tasks like managing users or accessing cluster and project details. Use Couchbase Capella as a data target (action).
Coupa Connector: Connect to an external Coupa account. Perform tasks like managing users or items. Use Coupa as a data target (action).
Courier Connector: Connect to an external Courier account. Perform tasks like sending messages or retrieving subscribers. Use Courier as a data target (action).
CrowdStrike Connector: Connect to an external CrowdStrike account. Perform tasks like fetching host data, reports, or prevention policies. Use CrowdStrike as a data target (action).
Dashlane Connector: Connect to an external Dashlane account. Perform tasks like retrieving team members' information, accessing password health data, and listing active user devices. Use Dashlane as a data target (action).
Datadog Connector: Connect to an external Datadog account. Perform tasks like managing user accounts or assigning roles. Use Datadog as a data target (action).
Delighted Connector (Beta): Connect to an external Delighted account. Perform tasks like creating people or retrieving people. Use Delighted as a data target (action).
Deputy Connector: Connect to an external Deputy account. Perform tasks like starting, pausing, and stopping timesheets, or creating and updating leave requests. Use Deputy as a data target (action).
Derdack SIGNL4 Connector: Connect to an external Derdack SIGNL4 account. Perform tasks like triggering alerts, managing alert timelines, or listing all users. Use Derdack SIGNL4 as a data target (action).
DHL Tracking Connector: Connect to an external DHL Tracking account. Perform tasks like getting tracking information. Use DHL Tracking as a data target (action).
Discord Connector: Connect to an external Discord account. Perform tasks like creating channels or messaging users. Use Discord as a data target (action).
Discourse Connector (Beta): Connect to an external Discourse account. Perform tasks like creating posts or managing users. Use Discourse as a data target (action).
DocSpring Form Connector (Beta): Connect to an external DocSpring Form account. Perform tasks like generating PDFs or managing form templates. Use DocSpring Form as a data target (action).
Document360 Connector: Connect to an external Document360 account. Perform tasks like retrieving knowledge base articles, accessing project workflows, or listing team accounts. Use Document360 as a data target (action).
Dovetail Connector: Connect to an external Dovetail account. Perform tasks like searching for information, and retrieving project lists, files, and associated data. Use Dovetail as a data target (action).
Drata Connector: Connect to an external Drata account. Perform tasks like deactivating employee access or getting team compliance status. Use Drata as a data target (action).
Dropbox Sign Connector: Connect to an external Dropbox Sign account. Perform tasks like getting a signature request and sending a request reminder. Use Dropbox Sign as a data target (action).
Dynatrace Connector: Connect to an external Dynatrace account. Perform tasks like creating, retrieving, updating, or deleting credentials for monitoring services. Use Dynatrace as a data target (action).
Elastic Email Connector (Beta): Connect to an external Elastic Email account. Perform tasks like creating campaigns or sending emails. Use Elastic Email as a data target (action).
Elasticsearch Connector: Connect to an external Elasticsearch account. Perform tasks like retrieving index and count information, listing inference endpoints, checking licenses, or running multiple searches. Use Elasticsearch as a data target (action).
Envoy Connector: Connect to an external Envoy account. Perform tasks like accessing location information, managing invites, or retrieving reservations. Use Envoy as a data target (action).
Eventbrite Connector: Connect to an external Eventbrite account. Perform tasks like creating events and retrieving attendees. Use Eventbrite as a data target (action).
Everhour Connector (Beta): Connect to an external Everhour account. Perform tasks like creating time entries or retrieving current users. Use Everhour as a data target (action).
Figma Connector: Connect to an external Figma account. Perform tasks like retrieving image files, managing comments, or listing team projects. Use Figma as a data target (action).
Files.com Connector (Beta): Connect to an external Files.com account. Perform tasks like managing users or listing folders. Use Files.com as a data target (action).
Fivetran Connector (Beta): Connect to an external Fivetran account. Perform tasks like creating connections or listing groups. Use Fivetran as a data target (action).
Flotiq Connector (Beta): Connect to an external Flotiq account. Perform tasks like managing content or searching data. Use Flotiq as a data target (action).
Freshchat Connector (Beta): Connect to an external Freshchat account. Perform tasks like retrieving user conversations or listing users. Use Freshchat as a data target (action).
Freshdesk Connector: Connect to an external Freshdesk account. Perform tasks like managing tickets, contacts, agents, and groups. Use Freshdesk as a data source (trigger) or a data target (action).
Freshsales Connector (Beta): Connect to an external Freshsales account. Perform tasks like creating contacts or retrieving deals. Use Freshsales as a data target (action).
Freshservice Connector: Connect to an external Freshservice account. Perform tasks like creating tickets or retrieving agents. Use Freshservice as a data target (action).
Front Connector: Connect to an external Front account. Perform tasks like sending messages, and managing contacts, inbox access, and team members. Use Front as a data target (action).
Fullstory Connector (Beta): Connect to an external Fullstory account. Perform tasks like creating events or managing users. Use Fullstory as a data target (action).
Gainsight PX Connector: Connect to an external Gainsight PX account. Perform tasks like managing users and accounts, tracking custom events, and monitoring engagement. Use Gainsight PX as a data target (action).
Genesys Cloud Connector: Connect to an external Genesys Cloud account. Perform tasks like managing user accounts, membership, and roles. Use Genesys Cloud as a data target (action).
GitLab Connector: Connect to an external GitLab account. Perform tasks like creating projects, managing repository branches, or adding project and group members. Use GitLab as a data target (action).
Google BigQuery Connector: Connect to an external Google BigQuery account. Perform tasks like retrieving and cancelling jobs. Use Google BigQuery as a data target (action).
Google Calendar Connector: Connect to an external Google Calendar account. Perform tasks like syncing contacts or sending transactional messages. Use Google Calendar as a data source (trigger) or a data target (action).
Google Chat Connector: Connect to an external Google Chat account. Perform tasks like creating spaces, adding or removing members, or posting and deleting messages. Use Google Chat as a data target (action).
Google Drive Connector: Connect to an external Google Drive account. Perform tasks like managing files, drives, permissions, and comments, or listing revisions. Use Google Drive as a data target (action).
Google Gemini Connector: Connect to an external Google Gemini account. Perform tasks like generating content. Use Google Gemini as a data target (action).
Google Meet Connector: Connect to an external Google Meet account. Perform tasks like looking up conferences, participants, recordings, and transcripts, or creating and updating meeting spaces. Use Google Meet as a data target (action).
Google Sheets Connector: Connect to an external Google Sheets account. Perform tasks like creating or retrieving rows. Use Google Sheets as a data target (action).
Grafana Connector: Connect to an external Grafana account. Perform tasks like retrieving alert rules, dashboards, teams, and notification channels. Use Grafana as a data target (action).
Guru Connector: Connect to an external Guru account. Perform tasks like creating cards or managing group members. Use Guru as a data target (action).
HappyFox Chat Connector (Beta): Connect to an external HappyFox Chat account. Perform tasks like retrieving transcripts or managing departments. Use HappyFox Chat as a data target (action).
Harness Connector: Connect to an external Harness account. Perform tasks like managing environments or creating projects. Use Harness as a data target (action).
Harvest Connector (Beta): Connect to an external Harvest account. Perform tasks like creating users or updating projects. Use Harvest as a data target (action).
HashiCorp Terraform Connector: Connect to an external HashiCorp Terraform account. Perform tasks like listing organizations, managing projects, or administering workspaces. Use HashiCorp Terraform as a data target (action).
Help Scout Connector (Beta): Connect to an external Help Scout account. Perform tasks like retrieving conversations or updating customers. Use Help Scout as a data target (action).
HiBob Connector: Connect to an external HiBob account. Perform tasks like managing employee data, tracking time-off, and handling onboarding processes. Use HiBob as a data target (action).
Highspot Connector: Connect to an external Highspot account. Perform tasks like managing users, spots, or content lists. Use Highspot as a data target (action).
HubSpot Connector: Connect to an external HubSpot account. Perform tasks like syncing deals or creating marketing events. Use HubSpot as a data source (trigger) or a data target (action).
Infoblox Connector: Connect to an external Infoblox account. Perform tasks like managing DNS records or administering networks and views. Use Infoblox as a data target (action).
Instana Connector: Connect to an external Instana account. Perform tasks like retrieving events, applications, or services. Use Instana as a data target (action).
Instapage Connector (Beta): Connect to an external Instapage (airSlate) account. Perform tasks like managing pages or publishing landing pages. Use Instapage as a data target (action).
Intercom Connector: Connect to an external Intercom account. Perform tasks like syncing contacts or creating tickets. Use Intercom as a data target (action).
Iterable Connector: Connect to an external Iterable account. Perform tasks like creating catalogs or deleting users. Use Iterable as a data target (action).
Jamf Pro Connector: Connect to an external Jamf Pro account. Perform tasks like retrieving configuration and usage information for managed computers and mobile devices. Use Jamf Pro as a data source (trigger) or a data target (action).
JFrog Artifactory Connector: Connect to an external JFrog Artifactory account. Perform tasks like administering users, managing user roles, or controlling project membership. Use JFrog Artifactory as a data target (action).
Jira Connector: Connect to an external Jira account. Perform tasks like creating issues or updating comments. Use Jira as a data source (trigger) or a data target (action).
Jira OAuth (Authorization Code Flow) Connector: Connect to an external Jira account that uses an Authorization Code Flow connection. Perform tasks like creating issues or updating comments. Use Jira OAuth as a data source (trigger) or a data target (action).
JumpCloud Connector: Connect to an external JumpCloud account. Perform tasks like managing users, user groups, system groups, and authentication settings. Use JumpCloud as a data target (action).
Jumpseller Connector (Beta): Connect to an external Jumpseller account. Perform tasks like listing products or managing store data. Use Jumpseller as a data target (action).
JustCall Connector: Connect to an external JustCall account. Perform tasks like sending messages and managing calls and contact records. Use JustCall as a data target (action).
Kaseya VSA Connector: Connect to an external Kaseya VSA account. Perform tasks like retrieving device inventory, asset information, environment specifications, and antivirus status. Use Kaseya VSA as a data target (action).
Kong Gateway Connector: Connect to an external Kong Gateway account. Perform tasks like managing consumers, services, or routes. Use Kong Gateway as a data target (action).
Logz.io Connector (Beta): Connect to an external Logz.io account. Perform tasks like creating alerts or searching logs. Use Logz.io as a data target (action).
Looker Connector: Connect to an external Looker account. Perform tasks like creating and managing users, adding them to groups, setting roles, and creating new groups. Use Looker as a data target (action).
Mailchimp Connector: Connect to an external Mailchimp account. Perform tasks like managing campaigns, lists, automations, and subscriber data. Use Mailchimp as a data target (action).
MailerLite Connector: Connect to an external MailerLite account. Perform tasks like managing subscribers, creating and deleting groups, and managing subscriber group membership. Use MailerLite as a data target (action).
Mailgun Connector (Beta): Connect to an external Mailgun account. Perform tasks like managing email queues or retrieving stored emails. Use Mailgun as a data target (action).
Mailjet Connector (Beta): Connect to an external Mailjet account. Perform tasks like retrieving profiles or sending emails. Use Mailjet as a data target (action).
Maxio Connector (Chargify): Connect to an external Maxio account. Perform tasks like syncing customers and creating subscriptions. Use Maxio as a data target (action).
Mezmo Connector (Beta): Connect to an external Mezmo account. Perform tasks like listing organizations or retrieving usage data. Use Mezmo as a data target (action).
Microsoft Azure Connector: Connect to an external Microsoft Azure account. Perform tasks like managing virtual machines, networks, and subnets, or controlling network interfaces. Use Microsoft Azure as a data target (action).
Microsoft Dynamics 365 Business Central Connector: Connect to an external Microsoft Dynamics 365 Business Central account. Perform tasks like managing sales orders, items, and other business resources. Use Microsoft Dynamics 365 Business Central as a data source (trigger) or a data target (action).
Microsoft Entra ID Connector: Connect to an external Microsoft Entra ID account. Perform tasks like managing groups and their memberships. Use Microsoft Entra ID as a data target (action).
Microsoft Excel Connector: Connect to an external Microsoft Excel account. Perform tasks like adding or retrieving rows. Use Microsoft Excel as a data source (trigger) or a data target (action).
Microsoft Exchange Online Connector: Connect to an external Microsoft Exchange Online account. Perform tasks like managing subscriptions, mail folders, and messages. Use Microsoft Exchange Online as a data target (action).
Microsoft Intune Connector: Connect to an external Microsoft Intune account. Perform tasks like managing users, devices, and applications. Use Microsoft Intune as a data target (action).
Microsoft OneDrive Connector: Connect to an external Microsoft OneDrive account. Perform tasks like managing files and folders. Use Microsoft OneDrive as a data target (action).
Microsoft Outlook Connector: Connect to an external Microsoft Outlook account. Perform tasks like sending messages or creating events. Use Microsoft Outlook as a data source (trigger) or a data target (action).
Microsoft Power BI Connector: Connect to an external Microsoft Power BI account. Perform tasks like operating on datasets. Use Microsoft Power BI as a data target (action).
Microsoft SharePoint Connector: Connect to an external Microsoft SharePoint account. Perform tasks like searching documents, listing sites, or moving items. Use Microsoft SharePoint as a data target (action).
Microsoft Teams Connector: Connect to an external Microsoft Teams account. Perform tasks like creating a channel or adding a member to a team. Use Microsoft Teams as a data target (action).
Mimecast Connector: Connect to an external Mimecast account. Perform tasks like managing users, groups, or group memberships. Use Mimecast as a data target (action).
Miro Connector: Connect to an external Miro account. Perform tasks like creating, updating, and deleting boards, teams, and widget cards. Use Miro as a data target (action).
Mitto Connector (Chat): Connect to an external Mitto account. Perform tasks like sending chats. Use Mitto as a data target (action).
Mitto Connector (SMS): Connect to an external Mitto account. Perform tasks like sending SMS messages. Use Mitto as a data target (action).
Mixpanel Connector (Beta): Connect to an external Mixpanel account. Perform tasks like querying events or listing cohorts. Use Mixpanel as a data target (action).
Monday.com Connector: Connect to an external Monday.com account. Perform tasks like creating and managing workspaces, boards, groups, and items, and adding users to teams. Use Monday.com as a data target (action).
Moosend Connector: Connect to an external Moosend account. Perform tasks like adding subscribers or sending campaigns. Use Moosend as a data target (action).
Neon Connector: Connect to an external Neon account. Perform tasks like managing projects or snapshots. Use Neon as a data target (action).
NetBox Connector (Beta): Connect to an external NetBox account. Perform tasks like listing, creating, updating, or deleting circuits and circuit types. Use NetBox as a data target (action).
NetLicensing Connector (Beta): Connect to an external NetLicensing account. Perform tasks like managing licenses or validating licensees. Use NetLicensing as a data target (action).
NetSuite Connector: Connect to an external NetSuite account. Perform tasks like syncing contacts or creating invoices. Use NetSuite as a data source (trigger) or a data target (action).
Neutrino Connector (Beta): Connect to an external Neutrino account. Perform tasks like validating emails or verifying phone numbers. Use Neutrino as a data target (action).
New Relic Connector: Connect to an external New Relic account. Perform tasks like retrieving application information, host details, and active alert policies. Use New Relic as a data target (action).
Nintex Workflow Cloud Connector: Connect to an external Nintex Workflow Cloud account. Perform tasks like managing users in tenants or administering workflow instances. Use Nintex Workflow Cloud as a data target (action).
Notion Connector: Connect to an external Notion account. Perform tasks like creating comments or listing users. Use Notion as a data target (action).
Nutshell Connector (Beta): Connect to an external Nutshell account. Perform tasks like managing accounts or deleting contacts. Use Nutshell as a data target (action).
Octopus Deploy Connector: Connect to an external Octopus Deploy account. Perform tasks like creating releases, retrieving an environment, or fetching a deployment status. Use Octopus Deploy as a data target (action).
Okta Connector: Connect to an external Okta account. Perform tasks like managing users, groups, applications, and authentication factors. Use Okta as a data target (action).
OneLogin Connector: Connect to an external OneLogin account. Perform tasks like creating and managing users, assigning roles and groups, updating account status, and handling authentication settings. Use OneLogin as a data target (action).
OnePageCRM Connector (Beta): Connect to an external OnePageCRM account. Perform tasks like creating contacts or managing deals. Use OnePageCRM as a data target (action).
Open Science Framework (OSF) Connector (Beta): Connect to an external Open Science Framework (OSF) account. Perform tasks like managing nodes or listing registrations. Use Open Science Framework (OSF) as a data target (action).
OpenAI Connector: Connect to an external OpenAI account. Perform tasks like completing chats and running threads.
OpenWeatherMap Connector: Connect to an external OpenWeatherMap account. Perform tasks like calling the current weather or obtaining weather overviews. Use OpenWeatherMap as a data target (action).
OutSystems Connector: Connect to an external OutSystems account. Perform tasks like managing user accounts or administering organizational roles. Use OutSystems as a data target (action).
Pabbly Connector (Beta): Connect to an external Pabbly account. Perform tasks like managing subscriber lists or importing subscribers. Use Pabbly as a data target (action).
PagerDuty Connector: Connect to an external PagerDuty account. Perform tasks like creating incidents or managing escalations. Use PagerDuty as a data target (action).
PandaDoc Connector: Connect to an external PandaDoc account. Perform tasks like sending documents or creating templates. Use PandaDoc as a data target (action).
Paperform Connector (Beta): Connect to an external Paperform account. Perform tasks like retrieving forms or getting form fields. Use Paperform as a data target (action).
Papertrail Connector (Beta): Connect to an external Papertrail account. Perform tasks like searching logs or listing log archives. Use Papertrail as a data target (action).
Paychex Connector: Connect to an external Paychex account. Perform tasks like getting companies, workers, checks, and pay rates, and updating or deleting worker pay details. Use Paychex as a data target (action).
PayPal Connector: Connect to an external PayPal account. Perform tasks like creating subscriptions or syncing catalog products. Use PayPal as a data target (action).
PDF.co Connector (Beta): Connect to an external PDF.co account. Perform tasks like converting documents or parsing PDFs. Use PDF.co as a data target (action).
Personio Connector: Connect to an external Personio account. Perform tasks like administering employee records and managing absence periods. Use Personio as a data target (action).
Ping Identity Connector: Connect to an external Ping Identity account. Perform tasks like creating and managing users, updating passwords, unlocking accounts, and resetting MFA. Use Ping Identity as a data target (action).
Pingdom Connector (Beta): Connect to an external Pingdom account. Perform tasks like creating checks or retrieving credits. Use Pingdom as a data target (action).
Pinterest Connector: Connect to an external Pinterest account. Perform tasks like creating pins or listing boards. Use Pinterest as a data target (action).
Pipedrive Connector: Connect to an external Pipedrive account. Perform tasks like creating and managing projects, tasks, and users. Use Pipedrive as a data target (action).
Plaid Connector: Connect to an external Plaid account. Perform tasks like accessing financial data in accounts, transactions, identity, and more. Use Plaid as a data target (action).
Planview AgilePlace Connector: Connect to an external Planview AgilePlace account. Perform tasks like updating a user or deleting a board. Use Planview AgilePlace as a data target (action).
Planview ProjectPlace Connector: Connect to an external Planview ProjectPlace account. Perform tasks like inviting a member or getting archived boards. Use Planview ProjectPlace as a data target (action).
Pluralsight Connector: Connect to an external Pluralsight account. Perform tasks like managing users and accessing learning insights. Use Pluralsight as a data target (action).
Postman Connector (Beta): Connect to an external Postman account. Perform tasks like managing collections or creating API documentation. Use Postman as a data target (action).
Postmark Connector (Beta): Connect to an external Postmark account. Perform tasks like sending emails or retrieving outbound statistics. Use Postmark as a data target (action).
Qlik Connector: Connect to an external Qlik account. Perform tasks like creating and listing spaces, listing recent audit events and roles, managing users, or assigning license access. Use Qlik as a data target (action).
Qualtrics Connector: Connect to an external Qualtrics account. Perform tasks like syncing contacts and creating mailing lists. Use Qualtrics as a data target (action).
QuickBooks Online Connector: Connect to an external QuickBooks Online account. Perform tasks like syncing customers or creating invoices. Use QuickBooks Online as a data source (trigger) or a data target (action).
QuickBooks Online GraphQL Connector: Connect to an external QuickBooks Online GraphQL account. Perform tasks like creating projects or getting project details. Use QuickBooks Online GraphQL as a data target (action).
Rally Connector: Connect to an external Rally account. Perform tasks like creating defects or accessing workspace and project information. Use Rally as a data target (action).
Razorpay Connector (Beta): Connect to an external Razorpay account. Perform tasks like creating orders or retrieving refunds. Use Razorpay as a data target (action).
ReadMe Connector (Beta): Connect to an external ReadMe account. Perform tasks like managing documentation or creating API references. Use ReadMe as a data target (action).
Rebrandly Connector (Beta): Connect to an external Rebrandly account. Perform tasks like creating links or managing tags. Use Rebrandly as a data target (action).
Recruitee Connector (Beta): Connect to an external Recruitee account. Perform tasks like creating candidates or retrieving candidate notes. Use Recruitee as a data target (action).
Recurly Connector (Beta): Connect to an external Recurly account. Perform tasks like managing subscriptions or retrieving invoices. Use Recurly as a data target (action).
Rollbar Connector (Beta): Connect to an external Rollbar account. Perform tasks like retrieving items or updating item details. Use Rollbar as a data target (action).
RudderStack Connector (Beta): Connect to an external RudderStack account. Perform tasks like identifying users or tracking events. Use RudderStack as a data target (action).
Salesforce Connector: Connect to an external Salesforce account. Perform tasks like syncing contacts or transferring opportunities. Use Salesforce as a data source (trigger) or a data target (action).
Salesforce Commerce Connector: Connect to an external Salesforce Commerce account. Perform tasks like syncing customers or creating products. Use Salesforce Commerce as a data target (action).
Salesforce Marketing Connector: Connect to an external Salesforce Marketing account. Perform tasks like syncing contacts and sending transactional messages. Use Salesforce Marketing as a data target (action).
SAP S/4HANA Connector: Connect to an external SAP S/4HANA account. Perform tasks like retrieving purchase orders, suppliers, GL accounts, and invoices. Use SAP S/4HANA as a data target (action).
Scalefusion Connector: Connect to an external Scalefusion account. Perform tasks like managing admins, retrieving devices, or accessing roles. Use Scalefusion as a data target (action).
Sematext Connector: Connect to an external Sematext account. Perform tasks like managing alert rules and dashboard subscriptions, or sending automated reports. Use Sematext as a data target (action).
Sentry Connector: Connect to an external Sentry account. Perform tasks like managing organization releases or administering release files and data. Use Sentry as a data target (action).
ServiceNow Connector: Connect to an external ServiceNow account. Perform tasks like creating incidents or updating service requests. Use ServiceNow as a data target (action).
Shippo Connector (Beta): Connect to an external Shippo account. Perform tasks like creating addresses or getting shipment rates. Use Shippo as a data target (action).
ShipStation Connector: Connect to an external ShipStation account. Perform tasks like managing your shipments, carriers, and warehouses. Use ShipStation as a data target (action).
Shodan Connector: Connect to an external Shodan account. Perform tasks like retrieving host and account profile details and running network and DNS lookups. Use Shodan as a data target (action).
Shortcut Connector (Beta): Connect to an external Shortcut account. Perform tasks like creating stories or retrieving epics. Use Shortcut as a data target (action).
SignNow Connector: Connect to an external SignNow account. Perform tasks like managing teams, retrieving document history, or handling signature invites. Use SignNow as a data target (action).
SignUpGenius Connector: Connect to an external SignUpGenius account. Perform tasks like getting invites and adding group members. Use SignUpGenius as a data target (action).
Slite Connector: Connect to an external Slite account. Perform tasks like creating, updating, deleting, and searching notes. Use Slite as a data target (action).
Snowflake Connector: Connect to an external Snowflake account. Perform tasks like submitting SQL statements, checking their status, or canceling them. Use Snowflake as a data target (action).
SolarWinds Connector: Connect to an external SolarWinds account. Perform tasks like managing tickets, users, groups, and incidents. Use SolarWinds as a data target (action).
Square Connector: Connect to an external Square account. Perform tasks like creating subscriptions or syncing customers. Use Square as a data target (action).
SquaredUp Connector: Connect to an external SquaredUp account. Perform tasks like accessing workspaces and alerting channels, or managing users. Use SquaredUp as a data target (action).
StatusCake Connector (Beta): Connect to an external StatusCake account. Perform tasks like creating uptime checks or retrieving heartbeat checks. Use StatusCake as a data target (action).
Statuspage Connector (Beta): Connect to an external Statuspage account. Perform tasks like creating incidents or listing pages. Use Statuspage as a data target (action).
Stripe Connector: Connect to an external Stripe API account. Perform tasks like creating, updating, deleting, and retrieving customer records. Use Stripe as a data target (action).
Sumo Logic Connector: Connect to an external Sumo Logic account. Perform tasks like creating search jobs or retrieving collectors. Use Sumo Logic as a data target (action).
Supabase Connector: Connect to an external Supabase account. Perform tasks like managing projects and login roles, or creating organizations. Use Supabase as a data target (action).
SurveyMonkey Connector: Connect to an external SurveyMonkey account. Perform tasks like syncing contacts or creating collectors. Use SurveyMonkey as a data target (action).
Survicate Connector (Beta): Connect to an external Survicate account. Perform tasks like retrieving survey responses or listing surveys. Use Survicate as a data target (action).
SYSTRAN Connector: Connect to an external SYSTRAN account. Perform tasks like creating a batch, detecting text, or getting the translation status. Use SYSTRAN as a data target (action).
Taboola Connector: Connect to an external Taboola account. Perform tasks like managing content discovery campaigns, performance analytics, and audience targeting. Use Taboola as a data target (action).
TeamCity Connector: Connect to an external TeamCity account. Perform tasks like managing users and administering projects. Use TeamCity as a data target (action).
Teamwork Connector (Beta): Connect to an external Teamwork account. Perform tasks like managing projects or tracking time entries. Use Teamwork as a data target (action).
Tenable Connector: Connect to an external Tenable account. Perform tasks like retrieving scan details, users, and scanners, or managing asset attributes. Use Tenable as a data target (action).
ThoughtSpot Connector: Connect to an external ThoughtSpot account. Perform tasks like managing users, automating account creation or deactivation, or fetching security logs for incident response. Use ThoughtSpot as a data target (action).
ThousandEyes Connector: Connect to an external ThousandEyes account. Perform tasks like managing users or alert suppression windows. Use ThousandEyes as a data target (action).
TikTok Ads Connector: Connect to an external TikTok Ads account. Perform tasks like managing ads, ad groups, and campaigns. Use TikTok Ads as a data target (action).
Tines Connector: Connect to an external Tines account. Perform tasks like managing stories, resources, and teams. Use Tines as a data target (action).
Toggl Connector: Connect to an external Toggl account. Perform tasks like managing time entries and workspace projects. Use Toggl as a data target (action).
Toggl Track Connector (Beta): Connect to an external Toggl Track account. Perform tasks like creating time entries or retrieving the current time entry. Use Toggl Track as a data target (action).
Tomorro Connector: Connect to an external Tomorro account. Perform tasks like managing contracts and companies, generating NDA drafts, syncing vendor details, or automating renewal and ITSM workflows. Use Tomorro as a data target (action).
Trend Micro Connector: Connect to an external Trend Micro account. Perform tasks like managing users and groups, sending invitations, or administering user roles and permissions. Use Trend Micro as a data target (action).
Twilio Connector: Connect to an external Twilio account. Perform tasks like sending messages or creating calls. Use Twilio as a data target (action).
Twilio Messaging Connector: Connect to an external Twilio Messaging account. Perform tasks like managing phone numbers and messaging services. Use Twilio Messaging as a data target (action).
Twilio Notify Connector: Connect to an external Twilio Notify account. Perform tasks like retrieving service resources. Use Twilio Notify as a data target (action).
Twilio SendGrid Connector (Beta): Connect to an external Twilio SendGrid account. Perform tasks like creating templates or sending emails. Use Twilio SendGrid as a data target (action).
UiPath Orchestrator Connector: Connect to an external UiPath Orchestrator account. Perform tasks like managing jobs, queues, robots, and processes. Use UiPath Orchestrator as a data target (action).
Vibes Connector: Connect to an external Vibes account. Perform tasks like creating campaigns and listing callbacks. Use Vibes as a data target (action).
VictorOps Connector (Beta): Connect to an external VictorOps account. Perform tasks like creating incidents or retrieving alerts. Use VictorOps as a data target (action).
WireMock Connector (Beta): Connect to an external WireMock account. Perform tasks like creating mock APIs or managing stub mappings. Use WireMock as a data target (action).
WordPress Connector: Connect to an external WordPress account. Perform tasks like creating posts and updating comments. Use WordPress as a data target (action).
Workable Connector (Beta): Connect to an external Workable account. Perform tasks like managing candidates or updating job applications. Use Workable as a data target (action).
Workday Absence Management Connector: Connect to an external Workday Absence Management account. Perform tasks like getting time-off balances and leave details, and requesting time off for a worker. Use Workday Absence Management as a data target (action).
Workday Expenses Connector: Connect to an external Workday Expenses account. Perform tasks like getting expense items and expense reports, and creating an expense report. Use Workday Expenses as a data target (action).
Workday Organizations Connector: Connect to an external Workday Organizations account. Perform tasks like getting organizations and retrieving an organization by ID. Use Workday Organizations as a data target (action).
Workday Staffing Connector: Connect to an external Workday Staffing account. Perform tasks like getting job profiles and workers, retrieving a worker by ID, and starting a job change. Use Workday Staffing as a data target (action).
Wrike Connector: Connect to an external Wrike account. Perform tasks like administering folders or projects and managing users or user groups. Use Wrike as a data target (action).
Wufoo Connector (Beta): Connect to an external Wufoo account. Perform tasks like retrieving forms or users. Use Wufoo as a data target (action).
xMatters Connector: Connect to an external xMatters account. Perform tasks like managing events, adding comments, or retrieving people and on-call information. Use xMatters as a data target (action).
Yeeflow Connector (Beta): Connect to an external Yeeflow account. Perform tasks like managing departments or locations. Use Yeeflow as a data target (action).
YouTrack Connector (Beta): Connect to an external YouTrack account. Perform tasks like retrieving current users or updating issues. Use YouTrack as a data target (action).
YugabyteDB Connector: Connect to an external YugabyteDB account. Perform tasks like managing clusters and cluster nodes, administering alert rules, or retrieving cluster metrics. Use YugabyteDB as a data target (action).
Zendesk Connector: Connect to an external Zendesk account. Perform tasks like creating tickets or updating comments. Use Zendesk as a data source (trigger) or a data target (action).
Zoom Connector: Connect to an external Zoom account. Perform tasks like creating webinars or adding registrants. Use Zoom as a data target (action).
Zscaler Connector: Connect to an external Zscaler account. Perform tasks like creating URL categories and updating URL filtering rules. Use Zscaler as a data target (action).
Zuora Connector: Connect to an external Zuora account. Perform tasks like creating orders or syncing products. Use Zuora as a data target (action).
Zuva DocAI Connector (Beta): Connect to an external Zuva DocAI account. Perform tasks like getting extractions or retrieving OCR text. Use Zuva DocAI as a data target (action).
Review Extracted Document Data: Open a review that a flow created, compare the extracted data with the original document, correct any values, and submit the review so the flow resumes.
Define What Data to Extract from Your Documents: Document Processing Configurations define the structure and rules for extracting data from your documents. By creating these configurations, you define what information to look for and how to organize the extracted data. This step is essential before you can process documents in your flows or set up review workflows.
Review Contract Data and Update Records Example: This example walks through a screen flow where a sales operations analyst reviews extracted contract data, corrects low-confidence values, then updates Contract and Opportunity records.
Process and Review Attached Documents Example: This example walks through a record-triggered flow that runs when a user attaches a document to a record. The flow extracts data, routes to an approval action and flow orchestration, then to a screen flow where the user reviews and corrects extracted values before the flow updates the record.
Route Reviewed Data to Records and Business Processes: Call the screen flow from the orchestration, branch on review outcomes, and add actions to update records, send notifications, or trigger other processes with the reviewed data.
Set Up Document Extraction and Routing to Human Review: Add the Extract Data from Document action to your flow, configure the document and configuration inputs, store the output, and route the extracted data to human review.
Flow Terminology: This glossary provides definitions for commonly used terms in Flow Builder.
Test a Flow for Error Handling: Configure negative assertions to verify that a flow handles errors gracefully when you use automated testing.
Generate Test Scenarios with Agentforce for Flow: Skip the manual setup and use Agentforce to draft your test scenarios from the command line, without opening Flow Builder. Generate comprehensive test scenarios for a record-triggered, autolaunched, or Data Cloud-triggered flow, including success, fault, and edge-case paths.
Test a Flow with Isolated Test Data: Test record-triggered and autolaunched flows using dedicated, reusable test data from an Apex class that includes a test setup method. After a test scenario runs, the isolated test data rolls back like an Apex unit test, so your org's live data stays as it was.
Test a Flow with Mock Outputs (Beta): Use mock outputs to test autolaunched and record-triggered flows without depending on external systems. Define predictable output values for action and subflow elements so your test scenarios validate flow logic instead of live callouts or subflow execution.
Testing Your Flow in Test Mode (Beta): Use Test Mode to configure, save, and run test scenarios for autolaunched and record-triggered flows. To use automated testing in Test Mode, turn on Scenario Testing Automation and add assertions to evaluate expected results automatically.
Turn On Flow Test Mode (Beta): Turn on flow Test Mode for your org so that users can test autolaunched and record-triggered flows in Flow Builder.
Automated Flow Testing: Understand assertions, flow versions, and test data before you set up an automated test scenario through Test Mode (beta) or for a Data Cloud-triggered flow.
Troubleshoot Flow Errors with Agentforce (Beta): Use Agentforce to troubleshoot design-time issues in saved flows and run-time errors in active flows, eliminating the need for manual troubleshooting. The Flow Automation agent diagnoses issues, identifies root causes, and explains remediation steps all in natural language. In some situations, the Flow Automation agent can automatically fix the flow for you.
Troubleshoot APEX_CPU_TIME_LIMIT_EXCEEDED Errors in Flows: When a transaction consumes too much CPU time, Salesforce throws an APEX_CPU_TIME_LIMIT_EXCEEDED error. Flows share this limit with every other automation in the same transaction, including Apex triggers.
Troubleshooting Flow Retries: Learn how a flow is run again after it failed to finish successfully. A flow retry is when a flow runs again to process records that failed to save successfully.
Run-Time Changes by Release and API Version: These versioned updates affect only flows that are configured to run on specific API versions. With versioned updates you can test and adopt run-time behavior changes for individual flows at your convenience.
Summer ’24 (API Version 61.0): These updates affect only flows that are configured to run on API version 61.0 and later.
Winter ’25 (API Version 62.0): These updates affect only flows that are configured to run on API version 62.0 and later.
Spring ’25 (API Version 63.0): These updates affect only flows that are configured to run on API version 63.0 and later.
Summer ’25 (API Version 64.0): These updates affect only flows that are configured to run on API version 64.0 and later.
Winter ’26 (API Version 65.0): These updates affect only flows that are configured to run on API version 65.0 and later.
Spring ’26 (API Version 66.0): These updates affect only flows that are configured to run on API version 66.0 and later.
Winter '27 (API Version 68.0): These updates affect only flows that are configured to run on API version 68.0 and later.
Automate Your Business Processes with Salesforce Flow: Say goodbye to manual tasks and hello to streamlined operations with Salesforce Flow. By using automation to reduce the number of manual processes and repetitive tasks, you decrease turnaround time, improve accuracy and user productivity, and reduce costs. Salesforce Flow offers no-code, point-and-click tools like Flow Builder and Flow Orchestration, which help you create guided visual experiences, behind-the-scenes automations, and approval automations.
Complete an Approval Work Item from an Email Notification: When the flow approval process assigns you an approval work item, you receive an email notification. If your org has email reply enabled, you can complete the work item by replying to the email with a keyword. You can also click the record link to complete the approval step in the Orchestration Work Guide.
Complete an Approval Work Item from the Approval Work Items List View: Use the Approval Work Items list view to find and complete your assigned approval work items. From the list view, you can select the Review action to complete an approval work item with the default approval screen flow. You can also open the record to complete the approval work item with the screen flow that the approval step calls.
Complete Approval Work Items: When someone submits a record for approval, the flow approval process assigns approval work items to the designated approvers for each step. You can find your assigned work items from an email notification or from the Approval Work Items list view. How you access your work item determines which completion methods are available to you.
Process Automation Settings: Salesforce provides various settings for platform automation to help customize and streamline business processes.
Equivalent Features in Flows and Workflow Rules: Features and fields in workflow rules correspond to certain things in flows. Use the equivalent features and fields to build flows that can replace your workflow rules.
Backup & Recover for Salesforce: Backup & Recover is designed to help you efficiently back up data, restore data if it's lost or corrupted, and meet data integrity and compliance goals. Precise data restoration tools help you identify and recover data affected by integration issues, system errors, or user error. You can create daily backups of data, attached files, metadata, managed packages, and sandboxes. Through secure cloud-to-cloud backups and independent data storage, stay connected to your backup data from anywhere without interruption.
Back Up Your Data with Backup & Recover for Salesforce: Safeguard your critical business information by adding a backup service to your account. Each service you add can back up Salesforce production data, production metadata, sandbox data, or sandbox metadata. Backups then run automatically, securing your data so it can be recovered.
Archive a Service in Backup & Recover for Salesforce: Preserve backup data after you migrate, decommission, or duplicate a Salesforce production or sandbox backup service instance. Archiving the service stops it from backing up new data. Access archived data for future restoration or data seeding.
Backup Types in Backup & Recover for Salesforce: After you add a backup service, full backups and incremental updates run automatically for continuous data integrity. You can also run backups on demand.
Verify Data Integrity with Blockchain Verify for Salesforce: Blockchain Verify ensures data integrity and authenticity within electronic storage, preventing fraud through verification against falsifying changes. Blockchain technology provides irrefutable evidence that backups remain unaltered, supporting regulatory compliance such as SEC17a-4.
Salesforce Bypass Best Practice Examples: Salesforce Automation Bypass temporarily disables automations, such as validation rules and flows. Use custom checkboxes on the User object, and then add conditions to the automations to verify the checkbox state. Set the checkbox to true to bypass the automation for that user. This gives you more control when you restore Salesforce data, without impacting other users.
Continuous Data Protection for Salesforce: Protect high-value or dynamic data and achieve near-zero Recovery Point Objectives (RPO) with Continuous Data Protection. Use minute-level backups to recover Salesforce data from a specific moment and visualize real-time changes with the Data Changes Tracker.
Compare Salesforce Backups to Identify Record Changes: Identify record changes between two Salesforce backups by comparing them. You can analyze an entire org or focus on specific objects and their related objects. Quickly spot additions, modifications, and deletions to ensure data accuracy and integrity.
Confirm Salesforce Backups are Unchanged: Blockchain Verify provides irrefutable evidence of backup data integrity by storing a cryptographic hash of the backup on a public ledger. Organizations can meet regulatory compliance requirements with a time-stamped audit trail of all modifications and deletions.
Data Changes Tracker in Backup & Recover for Salesforce: The Data Changes Tracker helps you monitor changes in high-activity Salesforce data. Investigate unexpected deletions quickly, and make sure that your automations and integrations aren't making erroneous bulk changes. The Data Changes Tracker helps you achieve near-zero Recovery Point Objectives (RPOs).
Data Privacy in Backup & Recover for Salesforce: Data privacy involves the practices and measures taken to protect personal data, which helps you comply with regulations and maintain customer trust. By implementing data privacy measures, you protect personally identifiable information (PII) and mitigate risks associated with data breaches.
Download a Backup in Backup and Restore for Salesforce to CSV: Get a comprehensive and easily accessible record of your backup data in a CSV file. Use separated metadata objects for integration with other systems or for data management tasks. Gain insights into your backup history and performance when you filter and analyze backup data.
Embedded Images in Rich Text Areas: A rich field type in Salesforce is a field type where users can enter formatted text and add images and links.
Common Errors and Warnings in Backup & Recover for Salesforce: Understand common issues and get tips for fixing problems when you try to access your account, back up or restore data, set up a Continuous Data Protection (CDP) service, or respond to a Data Privacy request.
Export a Backup to a Microsoft Azure Blob: Export your Salesforce backup data to a Microsoft Azure blob, so that you can store data externally for additional backups or integrate with other services. Exporting to Azure blob storage can facilitate the use of archived data in external reports, which can help with data analysis and reporting storage.
How to Search within Salesforce Backups: Find provides advanced full-text search within your backup snapshots, so you can quickly locate specific information. Search across all fields, standard and custom objects, Chatter feeds, and even within attachments like PDFs and Word documents. See all records matching your criteria, and compare versions across snapshots to track changes over time.
Search for Records and Attachments in Salesforce Backups: Search your Salesforce backup history and easily retrieve any record or attachment by using Find. Find helps you comply with regulations and initiate a restore job from the results found.
Fix Missing FLS Permissions for Backup: Ensure your Salesforce Backup service can access all necessary data by fixing missing field-level security (FLS) permissions. Identify inaccessible data for your backup service's authenticated user and then update the user's permission set with the missing field permissions.
Working with Formula Fields for Salesforce: Formula fields in Salesforce are read-only, so Own Data Platform captures the formula's logic as part of the metadata backup. And then, restoring or replicating records automatically recreates the formula's result upon data insertion.
Get Started with Backup & Recover for Salesforce: Set up and run your first backup with minimal friction. As a first-time user, provision an Own account as the Master Admin, connect a Salesforce org, and add an initial backup service. Configure key security and user access settings so your team can operate securely.
Backup History Tab in Backup & Recover for Salesforce: For each backup service, the Backup History tab provides an overview of all backups performed. See what type of backup was done, how long it took, and how many records and files were backed up.
Back Up History Tables in Backup & Recover for Salesforce: Include an object's field history in Salesforce backups. History tables capture and store historical data for each record, so you can track changes and understand the evolution of data over time.
Key Features of Backup & Recover for Salesforce: Track backups and view trends using the dashboard. Set up Smart Alerts to monitor changes to data. Search your backup history to find records and attachments. Comply with data privacy laws using tools that simplify the process.
Manage Backup Exclusion Rules in Backup & Recover for Salesforce: Create and verify rules to control your Salesforce backup content with backup exclusions. Select items that you don't want backed up and easily view them in one place with a clear audit trail.
Manage Metadata Restore in Salesforce: Restore Salesforce metadata to recover from data loss and corruption by reverting changes to metadata objects. Restore deleted or corrupted metadata components such as reports, layouts, and workflows.
Understand Supported Salesforce Objects: Ensure your data is fully protected by reviewing which Salesforce objects are supported in backups. By default, backups include history, share, and feed objects. Configure backups to include knowledge articles or custom big objects.
Run Backups On Demand in Backup & Recover for Salesforce: If a Salesforce automatic backup fails or you don't want to wait for the next scheduled backup, you can start a backup at any time. Back up the entire service or only specific objects.
Permissions Report in Backup & Recover for Salesforce FAQs: The Permissions Report lets you know when your Salesforce authenticated user is missing permissions needed to back up data. Find answers to questions about Permissions Reports.
Preserve Salesforce Record Audit Fields: Maintain accurate historical data in Salesforce by preserving record audit fields. Keep original values, such as dates and users, of audit fields during data operations such as restore, seed, or unarchive jobs.
Repair Field-Level Data Corruption in Salesforce: Maintain the integrity and accuracy of your data by repairing field-level corruption. Restoring data fields to their correct state prevents potential cascading effects on related processes or systems, keeping your organization’s data consistent and trustworthy.
Repair Data Loss to Restore Records in Salesforce: Restore deleted Salesforce records and their associated child records and attachments to maintain accurate and reliable data. By quickly restoring normal operations, you minimize downtime, support business continuity, and meet compliance requirements.
Restore a Salesforce Organization to Recover Lost Data: Revert your entire Salesforce organization to a previous state to recover from widespread data corruption or loss. Restore all deletions and changes between snapshots, including records deleted or changed.
Protect Personal Data with Privacy Requests: Safeguard personal data in Salesforce from unauthorized access to comply with regulations such as GDPR. Protecting personally identifiable information (PII) helps you maintain customer trust. Implement data privacy measures to efficiently handle data subject requests and mitigate risks associated with data breaches.
Restore Converted Leads for Salesforce: Revert leads to their original status, even if they were converted prematurely. Avoid unwanted accounts, contacts, and opportunities created when leads convert too early.
Restore Salesforce Data with Precision: Identify and correct unwanted changes in your SaaS data using precision repair. Run a data compare job, review the results, and select specific tables or objects to repair. By pinpointing only specific records, you maintain data integrity without disrupting your Salesforce environment.
Salesforce History, Share, and Feed Items Restoration: Restoring Salesforce history, share, and feed items helps to maintain a consistent, compliant, and fully functional Salesforce environment after any data recovery operations. In the event of data loss or corruption, restoring share and feed items helps maintain data integrity and sharing rules, while history tables are backed up for investigative and audit value.
Restore Salesforce Knowledge Article Versions: Recover lost data when you restore deleted or corrupted knowledge articles. Find discrepancies by comparing article versions and then restoring specific articles to help maintain continuity and knowledge integrity within your organization.
Restoring Salesforce Knowledge Articles Overview: Knowledge articles can be backed up and restored to protect against data loss and corruption. You can restore Knowledge articles to recover an entire article or its draft version, and fix corrupted content or publication status.
Restore Merged Salesforce Records: Restore records and related data after accidental merges by using the Dashboard tab or the Restore tab.
Restore and Confirm Metadata for Salesforce Using Visual Studio Code: Use Visual Studio (VS) Code to restore metadata and recover changes in your Salesforce environment. Efficiently run a metadata compare job to identify added, changed, or removed metadata records. View and select changes, copy code, and deploy it back to your Salesforce org.
Restore Metadata Using Workbench: Restore Salesforce metadata objects to minimize disruptions and ensure business operations continue smoothly. Compare metadata changes to easily deploy specific objects that have been deleted or corrupted, avoiding the cost and complexity of a full organizational restore.
Backup Retention Policies in Backup & Recover for Salesforce: Retention policies help you meet requirements for keeping Salesforce data backed up. You can adjust retention periods and retain backups indefinitely when needed for legal procedures.
How Backup & Recover Uses Salesforce APIs: Backup & Recover uses Salesforce APIs for its backup and restore operations. The API calls that Backup & Recover makes don’t count against your org's API limits.
Backup Service Dashboard in Backup & Recover for Salesforce: The Backup Service Dashboard for Salesforce provides a compreshensive overview of a service. See how many records and files are backed up, find out which recent backups had issues, and visualize changes in objects over time.
Essential Service Options in Backup & Recover for Salesforce: Configure and optimize your Salesforce backup services to meet your business needs. For example, you can schedule automatic backups for off-peak hours, pause or archive a service, or set retention policies to comply with regulations.
Services Page in Backup & Recover for Salesforce: On the Services page, you can see the status of your Salesforce backup services at a glance. Find text in a backup, or compare two backups to identify record changes.
Set Up Personal Notifications: Control email notifications you receive for Salesforce services, such as backups, jobs, data privacy, permissions, and alerts. Customize notifications for individual services to stay informed about the features that are important to you.
Set Up Smart Alerts: Get notified of specific changes in your Salesforce SaaS data and metadata when you define rules for Backup & Recover Smart Alerts to monitor that data. Set a percentage change threshold to minimize false positives and proactively detect unwanted schema modifications.
Smart Alerts for Salesforce – Overview: Backup & Recover Smart Alerts tell you about critical changes to your Salesforce SaaS data and metadata, such as deletions and corruptions. Configure alerts that align with your company's priorities and compliance requirements to reduce false positives and enhance data management.
SQL Where Clause for Salesforce Data Recovery: Use SQL where clauses during recovery, repair, and restore processes to filter and select specific records. SQL where clauses give you precise control over which data is restored or repaired.
Track Data Changes in Backup & Recover for Salesforce: Start a Data Changes Tracker job to visualize Salesforce data changes captured in real time. See the number of record additions, changes, and deletions for all Salesforce objects or specific objects. Depending on the time range you specify, you can see how many changes occurred over minutes, hours, or days.
Use Salesforce Custom Object Metadata for Auditing and Troubleshooting: Access custom object metadata in Salesforce backups to audit changes and resolve issues in your Salesforce environment. Reviewing the metadata helps you identify and address errors related to permissions or access issues.
Verify Unchanged Backups Using Hash Algorithms: Confirm the integrity of your Salesforce backup data using a cryptographic hash stored on a public ledger. Using blockchain verification helps you meet compliance requirements and prevent fraud by maintaining a time-stamped audit trail.
Weekly Backup Report in Backup & Recover for Salesforce: The Weekly Backup Report surveys active Salesforce backup services from the last seven days. The report informs you of service successes, warnings, and errors. Use the report to take action and maintain awareness.
Backup & Recover for Dynamics: Backup & Recover for Dynamics provides enterprise-grade protection for Dynamics 365 and Power Platform data. Automatic daily backups create precise copies of all data and proactive monitoring alerts you of any suspect changes. Incidents are streamlined for quick recovery, so you can isolate data loss, understand its scope, and restore affected data. Configure backups for any number of production instances or sandboxes, regardless of their size or complexity. Maintain compliance with internal data retention policies, industry regulations, and government mandates.
Abort a Running Dynamics Backup: Stop a running backup in Dynamics to fix an error in production data, modify default backup options, or if the backup process slows down other critical jobs.
Aborting a Running Backup in Dynamics Overview: Use the Abort Backup feature when you want to stop a running Dynamics backup. If you discover errors during a backup or want to modify default options before the first backup is completed, you can stop a running backup.
Protect Your Data with Backup Services for Microsoft Dynamics: Safeguard your critical business information by adding a backup service to your account. After selecting a service type and completing the initial setup, backups run automatically to give you peace of mind knowing your data is secure and recoverable.
Dynamics Authenticated User Permission Requirements for Backup & Recover: The Authenticated User connects your Backup & Recover application to a client's Dataverse environment. Having a dedicated integration user enhances security, improves audit trails, and avoids API concurrency collisions.
Backup Summary for Dynamics: The Backup History tab for Dynamics provides a comprehensive overview of all backups in a service. View backup statuses, understand different backup types, and efficiently filter and export data for continuous data integrity and compliance.
Backup Types for Dynamics: Backup & Recover has several backup types to protect your company's data. The Own application provides clients with automatic daily backups of all Data services, including attachments, content documents, and Knowledge Base articles.
Verify Data Integrity with Blockchain Verify for Dynamics: Blockchain Verify ensures data integrity and authenticity within electronic storage, preventing fraud through verification against falsifying changes. Blockchain technology provides irrefutable evidence that backups remain unaltered, supporting regulatory compliance such as SEC17a-4.
Compare Dynamics Backups to Identify Record Changes: Identify record changes between two Dynamics backups by comparing them. You can analyze an entire org or focus on specific objects and their related objects. Quickly spot additions, modifications, and deletions to ensure data accuracy and integrity.
Configure Dynamics Automatic Backups: Specify the time to run Automatic Backups for Dynamics, such as off-peak hours, to minimize the impact on system performance.
Confirm Dynamics Backups are Unchanged: Blockchain Verify provides irrefutable evidence of backup data integrity by storing a cryptographic hash of the backup on a public ledger. Organizations can meet regulatory compliance requirements with a time-stamped audit trail of all modifications and deletions.
Data Privacy in Backup & Recover for Dynamics: Data privacy involves the practices and measures taken to protect personal data, which helps you comply with regulations and maintain customer trust. By implementing data privacy measures, you protect personally identifiable information (PII) and mitigate risks associated with data breaches.
Forbidden Tables in Dynamics Backup Exclusions: To maintain backup and recover capabilities, there are some tables that can't be excluded from backups. If you try to create a backup exclusion rule for these forbidden tables, an error message appears.
Backup Exclusions in Dynamics – Overview: Microsoft Dynamics Backup exclusions let you control backup content by creating rules to exclude items. Exclude items that you don't need in the backup for data security or to reduce the backup duration.
How to Search within Dynamics Backups: Find is an advanced full-text search capability available in all of your Dynamics backup snapshots. Find searches attachments and all fields on all standard and custom tables, fields, and more.
Search for Records and Attachments in Dynamics Backups: Search your Dynamics backup history and easily retrieve any record or attachment using Find. Find helps you comply with regulations and initiate a restore job from the results found.
Get Started with Backup & Recover for Dynamics: Backup & Recover for Dynamics provides automated, comprehensive backup and recovery for data, metadata, and attachments through granular, point-in-time restore capabilities. Protect your data from human error, malicious activity, and data corruption in production and sandbox environments.
Dynamics Backup History Overview: The Backup History tab displays a comprehensive list of backups, including those with incomplete file downloads due to API limitations or errors.
Manage Dynamics Backup Exclusion Rules: Create and verify rules to control your Microsoft Dynamics backup content with backup exclusions. Select items that you don't want backed up and easily view them in one place with a clear audit trail.
Reauthenticate Services for Dynamics: Maintain backup and recovery operations when you reauthenticate a service so that it can access Dynamics with the correct permissions and credentials. You can restore access and functionality to resolve issues such as an inactive authenticated user or a revoked token.
Repair Data Loss and Data Corruption in Dynamics: Retrieve all deleted records, child records, and attachments to maintain accurate and reliable data that minimizes downtime and meets critical compliance requirements. Correct field-level corruption to uphold data integrity and prevent cascading issues across related systems.
Restore Dynamics Data with Precision: The Precision Repair capabilities for Dynamics provide a visual, interactive, and end-to-end experience making it easy to identify and correct only the unwanted changes to your SaaS data.
Restore Environments in Dynamics: Restore environment data to the same environment for repairing data corruption or loss within an environment. You can also restore to different environments for testing or compliance purposes, such as validating production data in a sub-production instance before moving it back to production.
Restoring Data to Dynamics: The Restore application provides a comprehensive solution for restoring data based on backups to your Dynamics environment.
Dynamics Backup Retention Policies: Retention policies help you meet requirements for keeping data backed up. You can adjust retention periods and retain backups indefinitely when needed for legal procedures.
Dynamics Scheduled Export: Automate the export of data from a service to a specified endpoint such as an S3 Bucket, SQL Azure Blob, or Snowflake. Dynamics Scheduled Export facilitates regular data backups or data sharing by automating the export process, which saves time and reduces manual effort.
Backup & Recover for Dynamics Server to Server Authentication: Server to Server Authentication (also known as Service Account or Application User) is the common way apps registered on Microsoft AppSource access the Dataverse data of their subscribers.
Backup Service Dashboard for Dynamics: The Backup Service Dashboard for Dynamics provides a comprehensive overview of backup data and files, visual data reports, and the number of records backed up. When you select a backup service from the dashboard, the specific dashboard for that service appears.
Archive a Dynamics Backup or Sandbox Service: Preserve data after a Microsoft Dynamics backup or sandbox service instance is migrated, decommissioned, or duplicated. Archiving backups stops the service from backing up new data. Access archived data for future restoration or data seeding.
Delete a Dynamics Sandbox Service: Free up resources and storage space after a sandbox service is outdated or refreshed. Deleting a sandbox service permanently removes all data associated with it.
Pause a Dynamics Backup Service: You can limit a vendor's access to your data during proof of concept or testing periods. By pausing instead of archiving, you can define when to resume backups and avoid losing backup coverage.
Services Screen for Dynamics – Overview: The Services Screen provides a centralized interface for managing Microsoft Dynamics backup services that protect and recover data. Perform actions related to backup service access and view service health quickly with visual status indicators.
Set Up Personal Notifications for Dynamics: Control email notifications you receive for Microsoft Dynamics services, such as backups, jobs, data privacy, permissions, and alerts. Customize notifications for individual services to stay informed about the features that are important to you.
Smart Alerts for Dynamics: Backup & Recover Smart Alerts tell you about critical changes to your Microsoft Dynamics SaaS data and metadata, such as deletions and corruptions. Configure alerts that align with your company's priorities and compliance requirements to reduce false positives and enhance data management.
Set Up Smart Alerts for Dynamics: Get notified of specific changes in your Dynamics SaaS data and metadata when you define rules for Backup & Recover Smart Alerts to monitor that data. Set a percentage change threshold to minimize false positives and proactively detect unwanted schema modifications.
SQL Where Clause Examples for Dynamics Data Recovery: Use SQL where clauses during Dynamics recovery, repair, and restore processes to filter and select specific records. SQL where clauses give you precise control over which data is restored or repaired.
Backup & Recover for ServiceNow: Backup & Recover for ServiceNow provides granular recovery, on-demand backups, and longer retention periods to protect data and meet data backup and recovery requirements. Synthetic backups minimize resource consumption by reducing the need for frequent full backups. Recovery tools isolate and restore only what you need. You control the timing and availability of backups while proactive monitoring alerts you to data loss or corruption.
Abort a Running ServiceNow Backup: Stop a running backup in ServiceNow to fix an error in production data, modify default backup options, or if the backup process slows down other critical jobs.
Aborting a Running Backup in ServiceNow Overview: Use the Abort Backup feature when you want to stop a running ServiceNow backup. If you discover errors during a backup or want to modify default options before the first backup is completed, you can stop a running backup.
Protect Your Data with Backup Services for ServiceNow: Safeguard your critical business information by adding a backup service to your account. After selecting a service type and completing the initial setup, backups run automatically to give you peace of mind knowing your data is secure and recoverable.
Managing API Consumption for ServiceNow Backups: In the Options menu, you can set the API Consumption limit. Admins are allowed to set limits for API consumption for data and attachments downloaded via the REST API.
Backup Summary for ServiceNow: The Backup History tab for ServiceNow provides a comprehensive overview of all backups in a service. View backup statuses, understand different backup types, and efficiently filter and export data for continuous data integrity and compliance.
Backup Types for ServiceNow: The application provides clients with automatic daily backups of all Data services, including attachments, content documents, and Knowledge Base articles.
Verify Data Integrity with Blockchain Verify for ServiceNow: Blockchain Verify ensures data integrity and authenticity within electronic storage, preventing fraud through verification against falsifying changes. Blockchain technology provides irrefutable evidence that backups remain unaltered, supporting regulatory compliance such as SEC17a-4.
Compare ServiceNow Backups to Identify Record Changes: Identify record changes between two ServiceNow backups by comparing them. You can analyze an entire org or focus on specific objects and their related objects. Quickly spot additions, modifications, and deletions to ensure data accuracy and integrity.
Configure ServiceNow Automatic Backups: Specify the time to run Automatic Backups for ServiceNow, such as off-peak hours, to minimize the impact on system performance.
Configure OAuth for ServiceNow: ServiceNow provides an OAuth authorization code grant flow by using REST. This allows users to access resources by authenticating directly with an OAuth server, rather than authenticating with a username and password. We use this authorization code grant flow process when connecting between a ServiceNow instance and our services.
Confirm ServiceNow Backups are Unchanged: Blockchain Verify provides irrefutable evidence of backup data integrity by storing a cryptographic hash of the backup on a public ledger. Organizations can meet regulatory compliance requirements with a time-stamped audit trail of all modifications and deletions.
Data Privacy in Backup & Recover for ServiceNow: Data privacy involves the practices and measures taken to protect personal data, which helps you comply with regulations and maintain customer trust. By implementing data privacy measures, you protect personally identifiable information (PII) and mitigate risks associated with data breaches.
Common Errors and Warnings for ServiceNow – Attachments: Check out common errors and warnings related to attachments you sometimes encounter while using Backup & Recover for ServiceNow. For each issue, we offer a clear explanation of the cause and actionable steps you can take to resolve it.
Common Errors and Warnings for ServiceNow – Backup: Check out common errors and warnings related to Backup you sometimes encounter while using Backup & Recover for ServiceNow. For each issue, we offer a clear explanation of the cause and actionable steps you can take to resolve it.
Common Errors and Warnings for ServiceNow – Restore: Check out common errors and warnings related to Restore you sometimes encounter while using Backup & Recover for ServiceNow. For each issue, we offer a clear explanation of the cause and actionable steps you can take to resolve it.
Common Errors and Warnings for ServiceNow – Synthetic Backups: Check out common errors and warnings related to Synthetic Backup you sometimes encounter while using Backup & Recover for ServiceNow. For each issue, we offer a clear explanation of the cause and actionable steps you can take to resolve it.
Application Exclusions for ServiceNow: Application Exclusions in ServiceNow enable users to exclude applications they don’t consider critical. This reduces Own's API consumption on the instance, thereby reducing backup durations, errors, and performance load.
Excluding Attachments for ServiceNow: Create a Backup Exclusion rule to exclude attachments or limit the number of attachments downloaded per daily scheduled backup.
Exclude Multiple Tables from a ServiceNow Backup: Omit certain tables from the backup process to optimize performance, reduce backup duration, and avoid overloading the ServiceNow instance. Exclude various tables from backups, such as those that are non-critical, hold system data, or have restricted access.
Forbidden Tables in ServiceNow Backup Exclusions: To maintain backup and recover capabilities, there are some tables that can't be excluded from backups. If you try to create a backup exclusion rule for these forbidden tables, an error message appears.
Backup Exclusions in ServiceNow – Overview: ServiceNow Backup exclusions let you control backup content by creating rules to exclude items. Exclude items that you don't need in the backup for data security or to reduce the backup duration.
How to Search within ServiceNow Backups: Find is an advanced full-text search capability available in all of your ServiceNow backup snapshots. Find searches attachments and all fields on all standard and custom tables, fields, and more.
Search for Records and Attachments in ServiceNow Backups: Search your ServiceNow backup history and easily retrieve any record or attachment using Find. Find helps you comply with regulations and initiate a restore job from the results found.
Get Started with Backup & Recover for ServiceNow: Backup & Recover for ServiceNow provides automated, comprehensive backup and recovery for data, metadata, and attachments through granular, point-in-time restore capabilities. Protect your data from human error, malicious activity, and data corruption in production and sandbox environments.
ServiceNow Backup History Overview: The Backup History tab displays a comprehensive list of backups, including those with incomplete file downloads due to API limitations or errors.
Manage ServiceNow Backup Exclusion Rules: Create and verify rules to control your ServiceNow backup content with backup exclusions. Select items that you don't want backed up and easily view them in one place with a clear audit trail.
Optimizing a ServiceNow Backup Service: Some methods are available for reducing the duration of a ServiceNow backup. Changes you make to configurations take effect in subsequent backups.
Permissions Report for Your ServiceNow Instance: The Permissions Report for ServiceNow identifies tables that the authenticated user doesn't have web service access to, which can cause incomplete backups. You can resolve permission issues using insights from the report such as excluding certain tables from backups.
Reauthenticate Services for ServiceNow: Maintain backup and recovery operations when you reauthenticate a service so that it can access ServiceNow with the correct permissions and credentials. You can restore access and functionality to resolve issues such as an inactive authenticated user or a revoked token.
Repair Data Loss and Data Corruption in ServiceNow: Retrieve all deleted records, child records, and attachments to maintain accurate and reliable data that minimizes downtime and meets critical compliance requirements. Correct field-level corruption to uphold data integrity and prevent cascading issues across related systems.
Resolve Permissions in ServiceNow: Resolving permission issues enables your backup to access all necessary data, preventing an incomplete backup of your ServiceNow instance. If restricted tables are left unaddressed, they can compromise data integrity during recovery.
Restore ServiceNow Data with Precision: The Precision Repair capabilities for ServiceNow provide a visual, interactive, and end-to-end experience making it easy to identify and correct only the unwanted changes to your SaaS data.
Restore Environments in ServiceNow: Restore environment data to the same environment for repairing data corruption or loss within an environment. You can also restore to different environments for testing or compliance purposes, such as validating production data in a sub-production instance before moving it back to production.
Restoring Data to ServiceNow: The Restore application provides a comprehensive solution for restoring data based on backups to your ServiceNow environment.
ServiceNow Backup Retention Policies: Retention policies help you meet requirements for keeping data backed up. You can adjust retention periods and retain backups indefinitely when needed for legal procedures.
Update Semaphores Assigned for API_INT in a ServiceNow Instance: A ServiceNow instance has one or more application nodes. An application node is a Tomcat web server with a database. An application node (node) contains semaphores, which are a throttling concept. Essentially, semaphores execute and process transactions within an application node. ServiceNow has several semaphores to handle different transactions like API transactions, default pool transactions (user interaction within the platform, and more. When users log in, they end up on one of the available application nodes. Reallocate semaphore capacity to the API_INT semaphore to process REST API requests faster.
Backup Service Dashboard for ServiceNow: The Backup Service Dashboard for ServiceNow provides a comprehensive overview of backup data and files, visual data reports, and the number of records backed up.
Archive a ServiceNow Backup or Sandbox Service: Preserve data after a ServiceNow backup or sandbox service instance is migrated, decommissioned, or duplicated. Archiving backups stops the service from backing up new data. Access archived data for future restoration or data seeding.
Delete a ServiceNow Sandbox Service: Free up resources and storage space after a sandbox service is outdated or refreshed. Deleting a sandbox service permanently removes all data associated with it.
Pause a ServiceNow Backup Service: You can limit a vendor's access to your data during proof of concept or testing periods. By pausing instead of archiving, you can define when to resume backups and avoid losing backup coverage.
Services Screen for ServiceNow – Overview: The Services Screen provides a centralized interface for managing ServiceNow backup services that protect and recover data. Perform actions related to backup service access and view service health quickly with visual status indicators.
Set Up Personal Notifications for ServiceNow: Control email notifications you receive for ServiceNow services, such as backups, jobs, data privacy, permissions, and alerts. Customize notifications for individual services to stay informed about the features that are important to you.
Smart Alerts for ServiceNow: Backup & Recover Smart Alerts tell you about critical changes to your ServiceNow SaaS data and metadata, such as deletions and corruptions. Configure alerts that align with your company's priorities and compliance requirements to reduce false positives and enhance data management.
Set Up Smart Alerts for ServiceNow: Get notified of specific changes in your ServiceNow SaaS data and metadata when you define rules for Backup & Recover Smart Alerts to monitor that data. Set a percentage change threshold to minimize false positives and proactively detect unwanted schema modifications.
Recover for ServiceNow Synthetic Backups: Recover for ServiceNow’s Synthetic Backups is an incremental backup solution that identifies and extracts data that has been added, changed, or removed since the previous full backup. These deltas are merged with the previous backup to create a “synthetic full” backup which reduces the need for a “full” backup. With this approach we can reduce API calls, resource consumption, performance impacts, and backup duration.
Backup & Recover for Workday: Backup & Recover for Workday efficiently backs up and restores data within the Workday environment. Help your organization meet audit and regulatory obligations when you back up data, files, and attachments. Integrated tools enable quick restoration of lost or corrupted data, maintaining data integrity and minimizing loss. You can configure data retention policies to comply with specific country or regional requirements.
Add a Workday Backup Service: Secure your Workday data by adding a backup service. A Workday backup service protects data against loss and corruption and helps you meet data protection compliance regulations.
How to Search within Backups for Workday: The Find feature enables you to search the entire backup history and easily retrieve any record or attachment. This capability enables you to comply with regulations, and initiate a restore job from the results found.
Search for Records and Attachments in Backups for Workday: Use the Find tool to search for records and attachments. Any records that match the search criteria are subsequently displayed. If different versions of the same record appear across multiple backup snapshots, you can view and export the different versions to see the changes.
Get Started with Backup & Recover for Workday: Protect against data loss and facilitate restoration of your Workday data with Backup & Recover for Workday. Quickly locate specific data across your backups and identify changes between backup versions when you want to restore lost or corrupted records.
Restore Assist for Workday: The Restore Assist offers a visual, interactive, experience that helps you identify and precisely correct only the unwanted changes to your SaaS data.
Build with Events: Monitor the performance of your event subscribers.
Build Your Own Web Site: Site.com and Salesforce Sites are legacy systems to create sites using Salesforce.
Build an App: The Lifecycle: Every Builder Central build follows the same general flow, whatever you're building. This flow describes the phases in a build from start to finish.
Builder Central (Beta) Best Practices: Get better results from Builder Central: describe what you want clearly, keep your data private, and refine effectively when a result isn't what you wanted.
Edit Metadata Through Visualizations: In Builder Central, when you visualize metadata such as a data model, an agent, a flow, a flexipage, or a permission set, you can select an element(s) in the visualization and use the agent to edit its metadata.
Get Started with Builder Central (Beta): Build Salesforce apps and agents by describing what you want, in plain language. Learn what Builder Central is, who it's for, and what you need before you start
Builder Central (Beta) Permissions: Beyond the base access that turns on Builder Central and lets a user build, some apps need extra access, such as a license or add-on, based on what your app includes, such as generative AI features or an agent.
Refine and Edit Your App: After the Build Agent creates your app, you can refine it in Builder Central without starting over. Describe the changes you want in the chat, or use visual editing to adjust elements directly on the design canvas.
Set Up Builder Central (Beta): Turn on Builder Central and give each admin and builder access, so your team can start building apps and agents by describing what they want.
What You Need Before You Build: Builder Central builds for you, but the best results come from the context you provide. This context is optional, and you don't need it all up front. You share most of it as you describe and refine your app, not in your first prompt.
Canvas App Previewer: Canvas App Previewer is a development tool that lets you see what your canvas apps will look like before you publish them.
Heroku Quick Start: The Heroku Quick Start button gets you started by creating an app in Heroku and creating a corresponding canvas app in Salesforce.
Change Management: The Change Management tab offers a unified view of all the modifications across your current org. From this tab, you can view, manage, and commit metadata and data changes to your source control repository. You can also move metadata and data together for direct deployment to a target org.
Change Sets: Use change sets to send customizations from one Salesforce org to another. For example, you can create and test a new object in a sandbox org, then send it to your production org using a change set. Change sets can contain only modifications you can make through the Setup menu. For example, you can’t use a change set to upload a list of contact records. Change sets contain information about the org. They don’t contain data, such as records.
Components Available in Change Sets: The components available for a change set vary by experience and edition. Also, some components have dependencies on corresponding features.
Deployment Connections for Change Sets: A deployment connection is required between two Salesforce orgs to send change sets from one org to another. You can’t create deployment connections between arbitrary orgs. Instead, you create connections between all orgs affiliated with a production org. For example, if you have a production org and two sandboxes, a deployment connection is created between production and each sandbox. Also, a deployment connection is created between the two sandboxes.
Inbound Change Sets: An inbound change set is a change set that has been sent from another Salesforce org to the org you are logged in to. A change set must be deployed for the changes to take effect. You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.
Outbound Change Sets: An outbound change set is a change set created in the Salesforce org in which you are logged in and that you want to send to another org. You typically use an outbound change set for customizations created and tested in a sandbox and that are then sent to a production org.
View Details of a Deployment Connection: A deployment connection enables customizations to be copied from one Salesforce org to another. The deployment connections list shows which orgs are authorized to upload changes to this org, and which orgs allow this org to upload changes to them.
View Available Deployment Connections: A deployment connection enables customizations to be copied from one Salesforce org to another. The deployment connections list shows which orgs are authorized to upload changes to this org, and which orgs allow this org to upload changes to them.
Change Sets Best Practices: Review these best practices about dependencies, validation, and access settings.
Deploy a Change Set: You can deploy the contents of an inbound change set as a whole but not on a component-by-component basis.
Validate a Change Set: You can validate a change set without deploying changes. By validating you can view the success or failure messages you receive with an actual deploy.
Viewing Change Set Details: The Change Sets detail page lists information about a particular change set.
View Inbound Change Sets: The Inbound Change Sets page lists change sets awaiting deployment, as well as the history of deployed change sets.
When Change Sets Become Unavailable: A change set deployed from a source sandbox that you recently deleted or refreshed can temporarily appear available for deployment in the target org.
Select Components for an Outbound Change Set: You typically use an outbound change set for customizations created and tested in a sandbox and that are then sent to a production org.
View and Add Dependent Components to a Change Set: A dependency is a relationship where one or more components must exist for another component to exist. Add dependent components to a change set, unless the dependent components exist in every org where this change set is deployed.
Upload an Outbound Change Set: When you've assembled the components in a change set, you can upload it to another Salesforce org. After you upload a change set, you can't edit it or recall it.
Upload Change Sets During Staggered Salesforce Service Upgrades: During Salesforce service upgrades, production and sandbox environments don't always run the same version of the platform because the upgrades are staggered. Some components may have new functionality that prevents you from deploying that type of component. You can deploy such components after the production org runs the same version as sandbox.
Outbound Change Set Validation Errors: If you receive an error about cross-version validation, the org used to create the outbound change set is running on a different version than the destination org.
Permission Sets and Profile Settings in Change Sets: Developers can use permission sets or profile settings to specify permissions and other access settings in a change set. When deciding whether to use permission sets, profile settings, or a combination of both, consider the similarities and differences.
Formula Data Types: The data type of a formula determines the type of data you expect returned from your formula.
Custom Labels: Custom labels enable developers to create multilingual applications by automatically presenting information (for example, help text or error messages) in a user’s native language. Custom labels are custom text values that can be accessed from Apex classes, Visualforce pages, Lightning pages, or Lightning components. The values can be translated into any language Salesforce supports.
Create and Edit Custom Labels: Create custom labels that can be referenced from Apex classes, Visualforce pages, Lightning pages, or Lightning components to make an app multilingual.
Translate Custom Labels: Translations for custom labels determine what text to display for the label’s value when a user’s default language is the translation language.
Something Went Wrong...There’s No Help for This Custom Object: You landed on this page because you were looking for more information about a particular custom object, but your Salesforce admin didn’t create a help page for that object. Review the suggested resources. If you need information on a specific custom object, contact your administrator about creating custom help for your custom objects.
Something Went Wrong...There’s No Help for This Custom Object: You landed on this page because you were looking for more information about a particular custom object, but your Salesforce admin didn’t create a help page for that object. Review the suggested resources. If you need information on a specific custom object, contact your administrator about creating custom help for your custom objects.
Apex Code Overview: Apex is a strongly typed, object-oriented programming language that allows developers to execute flow and transaction control statements on the Salesforce Platform. Apex enables developers to add business logic to most system events, including button clicks, related record updates, and Visualforce pages. Apex code can be initiated by web service requests and from triggers on objects.
Apex Developer Guide and Developer Tools: The Apex Developer Guide and Apex Reference Guide provide the complete reference for the Apex programming language. The Apex Developer Guide explains how to invoke Apex, how to work with limits, how to write tests, and more. The Apex Reference Guide provides reference information on Apex classes, interfaces, exceptions and so on. To write Apex code, you can choose from several Salesforce and third-party tools.
What Happens When an Apex Exception Occurs?: When an exception occurs, code execution halts. Any DML operations that were processed before the exception are rolled back and aren’t committed to the database. Exceptions get logged in debug logs. For unhandled exceptions, which are exceptions that the code doesn’t catch, Salesforce sends an email that includes the exception information. The end user sees an error message in the Salesforce user interface.
Monitoring the Apex Flex Queue: Use the Apex Flex Queue page to view and reorder all batch jobs that have a status of Holding. Or reorder your batch jobs programmatically using Apex code.
Monitor the Apex Job Queue: The Apex Jobs Setup page has information about Apex jobs, including the percentage of async Apex usage and the number of Apex operations that have been used out of the 24-hour org limit. Monitor the status of Apex jobs to mitigate potential limit problems before they happen.
Debug Logs: Use debug logs to track events that occur in your org. Debug logs are generated when you have active user-based trace flags, when you run Apex tests, and when executed code or API requests include debugging parameters or headers.
Set Up Apex Class and Trigger Trace Flags: You can set up an Apex class or trigger trace flag in Salesforce Setup, in the Developer Console, or by creating Tooling API objects with Salesforce CLI commands. These trace flags have the CLASS_TRACING debug log type and override the debug log levels of the USER_DEBUG and DEVELOPER_LOG trace flags.
Delete Debug Logs: When your org accumulates too many debug logs, delete some or all of your system logs and monitoring logs. Use the Developer Console’s Query Editor to find and delete the logs using Tooling API.
Debug Log Details: A debug log includes a header, execution units, code units, log lines, and other log data.
Debug Log Order of Precedence: Which events are logged depends on various factors. These factors include your trace flags, the default logging levels, your API header, user-based system log enablement, and the log levels set by your entry points.
Define Apex Triggers: Apex code can be invoked by using triggers. Apex triggers can be configured to perform custom actions before or after changes to Salesforce records, such as insertions, updates, or deletions.
Developer Console: The Developer Console is an integrated development environment with a collection of tools you can use to create, debug, and test applications in your Salesforce org.
Overlaying Apex Code and SOQL Statements: Use the Developer Console to overlay diagnostics that run when Apex code executes at a checkpoint, without changing any code.
Set Checkpoints in Apex Code: Use Developer Console checkpoints to debug your Apex classes and triggers. You can’t set checkpoints in Visualforce markup.
Executing Anonymous Apex Code: The Developer Console allows you to execute Apex code as another way to generate debug logs that cover specific application logic.
Developer Console Debug Menu: The Developer Console Debug menu allows you to manage your logs and execute anonymous Apex. It includes these options.
Developer Console Edit Menu: The Developer Console Edit menu allows you to search and edit your code files. It includes these options.
Developer Console File Menu: The Developer Console File menu allows you to manage your Apex triggers and classes, Visualforce pages and components, and static resources (text, XML, JavaScript, or CSS). It includes these options.
Open the Developer Console: It takes only a couple of clicks to open the Developer Console from Salesforce Classic or Lightning Experience. The Developer Console is an integrated development environment with a collection of tools you can use to create, debug, and test applications in your Salesforce org.
Creating Custom Perspectives in the Log Inspector: Every developer has a different style. You can use one of our out-of-the box perspectives, create a custom perspective, or modify an existing perspective.
Logs Tab: Use the Logs tab in the Developer Console to access logs that include database events, Apex processing, workflow, callouts, and validation logic.
Checkpoints Tab: The Checkpoints tab displays a list of saved checkpoints that preserve a snapshot of the state of objects in memory at the time the checkpoint was reached.
Developer Console Query Editor: You can use the Query Editor in the Developer Console to execute a SOQL query or SOSL search on the data in your organization. A SOQL query retrieves data from a single object or multiple related objects in the database. You can execute a SOQL query immediately after data is added to the database. A SOSL query is a free-form text search that retrieves multiple related or unrelated objects and fields. Using SOSL, you can retrieve data for a specific term that exists within a field. And, SOSL can tokenize multiple terms to find relevant records. It can take several minutes for data to be indexed before you can execute a query and get results.
Retrieve Query Plans: Use the Query Plan tool to optimize and speed up queries done over large numbers of records. View query plans for SOQL queries, reports, and list views. If custom indexes are available for your organization, use query plans to help you decide when to request a custom index from Salesforce Support.
Query Results Grid: The Query Results grid displays each record as a row. You can create, update, and delete records without leaving the Developer Console. For SOSL search results with multiple objects, each object is displayed on a separate tab.
Tests Tab: Use the Developer Console to set up test runs, run tests, and check Apex code coverage.
View State Tab: The View State tab in the Developer Console allows you to examine the view state for a Visualforce page request.
Create a Test Run: A test run is a collection of classes that contain test methods. Set up a test run in the Developer Console to execute the test methods in one or more test classes.
Manage Sets of Apex Test Classes with Test Suites: A test suite is a collection of Apex test classes that you run together. For example, create a suite of tests that you run every time you prepare for a deployment or Salesforce releases a new version. Set up a test suite in the Developer Console to define a set of test classes that you execute together regularly.
Checking Code Coverage: The Developer Console retrieves and displays code coverage information from your organization. Code coverage results come from any tests you’ve run from an API or from a user interface (for example, the Developer Console, the Salesforce Extensions for Visual Studio Code, or the Application Test Execution page).
Checkpoint Inspector: Use checkpoints to investigate the objects in memory at a specific point of execution and see the other objects with references to them.
Source Code Editor: The Developer Console includes a Source Code Editor with a collection of features for editing Apex and Visualforce code.
Object Inspector: The Object Inspector provides a read-only reference for the fields of a standard or custom object, and their data types. To open the Object Inspector, click File > Open and select the object you want to view.
Log Inspector: The Log Inspector is a context-sensitive execution viewer in the Developer Console. It shows the source of an operation, what triggered the operation, and what occurred next. Use this tool to inspect debug logs that include database events, Apex processing, workflow, and validation logic.
Developer Console User Interface: Workspace: A workspace is a collection of resources represented by tabs in the main panel of the Developer Console. The detail view or editor shown in each tab is determined by the type of resource open in the tab. For example, source code opens in the Source Code Editor, logs open in the Log Inspector, and so on.
Email Services: You can use email services to process the contents, headers, and attachments of inbound email. For example, you can create an email service that automatically creates contact records based on contact information in messages.
Define Email Services: Set up an email service to handle incoming email, and configure the service to process messages according to your users' needs.
What Are Email Services?: Email services are automated processes that use Apex classes to process inbound email.
Handling Apex Exceptions in Managed Packages: When you create a managed package for AppExchange, you can specify a user to receive an email notification when an exception occurs that Apex doesn’t catch.
The InboundEmail Object: For every email the Apex email service domain receives, Salesforce creates a separate InboundEmail object that contains the contents and attachments of that email. You can use Apex classes that implement the Messaging.InboundEmailHandler interface to handle an inbound email message. Using the handleInboundEmail method in that class, you can access an InboundEmail object to retrieve the contents, headers, and attachments of inbound email messages, as well as perform many functions.
Manage Apex Classes: An Apex class is a template or blueprint from which Apex objects are created. Classes consist of other classes, user-defined methods, variables, exception types, and static initialization code.
Manage Apex Triggers: A trigger is Apex code that executes before or after specific data manipulation language (DML) events occur, such as before object records are inserted into the database, or after records have been deleted.
How Does Apex Class Security Work?: Limit which users can execute methods in a particular top-level Apex class based on their profiles or an associated permission set. This technique lets you apply granular security to Apex operations in your org.
Application Unit Tests: Run Apex and automated flow unit tests on methods, classes, sets of classes, or your whole org.
Schedule Apex Jobs: Use the Apex scheduler and the Schedulable interface if you have specific Apex classes that you want to run on a regular basis, or to run a batch Apex job using the Salesforce user interface.
Debug Log Levels: To specify the level of information that gets included in debug logs, set up trace flags and debug levels. The debug levels assigned to your trace flags control the type and amount of information that is logged for different events. After logging has occurred, inspect debug events in your debug logs.
Execute Application Tests: Select the Apex and flow tests that you want to run. Then examine the results, analyze error messages, and inspect your Apex source code.
Inspect Code Coverage Results: After you run tests using the Application Test Execution page, you can view code coverage details in the Developer Console.
Disable Parallel Test Execution: Tests that are started from the Salesforce user interface (including the Developer Console) run in parallel. Parallel test execution can speed up test run time. Sometimes, parallel test execution results in data contention issues, and you can turn off parallel execution in those cases.
Use the Independent Auto-Number Sequence Test Option: The Independent Auto-Number Sequence setting helps to avoid gaps in auto-number fields caused by test records created in Apex tests. This option isolates the auto-number sequence used in Apex tests from the sequence used in your org. As a result, the creation of test data in Apex tests doesn’t cause the sequence ofauto-number fields to be higher for new non-test records.
View Application Test History: The Application Test History page shows all the test results associated with a particular test run. The page shows results only for tests that have been run asynchronously.
View Application Test Results: From Setup, enter Application in the Quick Find box, select Application Test Execution, then click View Test History to view all test results for your org, not just tests that you have run. Test results are retained for 30 days after they finish running, unless cleared.
View Application Test Results Details: View all test results for your org in the default view for 30 days unless cleared, not just tests that you have run.
Choose Your Tools for Developing and Deploying Changes: Whether you’re an admin using point-and-click tools or a developer writing code, you can pick the right tool, work in a sandbox, and deploy complete changes to a production org. You can customize and code changes for your org in a sandbox using one, or more, of the tools provided by Salesforce.
Deploy Using Change Sets: You can deploy workflows, rules, Apex classes and triggers, and other customization from a sandbox org to your production org. You can create an outbound change set in the Salesforce user interface and add the components that you want to upload and deploy to the target org.
Deploy Metadata and Data from DX Inspector: Quickly move metadata and configuration data from your current Salesforce org (source org) to a target org in a single orchestration. You can access this feature from the Change Management tab in DX Inspector. This type of direct deployment is ideal for moving small, specific changes without using a full DevOps pipeline.
Deploy Using Lifecycle Center: Manage changes and releases collaboratively with Lifecycle Center, a tool designed for both low-code admins and pro-code developers. Lifecycle Center ensures a single source of truth and provides governed, version-controlled deployments by connecting your development environments (sandboxes, scratch orgs) to a source control repository.
Develop and Deploy Apex in the Developer Console: The Developer Console is an integrated development environment with a collection of tools you can use to create, debug, and test applications in your Salesforce org.
Develop and Deploy Using Metadata API: Use Metadata API to retrieve, deploy, create, update or delete customization information, such as custom object definitions and page layouts, for your org. This API is intended for managing customizations and for building tools that can manage the metadata model, not the data itself.
Manage Version Settings for Apex: To aid backwards-compatibility, Apex classes and triggers are stored with version settings for the Salesforce API and any referenced managed packages.
View Apex Classes: After you have created a class, you can view the code contained in the class, as well as the API against which the class was saved, and whether the class is valid or active.
View Apex Trigger Details: Apex triggers are stored as metadata in the application under the object with which they are associated.
Create an Apex Class from a WSDL: An Apex class can be automatically generated from a WSDL document that is stored on a local hard drive or network.
Opt Out of Approval Request Posts from Classic Approval Processes in Chatter: By default, after your org enables Approvals in Chatter, you’re notified about approval requests by email and a Chatter post. To stop seeing the Chatter posts, opt out. If you do opt out, the posts don’t appear in your feed but they do appear in the associated record’s feed.
Commit Changes to Source Repository: Commit changes to your source repository from the Change Management tab. After reviewing the changes, select the ones you want to include in the work item, then commit them to your Lifecycle Center project repository. When you commit changes, DX Inspector stores them in the repository branch created when the work item moved to the In Progress status.
Communication Subscription Objects: You can store and manage the data related to your customer’s communication subscriptions, such as newsletters or appointment reminders. Different communication subscription objects store different data, such as how the customer consented to the communication subscription and preferred contact timing.
Set Up a Custom Domain That Uses the Salesforce CDN: You can set up the Salesforce content delivery network (CDN) for your custom domain in Experience Builder, Salesforce Tabs, and Visualforce sites. Within each production environment, you can define multiple domains in a sandbox, but only one custom domain associated with a sandbox org can use the Salesforce CDN.
Considerations for the Salesforce CDN: If you host public-facing, cacheable content on your Experience Cloud sites, we recommend that you use the Salesforce content delivery network (CDN) to greatly improve load times.
Custom Firewall Rule Expressions on the Salesforce CDN: Custom web application firewall (WAF) rule expressions evaluate incoming traffic based on IP address, autonomous system number (ASN), or country. After you write an expression, choose whether to allow, block, or run a managed challenge on incoming traffic that matches the expression.
Edit Settings for the Salesforce CDN: Fine-tune the Salesforce content delivery network’s (CDN) default settings to address the unique needs of your storefront domains. Turn image optimization and the web application firewall (WAF) managed ruleset off or on. You can also protect your domain from malicious activity with up to 10 custom WAF rules based on autonomous system number (ASN), IP address, and country.
Content Delivery Networks (CDNs) and Salesforce: Optimize page load times and site performance with our content delivery network (CDN). Salesforce partners with a CDN provider to efficiently deliver publicly cacheable content to users on your Experience Cloud sites.
Prerequisites for the Salesforce CDN: Before you set up a custom domain that uses the Salesforce content delivery network (CDN), complete these steps.
Traffic Allowances for the Salesforce CDN: Each byte of traffic that’s requested, whether it’s an image or a complex report, counts toward your content delivery network’s (CDN) usage amount. The amount of traffic allowed over a CDN depends on the license that you purchase. Understand how to monitor your Salesforce CDN usage and what happens if you exceed the terabyte limit.
Assign Compact Layouts to Record Types: As with page layouts, there are separate compact layouts for each object. By default, each object derives its record highlight fields, preview cards, and action-related feed items from the predefined set of fields in the object’s read-only, system default compact layout. You can create custom compact layouts on an object-by-object basis. After you create one or more custom compact layouts, you set one as the primary compact layout for the object. The primary compact layout is then used as the new default for that object.
Create Compact Layouts: Use compact layouts to customize the fields that display for object records when viewed in the Salesforce mobile app and Lightning Experience.
Compact Layouts: A compact layout displays a record’s key fields at a glance in the Salesforce mobile app, Lightning Experience, and in the Outlook and Gmail integrations.
Conditional Field Formatting in Lightning App Builder: Make a field stand out by adding special formatting based on rules and criteria you provide, so that end users can quickly identify the most relevant information on a record page. You can apply conditional formatting to almost any field on a Dynamic Forms-enabled page, including the fields in the Dynamic Highlights Panel component.
Configuring the Size and Position of the Guidance Center: Personalize the in-app content experience with options for pinning and unpinning the Guidance Center panel. The Guidance Center panel also automatically expands for videos and Trailhead modules, offering more room on the screen for your content.
Consent Management Objects: Get familiar with the objects that you can use for managing your customers’ privacy and consent.
Fields in Contact Point Consent Records: Represents a customer's consent to be contacted via a specific contact point, such as an email address or phone number.
Fields in Contact Point Type Consent Records: Contact point type consent records let you enter details about how a customer has agreed to be contacted by your company. For example, you can indicate that a customer consented to a specific contact point like email, but not phone calls and mail.
Create a Slack Canvas Action: Creates a canvas in Slack. A Slack canvas is a surface built into Slack where you can create and share fully-formatted content.
Create a Change Request: After you commit changes to an In Progress work item and are ready to share them with team members, start a review from the development environment using DX Inspector. Creating a review moves the work item to In Review status and opens a change request (also called a pull request).
Create Feed-Based Page Layouts in Salesforce Classic: Make it easier for your users to work with account, contact, lead, opportunity, custom, and external object records by creating feed-based layouts. These layouts include two separate views: one for the record’s feed and one for its details.
Use Screen Flows to Interact with Users: Use screen flows to build online forms that collect or display information for internal and external users. Screen components enable you to gather user input or show data, such as using an Address component to collect street, city, state, and zip information. Create records such as contacts or leads from the collected data.
Create and Edit Personal Groups: Use personal groups to make it easier to manually share your records with other users. All users can create and edit their own personal groups in Salesforce Classic. Personal groups aren’t available in Lightning Experience.
Sandbox Types and Templates: Sandboxes are isolated from your production org, so operations that you perform in your sandboxes don’t affect your production org.
Create and Edit Public Groups: Create public groups to help configure your users’ access to records and other features. Only administrators and delegated administrators can create and edit public groups.
Create a Custom Object Tab: Give your users access to custom object data and records in an app. Custom object tabs are available only at the app level, not on subtab apps, and function like standard tabs.
Create Lightning Page Tabs: Before you can include a Lightning app page in the Salesforce mobile app or in a Lightning app, you must create a custom tab for it.
Create Global Quick Actions: You can add global actions to any page that supports actions, like the Home page, the Chatter tab, object pages, and custom Lightning app pages. For example, add a Log a Call action to global layouts so users can record call details right from a Chatter thread.
Create Global Publisher Layouts: Global publisher layouts determine the global actions that appear in the various Salesforce interfaces. In Salesforce Classic and Lightning Experience, these layouts customize the actions on global pages (like the Home page) and on the Chatter page. Lightning Experience also uses these layouts to populate the Global Actions menu. And in the Salesforce mobile app, these layouts drive the actions that appear in the action bar on the Feed and People pages. Global publisher layouts can include global actions only.
Create Multiple Business Processes: Follow these steps to create sales processes, support processes, lead processes, and solution processes.
Create Object-Specific Quick Actions: Object-specific actions let users create records with automatic relationships to other records, make updates to specific records, and interact with records in ways that you define.
Create Record Types: Before creating record types, include all of the possible record type values in your master list of picklists. The master picklist is a complete list of picklist values that can be used in any record type.
Create Web Tabs: Build web tabs so that your users can use your web applications or other websites from within the application.
Define a Flow Trigger for Workflow (Pilot): Create a flow trigger so that you can launch a flow from workflow rules. With flow triggers, you can automate complex business processes—create flows to perform logic, and have events trigger the flows via workflow rules—without writing code. For example, your flow looks up and assigns the relevant entitlement for a case. Create a flow trigger to launch the flow whenever a case is created, so that all new cases are automatically set with a default entitlement.
Create an Outbound Message Notification: You can request that up to five users receive a notification listing all outbound messages that have failed for at least 24 hours. A fresh notification is sent every 24 hours until you cancel the request.
View and Edit Custom Settings: After you create a custom setting, you can view the details of the custom setting, manage the custom setting, and add fields.
Grant Permissions on Custom Settings: By default, access to custom settings is limited through the Restrict access to custom settings org-wide preference. Admins can grant API Read access through profiles and permission sets to users without the Customize Application permission.
Manage Custom Settings Data: After creating custom setting and adding fields, you can add records, then use the values in these records in your Apex code and validation rules.
View the System Usage Data: View the number of custom objects and custom settings in your org, including installed objects from AppExchange.
Visualforce Pages as Global Custom Actions: Visualforce pages used as global actions can be invoked in many different places and don’t have a specific record associated with them. They have complete freedom of action, which means it’s up to you to write the code.
Visualforce Pages as Object-Specific Custom Actions: A Visualforce page added as a custom action on an object is invoked in the context of a record of that object type. The custom action is passed a specific record ID—the record the user was looking at when the user clicked the custom action. Design the page to act on that specific record type.
Hide the Action Header for Visualforce Custom Actions: When creating a Visualforce page to use as a custom action, you can choose to hide the action’s header. Hiding the action header helps prevent user confusion, especially if you have your own buttons specified in the Visualforce page.
Changing Big Object Fields: Learn how big object fields differ from standard object fields when you update or delete them. Make sure that your big object is correct before you save it.
Considerations When Creating an Index: Plan carefully when creating an index for your custom big object. The index is used for querying and filtering the big object data and must be designed properly.
Create or Edit a Big Object: Track and store big data that’s unique to your org. For existing big objects, a details page shows information about the big object’s fields and index.
Delete a Big Object: When you delete a custom big object, Salesforce doesn’t add it to the Recycle Bin. Instead, deleted big objects appear in the Deleted Objects list for 15 days. During this time, the big object and its data are soft deleted, meaning you can restore or permanently erase (flag for hard delete) the big object and its data. After 15 days, the big object and its data are automatically flagged for hard delete.
Add an Index to a Big Object: The index defines the composite primary key for a custom big object and is used for querying and filtering the big object data. Each big object requires an index.
Custom Field Attributes: A custom field has different attributes depending on its field type.
Geolocation Custom Field: The geolocation custom field allows you to identify locations by their latitude and longitude and to calculate distances between locations.
Considerations for AI Prediction Fields: When you use Einstein Prediction Builder to build a prediction, a custom field is created for storing and displaying the prediction scores on records. Or, you can create a predictive custom field manually, and enter its name and label when building a prediction in Einstein Prediction Builder.
Considerations for the Time Custom Field Type: Track time, unbound to a date, with the Time custom field type, which is useful for time management, event planning, and project management.
Custom Field Types: Salesforce supports various field types, allowing you to select the right one for your data. You can also convert an existing field to a different data type if needed.. When you have data that doesn’t match any of the standard fields, your admin can create a custom field for that data. For example, create a Middle Name field for contacts to capture additional information.
Manage Big Objects: A big object stores and manages massive amounts of data on the Salesforce platform. You can archive data from other objects or bring datasets from outside systems into a big object to get a full view of your customers. From Setup, you can create a custom big object and define its fields and index.
Big Object Definition Details: When you create a custom big object, several required fields define how you can access the big object.
Custom Link Best Practices: Custom buttons and links can streamline actions within Salesforce, or integrate Salesforce data with external URLs, applications, or systems. Use these tips to get the most out of your custom links.
Custom Link Example: Link to Reports: Use custom links to run reports with filtered results from a Salesforce record detail page. For example, let’s say you frequently run a mailing list report for the contacts related to an account. You can create a custom link for accounts that links directly to a report that is automatically filtered to the account that you’re viewing. In this case, your custom link must pass the account’s unique record ID to the report.
Create Custom Permissions: Create custom permissions to give users access to custom processes or apps.
Custom Permissions: Use custom permissions to give users access to custom processes or apps.
Add or Remove Required Custom Permissions: A required custom permission is a custom permission that must be enabled when the parent custom permission is enabled. For example, you could have a custom permission “Approve Time-Off Requests” and specify that it requires the custom permission “Submit Time-Off Requests.”
Custom Tabs: Custom tabs let you display custom object data or other web content in Salesforce. When you add a custom tab to an app in Salesforce Classic, it appears as a tab. When you add a custom tab to an app in Lightning Experience, it appears as an item in the app’s navigation bar and in the App Launcher.
Add a Custom URL: To specify the site to load when users access your custom domain, add a custom URL. Optionally, you can define additional relationships between your domains and sites by mapping paths for your domain to your sites.
Use the Convert External User Access Wizard: In production orgs created before February 8, 2024 that enabled digital experiences before the “Enable Secure Roles Behavior and Update Sharing Group References in Production” release update was enforced Winter ’26, records that were previously accessible to Roles and Subordinates became available to Roles, Internal and Portal Subordinates. You can use the Convert External User Access wizard to not share records or folders with external users.
Custom Help Content: Tailor help so that users understand how to work within your unique implementation of Salesforce. You can add learning in the flow of work in several ways. Add custom help for a page, app, object, or org level, or provide links to help in the Utility Bar, Path, or as a text box on the page. Show users custom resources in a Lightning Experience welcome mat when they first log in. Or, to reach users with important news, training, and on-boarding information, add micro-learning prompts and walkthroughs to your app.
Custom Help in Salesforce Classic: In Salesforce Classic, object-level help replaces the links for a custom object or external object page. Replace built-in Salesforce Help with documentation that’s customized for your users.
Define Field-Level Help: Define custom help text for your organization’s fields to provide users with a helpful description. Help text can be defined for standard and custom fields on all detail and edit pages where the field displays. Users can view the field-level help text by hovering over the Info icon next to the field.
Define Object-Level Help in Salesforce Classic: Object-level help overrides the Help for this Page links for a custom object or external object with your own help content contained in a Visualforce page. To make object-level help available to all your users, create a Visualforce page that contains your help content. Then edit the custom or external object definition to reference the page. Object-level help becomes available to all your users instantly.
Field-Level Help: Field-level help lets you provide help text detailing the purpose and function of any standard or custom field. Before defining field-level help, review these implementation tips and best practices.
Object-Level Help in Salesforce Classic: Help your users by providing object-level help for all custom objects and external objects. This way, when your users click the Help for this Page link on your custom object, they’ll find useful information that’s relevant to your custom object. When you add custom help to a custom or external object, the Help for this Page link on those object pages displays your custom help instead of generic help. Your users can access the custom help content from the object home (overview), detail, and edit pages, list views, and related lists.
Custom Help in Lightning Experience: In Lightning Experience, In-App Guidance allows you to add prompts and walkthroughs to reach users directly with feature updates, record help, and onboarding tips. When Sales Programs, Guidance Sets, or Learning Paths are in use, the Guidance Center icon appears in the global header. Open it to find learning items assigned with Learning Paths and suggestions from Salesforce. All Trailhead modules and custom help assignments can be found on Learning Home.
In-App Guidance in Lightning Experience: Help users discover your products and services, adopt your processes, or learn how to use a new feature. Create prompts and walkthroughs in Lightning Experience apps or pages.
Turn Off Learning Paths: Optionally, you can turn off Learning Paths, which hides the Learning Home and prevents admins from assigning learning items to users. When Learning Paths is turned off, the Guidance Center icon remains available if Sales Programs or Guidance Sets are in use. If neither is in use, the icon is hidden.
Learning Paths Best Practices: Learn how to define an in-app help strategy, and get tips for customizing Learning Paths.
Learning Paths: Create a personalized and always-available learning experience for your users. When you customize Learning Paths, you can choose whom to assign a learning item to—individuals, public groups, or all users. The Guidance Center icon in the global header opens a panel where users can see suggestions from Salesforce and your Learning Paths assignments. Associate the learning item with a particular app or page, and optionally apply a due date. Choose modules from Trailhead or an enablement site (myTrailhead), and add links to other training resources for the ultimate custom training experience. Admins can let other stakeholders, such as trainers or sales team managers, assign and manage learning items.
Monitor Learning Paths (Beta): Use custom reports and dashboards to track user engagement with Learning Paths, Trailhead, and enablement sites (myTrailhead).
Assign a Learning Item for Learning Paths: You can assign a Trailhead or enablement site (myTrailhead) module or a custom learning item such as a video, tutorial, or reference guide. You can assign a learning item to individuals, public groups, or all users. And you can associate a learning item with an app and a particular object and page within the app.
Turn Off Suggested Content in the Guidance Center: Optionally, you can turn off Salesforce suggestions for content in the Guidance Center for end users. Suggested content still appears for admins. Turning off suggestions leaves the Guidance Center icon in place when Sales Programs, Guidance Sets, or Learning Paths are in use, so you can still assign specific learning items with Learning Paths.
Customize the Help Menu in Lightning Experience: The question mark icon in the global header opens a menu of Salesforce resources. Supplement these links by adding a global section with links to your own content. There’s only one custom Help Menu section per org and it appears at the top of the Help Menu.
App Setup Overview: The App Setup and Build pages list optional tasks to customize Salesforce, and build, customize, and manage applications.
Automated Actions: An automated action is a reusable component that performs some sort of action behind the scenes—like updating a field or sending an email. After you create an automated action, add it to a process, milestone, or other automated process.
Considerations for Automated Actions: Before you start working with automated actions, familiarize yourself with relevant limits and special behaviors.
What Is a Cross-Object Formula?: A Cross-object formula is a formula that spans two related objects and references merge fields on those objects. A cross-object formula can reference merge fields from a master (“parent”) object if an object is on the detail side of a master-detail relationship. A cross-object formula also works with lookup relationships.
Custom Buttons and Links: Custom buttons and links help you integrate Salesforce data with external URLs, applications, your company’s intranet, or other internal office systems.
What Determines Field Access?: Several factors control whether users can view and edit specific fields in Salesforce. You can control users’ access to fields at the record type, user, or field level.
Customize Fields: Customize standard and custom fields to tailor your org to your own unique requirements.
Change the Data Type of a Custom Field: You can modify the data type of a custom field. For example, you can change a field from Text to Text Area (Long).
Formula Best Practices: You can use the Formula Editor in Salesforce to construct a simple formula with a few clicks. But what if you want to build something more complex? Use these tips to help you map out formula logic and make it easier to troubleshoot errors.
Calculate Field Values with Formulas: A formula is an algorithm that derives its value from other fields, expressions, or values. Formulas can help you automatically calculate the value of a field based on other fields.
Formula Operators and Functions by Context: Use these operators and functions when building formulas. All functions are available everywhere that you can include a formula, such as formula fields, validation rules, approval processes, and workflow rules, unless otherwise specified.
ABS: Calculates the absolute value of a number. The absolute value of a number is the number without its positive or negative sign.
ADDMONTHS: Returns the date that is the indicated number of months before or after a specified date. If the specified date is the last day of the month, the resulting date is the last day of the resulting month. Otherwise, the result has the same date component as the specified date.
&& (AND): Evaluates if two values or expressions are both true. Use this operator as an alternative to the logical function AND.
AND: Returns a TRUE response if all values are true; returns a FALSE response if one or more values are false.
= and == (Equal): Evaluates if two values are equivalent. The = and == operators are interchangeable.
BEGINS: Determines if text begins with specific characters and returns TRUE if it does. Returns FALSE if it doesn't.
BLANKVALUE: Determines if an expression has a value and returns a substitute expression if it doesn’t. If the expression has a value, returns the value of the expression.
CASE: Checks a given expression against a series of values. If the expression is equal to a value, returns the corresponding result. If it isn't equal to any of the values, returns the else_result.
CASESAFEID: Converts a 15-character ID to a case-insensitive 18-character ID. In Salesforce Classic, the function converts only valid Salesforce 15-character IDs. If you pass in an invalid ID, the function returns the ID passed in. In Lightning Experience, the function converts any 15-character ID.
CEILING: Rounds a number up to the nearest integer, away from zero if negative.
CONTAINS: Compares two arguments of text and returns TRUE if the first argument contains the second argument. If not, returns FALSE.
CURRENCYRATE: Returns the conversion rate to the corporate currency for the given currency ISO code. If the currency is invalid, returns 1.0.
DATE: Returns a date value from the year, month, and day values you enter. Salesforce displays an error on the detail page if the value of the DATE function in a formula field is an invalid date, such as February 29 in a non-leap year.
DATETIMEVALUE: Returns a year, month, day, and GMT time value.
DATEVALUE: Returns a date value for a date/time or text expression.
DAY: Returns a day of the month in the form of a number from 1 through 31.
DISTANCE: Calculates the distance between two locations in miles or kilometers.
> (Greater Than): Evaluates if a value is greater than the value that follows this symbol.
>= (Greater Than or Equal): Evaluates if a value is greater than or equal to the value that follows this symbol.
HOUR: Returns the local time hour value without the date in the form of a number from 1 through 24.
HTMLENCODE: Encodes text and merge field values for use in HTML by replacing characters that are reserved in HTML, such as the greater-than sign (>), with HTML entity equivalents, such as >.
HYPERLINK: Creates a link to a URL specified that is linkable from the text specified.
IF: Determines if expressions are true or false. Returns a given value if true and another value if false.
IMAGE: Inserts an image with alternate text and height and width specifications.
IMAGEPROXYURL: Securely retrieves external images and prevents unauthorized requests for user credentials.
INCLUDE: Returns content from an s-control snippet. Use this function to reuse common code in many s-controls.
INCLUDES: Determines if any value selected in a multi-select picklist field equals a text literal you specify.
ISBLANK: Determines if an expression has a value and returns TRUE if it does not. If it contains a value, this function returns FALSE.
ISCHANGED: Compares the value of a field to the previous value and returns TRUE if the values are different. If the values are the same, this function returns FALSE.
ISCLONE: Checks if the record is a clone of another record and returns TRUE if one item is a clone. Otherwise, returns FALSE.
ISNEW: Checks if the formula is running during the creation of a new record and returns TRUE if it is. If an existing record is being updated, this function returns FALSE.
ISNULL: Determines if an expression is null (blank) and returns TRUE if it is. If it contains a value, this function returns FALSE.
ISNUMBER: Determines if a text value is a number and returns TRUE if it is. Otherwise, returns FALSE.
ISPICKVAL: Determines if the value of a picklist field is equal to a text literal you specify.
JSENCODE: Encodes text and merge field values for use in JavaScript by inserting escape characters, such as a backslash (\), before unsafe JavaScript characters, such as the apostrophe (').
JSINHTMLENCODE: Encodes text and merge field values for use in JavaScript inside HTML tags by replacing characters that are reserved in HTML with HTML entity equivalents and inserting escape characters before unsafe JavaScript characters.
JUNCTIONIDLIST: Returns a JunctionIDList based on the provided IDs.
LEFT: Returns the specified number of characters from the beginning of a text string.
LEN: Returns the number of characters in a specified text string.
< (Less Than): Evaluates if a value is less than the value that follows this symbol.
<= (Less Than or Equal): Evaluates if a value is less than or equal to the value that follows this symbol.
LINKTO: Returns a relative URL in the form of a link (href and anchor tags) for a custom s-control or Salesforce page.
LN: Returns the natural logarithm of a specified number. Natural logarithms are based on the constant e value of 2.71828182845904.
LOWER: Converts all letters in the specified text string to lowercase. Any characters that are not letters are unaffected by this function. Locale rules are applied if a locale is provided.
LPAD: Inserts characters you specify to the left-side of a text string.
MAX: Returns the highest number from a list of numbers.
MCEILING: Rounds a number up to the nearest integer, towards zero if negative.
MFLOOR: Rounds a number down to the nearest integer, away from zero if negative.
MID: Returns the specified number of characters from the middle of a text string given the starting position.
MILLISECOND: Returns a milliseconds value in the form of a number from 0 through 999.
MIN: Returns the lowest number from a list of numbers.
MINUTE: Returns a minute value in the form of a number from 0 through 60.
MOD: Returns a remainder after a number is divided by a specified divisor.
MONTH: Returns the month, a number from 1 (January) through 12 (December) in number format of a given date.
NOW: Returns a date/time representing the current moment.
NULLVALUE: Determines if an expression is null (blank) and returns a substitute expression if it is. If the expression is not blank, returns value of the expression.
() (Open Parenthesis and Close Parenthesis): Specifies that the expressions within the open parenthesis and close parenthesis are evaluated first. All other expressions are evaluated using standard operator precedence.
|| (OR): Evaluates if at least one of multiple values or expressions is true. Use this operator as an alternative to the logical function OR.
OR: Determines if expressions are true or false. Returns TRUE if any expression is true. Returns FALSE if all expressions are false.
All Formula Operators and Functions: Use operators and functions when building formulas. All functions are available everywhere that you can include a formula such as formula fields, validation rules, approval processes, and workflow rules, unless otherwise specified.
PARENTGROUPVAL: This function returns the value of a specified parent grouping. A “parent” grouping is any level above the one containing the formula.
PREDICT: Returns an Einstein Discovery prediction for a record based on the specified record ID or for a list of fields and their values.
PREVGROUPVAL: This function returns the value of a specified previous grouping. A “previous” grouping is one that comes before the current grouping in the report.
PRIORVALUE: Returns the previous value of a field.
REGEX: Compares a text field to a regular expression and returns TRUE if there is a match. Otherwise, returns FALSE.
REQUIRESCRIPT: Returns a script tag with URL source that you specify. Use this function when referencing the Lightning Platform AJAX Toolkit or other JavaScript toolkits.
REVERSE: Returns the characters of a source text string in reverse order.
RIGHT: Returns the specified number of characters from the end of a text string.
ROUND: Returns the nearest number to a number you specify, constraining the new number by a specified number of digits.
RPAD: Inserts characters that you specify to the right-side of a text string.
SECOND: Returns a seconds value in the form of a number from 0 through 60.
SQRT: Returns the positive square root of a given number.
SUBSTITUTE: Substitutes new text for old text in a text string.
- (Subtract): Calculates the difference of two values.
TEXT: Converts a percent, number, date, date/time, or currency type field into text anywhere formulas are used. Also, converts picklist values to text in approval rules, approval step rules, workflow rules, escalation rules, assignment rules, auto-response rules, validation rules, formula fields, field updates, and custom buttons and links.
TIMENOW: Returns a time value in GMT representing the current moment. Use this function instead of the NOW function if you only want to track time, without a date.
TIMEVALUE: Returns the time value without the date, such as business hours.
TODAY: Returns the current date as a date data type.
TRIM: Removes the spaces and tabs from the beginning and end of a text string.
UPPER: Converts all letters in the specified text string to uppercase.
URLENCODE: Encodes text and merge field values for use in URLs by replacing characters that are illegal in URLs, such as blank spaces, with the code that represent those characters as defined in RFC 3986, Uniform Resource Identifier (URI): Generic Syntax.
URLFOR: Returns a URL for an action, an s-control, a Visualforce page, or a file in a static resource archive. URLFOR is available for use in custom buttons and links, s-controls, and Visualforce pages.
VLOOKUP: Returns a value by looking up a related value on a custom object similar to the VLOOKUP() Excel function. This function is only available in validation rules.
WEEKDAY: Returns the day of the week for the given date, using 1 for Sunday, 2 for Monday, through 7 for Saturday.
YEAR: Returns the four-digit year in number format of a given date.
Salesforce Classic Home Tab Page Layouts: You can customize the Home tab in Salesforce Classic to include components such as sidebar links, a company logo, a dashboard snapshot, or custom components that you create. A dashboard snapshot is a clipping of the top row of a dashboard’s components. Just like other tabs, you can also assign different home page layouts to different users based on profile.
Page Layouts: Page layouts control the layout and organization of buttons, fields, s-controls, Visualforce, custom links, and related lists on object record pages. They also help determine which fields are visible, read only, and required. Use page layouts to customize the content of record pages for your users.
Create Page Layouts: With the enhanced page layout editor, you can tailor record page layouts to the needs of your users.
The Enhanced Page Layout Editor: The enhanced page layout editor is a tool for customizing your page layouts in Salesforce, the Self-Service Portal, and the Salesforce Customer Portal. The enhanced page layout editor has all the functionality of the original page layout editor, but has more features and an easier-to-use interface.
User Interface Elements for the Enhanced Page Layout Editor: This list describes the enhanced page layout editor user interface elements and how you can use them in your page layout. To add elements, drag them from the palette to the layout. Valid drop locations show up in green. To remove elements, drag them off the layout and back to the palette.
Ways to Control User Access to Fields: Use field-level security to control user access to fields. Use page layouts to control the layout and organization of detail and edit pages in Salesforce, the Self-Service Portal, and the Salesforce Customer Portal.
Lightning App Navigation Bar Items: Most of the items that appear in the App Launcher can appear in a Lightning app navigation bar. To add items to an app’s navigation bar, you can use the Lightning app creation wizard, which lets you choose from a list of available items.
Customize Your Salesforce Org: You can customize each of the standard tabs and types of records, including adding custom fields and setting page layouts. You can also customize search, tagging, and user interface options for your org. In addition, every Contact Manager, Group, Professional, Enterprise, Unlimited, and Performance Edition user can customize various personal display options.
Managing Multiple Business Processes: Use multiple business processes to display different picklist values according to each user’s profile. Use multiple business processes to track separate sales, support, and lead lifecycles.
Select Which Fields Appear in the Recently Viewed List: As a Salesforce admin, you can customize the Recently Viewed list that appears on the Setup home page for most standard and custom objects. Choose and order the fields to display so that your users see the information that’s most important for your company.
Tailor Business Processes to Different Record Types Users: Record types let you offer different business processes, picklist values, and page layouts to different users. You can create record types to differentiate your regular sales deals from your professional services engagements, offering different picklist values for each. Or you can display different page layouts for your customer support cases versus your billing cases.
Rename Object, Tab, and Field Labels: You can change the name of almost any object, field, or tab in Salesforce. This simple adjustment lets you continue using the terminology your users already know and helps them transition to using Salesforce. However, Salesforce Help and most pages in Setup always display the original names for standard objects, fields, and tabs.
Replace a Picklist Value: As your business changes, replace picklist values with more relevant alternatives. Replacing a value globally replaces that field value on all existing records.
Sort Picklists: You can arrange picklist values in a specific order or sort them alphabetically.
Standard Object Limits: Standard object limits include usage details for object customizations, such as the custom fields you’ve added or sharing rules you’ve applied to an object.
Customize Standard Fields: You can customize several aspects of standard fields, such as the values in picklists, the format for auto-number fields, tracking field history, lookup filters on relationship fields, and field-level help.
Adding Tags to the Sidebar: When you enable tags for your organization, you can add the Tags component to your users' sidebar.
Delete Personal Tags for Deactivated Users: Your org can have up to 5,000,000 personal and public tags applied to records across all users. If your org is approaching this limit, delete personal tags for deactivated users.
Enable Tags: Allow users to add personal or public tags to most records. Tags are words or short phrases that users associate to records to describe and organize data in a personalized way.
Topics and Tags Settings: Topics on objects allow users to add topics to records so they can organize them by common themes. With Chatter enabled, users can also see related posts and comments. Enabling topics for an object disables public tags on records of that object type. Personal tags aren’t affected.
Enable or Disable Translation Workbench: Translation Workbench allows you to specify languages for translation, assign translators, and manage your translations through the workbench or bulk translation.
Workflow Rules: Workflow rules are a legacy automation feature that let you define conditions and actions for records in your org. Support ended on December 31, 2025. Use Flow Builder for new automations and migrate existing rules as needed.
Email Alert Actions: An email alert is an email generated by an automated process and sent to the designated recipients. The action consists of the standard text and the list of recipients. You can use an email alert in an automation, such as a flow, approval process, or entitlement process. Legacy workflow rules and processes built in Process Builder or through the Invocable Actions REST API endpoint also use email alerts.
Task Actions: Task actions determine the details of an assignment given to a specified user by an automated process. You can associate task actions with workflow rules, approval processes, or entitlement processes.
Add Actions to Global Publisher Layouts: Actions you add to the global publisher layouts appear on pages such as the Home and Chatter pages. They also appear on the action bar and action menu on the Feed and People pages in the Salesforce mobile app.
Customize Related Lists: You can customize related lists on record detail pages in Salesforce and the Salesforce Customer Portal. Configure elements such as the buttons and columns, the column order, and the record sort order.
Custom Metadata Type Validation Rules: Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record. A validation rule can contain a formula or expression that evaluates the data in one or more fields and returns a value of “True” or “False”. Validation rules also include an error message to display to the user when the rule returns a value of “True” due to an invalid value.
What are Custom Metadata Types?: Custom metadata is customizable, deployable, packageable, and upgradeable application metadata. First you create a custom metadata type, which defines the form of the application metadata. Then you build reusable functionality that determines the behavior based on metadata of that type.
Create and Manage Custom Metadata Types Using CLI Commands: You can use the Salesforce command-line interface (CLI) to create custom metadata types, generate fields, create records, create records from a CSV file, and generate custom metadata types from an sObject.
Reference Custom Metadata Type Records in Default Values: Default field values make your users more productive and decrease errors by reducing the number of fields to fill in manually. Reference a custom metadata type record in a default value. If a default field value changes, you can update it in the custom metadata type instead of updating multiple field references.
Custom Metadata Type Fields: Similar to a custom object or custom setting, a custom metadata type has a list of custom fields that represent aspects of the metadata.
Custom Metadata Types and Advanced Formula Fields: When you create a custom metadata type, you can reference its values in an advanced formula field. If a field value changes, you can update it in the custom metadata type instead of changing multiple, hard-coded formulas. If you use packaging, define the logic you want and allow your subscribers to customize the details.
Custom Metadata Types: You can create your own declarative developer frameworks for internal teams, partners, and customers. Rather than building apps from data, you can build apps that are defined and driven by their own types of metadata. Metadata is the information that describes the configuration of each customer’s organization.
Package Custom Metadata Types and Records: You can package custom metadata types and records in unmanaged packages, managed packages, or managed package extensions. Your packages can then be installed in Professional, Developer, Enterprise, Performance, Unlimited, and Database.com Edition organizations.
Control Read Access to Custom Metadata Types: Admins with the Customize Application permission can grant Read access to specific custom metadata types through profiles and permission sets.
Custom Metadata Types and Process Builder: Reference custom metadata type records from a Process Builder formula to automate your business processes, reusing functionality that you define. To change a value, you can update it in the custom metadata type instead of in your process and any hard-coded formulas that your process uses.
View Filtering on Metadata Relationship Fields: When you create a view and filter on a relationship field of a custom metadata type, use these guidelines for entering the filter values.
Custom Metadata Relationships: Create relationships between custom metadata types, entity definitions, field definitions, or entity particles. Use relationships rather than text fields to directly reference objects, simplify your Apex code, and enforce referential integrity, for example, when packaging custom metadata types.
Custom Metadata Types and Validation Rule Formulas: Use custom metadata records to store validation rule record values. Then, reference the records directly within validation rules and eliminate the need to add the same values into different validation rules. Using packaging? You can define the logic and leave customization to a subscriber.
Remove Pending Approval Requests for Classic Approval Processes: If you want to clean up old approval requests—such as to delete a classic approval process—remove them from your Salesforce org. After approval requests are removed, the associated records are unlocked and removed from all classic approval processes, so they no longer appear on the approver’s list of pending approval requests.
Data Classification Metadata Fields: Record the data owner, field usage, data sensitivity, and compliance categorization for any standard or custom object field. You can also access data classification metadata in the Salesforce API and Apex.
Set Up Data Classification Metadata: Customize your data classification settings to meet your organization’s needs. You can also upload or download data classification values.
Protect Sensitive Data with Data Mask & Seed: Protect sensitive information in your sandboxes by replacing personally identifiable information (PII) with realistic synthetic data.
Edit Existing Custom Libraries: Add values or remove values used to mask text or email fields in a masking policy from custom libraries.
Manually Add Values to a Custom Library: Use this procedure when you want to individually add a relatively small number of typical or standard values to a custom library. For example, for QA of sandbox masking you only need a library containing 15 female first names.
Generate and Add Values to a Custom Library with Einstein: Use this procedure when you want to generate and add to a custom library a large number of values of a specific or unique type. For example, for your QA of sandbox masking you need to generate a custom library containing 100 cities having a population of over 5 million.
Define New Custom Libraries: Create new custom libraries to add values to use to mask text or email fields in a masking policy.
Create a Masking Policy: Here’s how to create an initial masking policy to begin addressing your masking use case needs.
Custom Libraries Overview: Custom libraries are user-defined collections of values that you can use to mask text or email fields in a masking policy.
Custom Libraries Tab: Use the Custom Libraries tab to view, create, edit, activate, and delete custom libraries for masking policies.
Delete Values from a Custom Library: Use this procedure when you want to delete values from a custom library that are no longer necessary for or relevant to your development or QA work.
Filter Object Records for Masking: Add object filters in masking policies in order that masking job processing selects for masking only the specific object records that meet your use case criteria, such as accounts in a particular region or contacts created after a specific date.
Data Mask & Seed Home Tab: The Data Mask & Seed Home page provides descriptions of the application’s features and the UI utilities for beginning your work with the Data Mask & Seed application.
Monitor Masking Jobs from the Jobs Tab: Access the Data Mask & Seed Jobs tab to monitor running and completed masking jobs, view job details, and cancel jobs in progress. The Jobs tab is only available in sandboxes.
Data Mask & Seed Policies Tab: Use the Policies tab to create, view, edit, and delete masking policies for your org.
Data Mask & Seed Requirements and Limitations: This topic provides the requirements and limitations that govern working with Data Mask & Seed. Before working with Data Mask & Seed, review these requirements and limitations.
Run a Masking Job: After creating a policy in your sandbox that addresses your masking use case needs, you can then manually run a masking job using that policy to mask your sandbox’s object data.
Scheduled Masking Policies: After creating a policy in your sandbox that addresses your masking use case needs, you can then schedule masking jobs to be automatically run using that policy to mask your sandbox’s object data.
Data Mask Considerations: When running Data Mask in your sandbox, it’s important to understand how rules and records are handled.
Create Custom Libraries: Create a custom library that’s separate from the predefined Data Mask libraries. Custom libraries can contain any string value, such as long text, integers, and non-English characters.
Create or Edit a Data Mask Configuration: You can configure the masking process in one of two ways. Configure it in production, then when a sandbox is created or refreshed, the configuration appears in the sandbox. Or, configure the masking process in an existing sandbox.
Install the Managed Package in a Production Org: Data Mask is a managed package that you install in your production org. You can run the masking process from any new sandbox created from the production org. To install and use Data Mask, you must enable certain features in your production org and specify user permissions. After you install the package, Salesforce automatically upgrades it with new features and bug fixes. Data Mask currently supports API version 50.0.
Run a Data Mask Job: While the Data Mask package can be installed and configured in your production org, data masking jobs only run in sandbox orgs. That way, the data in the production org isn’t accidentally masked. When the configuration is complete, you can mask your sandbox data. Run the mask each time you want to replace or delete the data in your sandbox. Or, set the mask to automatically run each time you refresh your sandbox.
Data Mask Best Practices: We recommend that you mask fields that typically contain personally identifiable information (PII) or other sensitive data. These fields are a good place to start.
Set Filter Criteria: Target specific data records for masking to meet business requirements and security goals.
Schedule Data Mask Jobs: Decide whether to set a scheduled start with a repeating frequency or continue to run your mask with the manual default.
Understand How Different Masking Types Work: Data Mask uses different levels or types of masking to help keep your sensitive production data private in a sandbox. For example, you can replace sensitive data in your sandboxes with random characters or similarly mapped words, or eliminate it.
Add Configuration Security by Using Named Credentials: If your organization requires heightened security when making configuration changes, enhance your Data Mask configuration security. Use a named credential with an Auth provider and a connected app to provide a secure connection to the Salesforce Metadata API. This feature is available in Data Mask version 4.2 and later.
Sandbox Access Considerations: Review some important considerations about access before you create a sandbox so that sandbox users can make full use of the sandbox environment for development and UAT testing.
Clone a Sandbox: When you clone a sandbox, its data and metadata are copied to the new sandbox. If included in the source sandbox, entity history and Chatter are copied for only Full sandboxes. A cloned sandbox uses the same license type as its source org. For example, to clone a Full sandbox you must have a Full sandbox license available.
Sandbox Cloning: You can create a sandbox by cloning an existing sandbox rather than using your production org as your source. Save time by customizing a sandbox with a set of data and metadata and then replicating it. Sandbox cloning simplifies having multiple concurrent streams of work in your application life cycle. You can set up a sandbox for each type of work, such as development, testing, and staging. Your colleagues can easily clone individual sandboxes instead of sharing one sandbox and avoid stepping on each other’s toes.
Configuring Full Sandboxes: When you create or refresh a full sandbox, you can configure it to determine what data is copied. Minimizing the amount of data you include speeds up your sandbox copy.
Create a Sandbox: When you create a sandbox, Salesforce copies the metadata from your production org to a sandbox org. What data gets copied depends on the sandbox type.
Create, Clone, or Refresh a Sandbox: Create a sandbox to use for development, testing, and training. Clone a sandbox to copy its data and metadata into another sandbox. Refresh an existing sandbox to update its contents.
Some Considerations: Review these considerations when you create, refresh, or delete a sandbox.
Customization and Data Changes: Customizations and data changes in your production org aren’t reflected in your sandboxes.
Email Deliverability: New and refreshed sandboxes use the System email only setting by default. Sandboxes created before Spring ’13 default to All email.
Enable Source Tracking in Sandboxes: By enabling source tracking in Developer and Developer Pro sandboxes, Salesforce DX tooling can automatically track new, changed, and deleted metadata components. You can then select and determine which changes to move forward in the development cycle and release. For DX tooling that uses a Salesforce DX project or source control repository, source tracking can aid in conflict detection and resolution. And best of all, because source tracking identifies which metadata components changed, you no longer have to manually keep track of changes.
Sandbox Licenses and Storage Limits by Type: A sandbox is a copy of your organization in a separate environment that you can use for a variety of purposes, such as testing and training. Sandboxes are completely isolated from your Salesforce production organization. The operations you perform in your sandboxes don’t affect your Salesforce production organization. You can create different sandbox environments for your org, depending on your needs for storage, copy configuration, and frequency of refresh.
Sandbox Setup Considerations: Sandbox behavior is similar to a Salesforce production org, but important differences affect how you configure and test a sandbox org.
Inactive Sandbox Expiration: To better utilize capacity and support growth, we perform a routine cleanup of inactive sandboxes. A sandbox is considered inactive and eligible for deletion if it hasn’t been accessed for 180 days.
Inactive User Freezing: Users who haven’t logged in to a Developer or Developer Pro sandbox within the first 60 days based on the time the user was created are frozen. This feature can’t be disabled.
Sandbox License Compliance: When you exceed your sandbox allocations, we lock the appropriate number of sandboxes to restore your license compliance, starting with the least recently used sandboxes. After you meet compliance, locked sandboxes are unlocked.
Unlock a Sandbox: Sandboxes are licensed separately from the Salesforce service and are subject to restrictions. When your sandbox licenses expire, Salesforce decreases the count of available sandbox licenses for the selected sandbox type.
Manage Your Sandboxes: In Setup, enter Sandboxes in the Quick Find box, then select Sandboxes. Sandboxes displays the available sandboxes that you purchased and a list of your sandboxes in use.
Multi-Factor Authentication: Sandbox environments aren’t contractually required to use multi-factor authentication (MFA). But we strongly recommend using MFA for sandboxes that include intellectual property, customer data, or other Salesforce production data. To develop a strategy for managing MFA in sandbox environments, review these considerations.
Monitor Your Sandbox’s Progress: From Setup, enter Sandboxes in the Quick Find box, then select Sandboxes. The list displays all your sandboxes. Select a sandbox to view details about its copy or refresh progress.
Other Service Differences: Sandbox behavior is similar to a Salesforce production org, but important differences affect how you configure and test a sandbox org.
What are Preview and Non-Preview Sandboxes?: During the Salesforce major release transitions, sandboxes get upgraded on different timelines based on their release type. The two release types for sandboxes are preview and non-preview.
Product and Service Exclusions: Some products and services are enabled in production orgs and disabled by default in sandboxes. Some can be re-enabled, while others cannot.
Refresh Your Sandbox: Refreshing a sandbox updates its metadata from the source org. If the sandbox is a clone or if it uses a sandbox template, the refresh process updates the org’s data and its metadata. The org ID of the sandbox changes each time it’s refreshed.
Activate Your Refreshed Sandbox: If you didn’t select Auto Activate while refreshing your sandbox, you must activate your sandbox before you can use it.
Refresh a Cloned Sandbox: Refreshing a cloned sandbox updates the sandbox’s metadata and data from its source org. The org ID of the sandbox changes each time it’s refreshed.
Determine Who Has Sandbox Access: Selective Sandbox Access helps you limit access to only required users who are included in a public group. It also removes the additional step for a Salesforce admin to change user email addresses back to their original format.
Servers and IDs: Sandbox and production orgs have unique org IDs. The sandbox copy engine creates an org as part of each creation and refresh request.
Sandbox Action and Status Reference: Access the list of your sandboxes from the Sandbox Setup page. Each entry shows the status of the sandbox and the actions that you can take.
Sandbox Data Storage Upgrades: Upgrade the data storage of new or existing Developer or Developer Pro sandboxes, which supports developing and testing with larger data sets.
Sandbox Login Troubleshooting: Learn how to troubleshoot the most common reasons why users can’t log in to a sandbox.
Data Translation: When data translation is enabled, the data stored in certain objects and fields are available for translation. You can also enable data translation for custom text and URL fields on objects.
Enable Data Translation for Custom Fields: Allow translation of data stored in custom fields on certain objects and fields. You can enable data translation on custom fields with a type of Text, Text Area, Text Area (Long), Text Area (Rich), and URL.
Fields in Data Use Purpose Records: Represents a category that defines the reason for contacting an individual. For example, billing, marketing, or surveys.
Delete Users: While you can’t completely delete a user, you can deactivate a user’s account so they can’t log in to Salesforce.
Debug Your Code: Use checkpoints, logs, and the View State tab to help debug the code you’ve written.
Default Action Fields: Each default action includes a pre-defined set of fields, which lets you make actions available to your users without spending much time on setup.
Default Actions: Default actions are sets of predefined actions to get you and your users started using actions in your org. Add default actions to publisher layouts to make them available to your users in the full Salesforce site and the action bar in the Salesforce mobile app.
Define Custom Buttons and Links: Define the action that occurs when a user clicks a custom button or link. Custom buttons and links can streamline actions within Salesforce or integrate Salesforce data with external URLs, applications, or systems.
Custom Button and Link Fields: This table describes the fields that are available when you create a custom button or link.
Define Delegate Administrators: Enable delegated administrators to manage users in specified roles and all subordinate roles. You can assign specified profiles to those users, and log in as users who have granted login access to administrators. A delegated administration group is a group of users who have the same admin privileges. These groups are not related to public groups used for sharing.
Delete Custom S-Controls: S-controls provide a flexible, open means of extending the Salesforce user interface, including the ability to create and display your own custom data forms.
Delete a Custom Field: Custom fields can be deleted as long as they meet certain requirements.
Deployment Best Practices: Keeping your live Salesforce environment (production org) running smoothly is critical for maintaining customer trust. How do you do that? By making smart, deliberate choices that follow best practices around governance and change management. A solid deployment strategy ensures that you're introducing changes into your system thoughtfully, which helps you maintain stability and avoid disruptions that can adversely affect your customers or business.
Monitor Deployments: You can monitor deployments that are in progress, check which deployments are waiting for execution, and view the results of completed deployments on the Deployment Status page.
Deploy Your Changes: Migrate metadata changes between Salesforce orgs by using the deployment tools available in Setup.
When to Use a Sandbox: Sandboxes create copies of your Salesforce org in separate environments. Use them for development, testing, and training, without compromising the data and applications in your production org.
Sandboxes: Staging Environments for Customizing and Testing: Want to customize your organization in a staging environment where you can test changes without affecting your production organization or its users? Want to have an organization that users can log into and test new features before they’re production-ready? Or maybe you just want to log into a Salesforce organization for training or development that mirrors your production organization.
Manage Your Sandboxes Programmatically: Use Salesforce CLI to authorize in to, create, and clone sandboxes. Traditionally, admins create and manage sandboxes through the Setup UI. But we realize that many admins and developers want the ability to create and manage their development and testing environments programmatically, and to automate their CI processes. Salesforce CLI enables you to do both.
Special Behavior in Deployments: Use the information here to determine what to include in your deployment and how the changes appear in the destination.
Design Home Page Layouts in Salesforce Classic: After creating the components you want displayed on the Home tab, design your home page layouts. You can design your layouts based on your unique organizational and user needs.
About S-Controls: Use s-controls to add your own functionality to your Salesforce organization. Whether you are integrating a hosted application of your own or are extending your current Salesforce user interface, use s-controls to store your code or refer to code elsewhere. Custom s-controls can contain any type of content that you can display in a browser, for example a Java applet, an Active-X control, an Excel file, or a custom HTML Web form.
Valid Values for the $Action Global Variable: All objects support basic actions, such as new, clone, view, edit, list, and delete. The $Action global also references actions available on many standard objects. The values available in your organization may differ depending on the features you enable.
Delete Custom Objects: When you delete a custom object, Salesforce doesn’t add it to the Recycle Bin. Instead, deleted objects appear in the Deleted Objects list for 15 days. During this time, the object and its data are soft deleted, meaning you can restore or permanently erase (hard delete) the object and its data. After 15 days, the object and its data are automatically hard deleted.
Manage Deleted Custom Objects: Deleted custom objects appear in the Deleted Objects list for 15 days. During this time, you can choose to permanently delete the object and its data, or you can undelete them. If you undelete a custom object, some manual cleanup can be required to restore list views and other customizations that use the object.
Store Information That’s Unique to Your Organization: Create custom objects to store information that’s unique to your organization. Choose whether your custom objects are searchable, support sharing, or include access to the Bulk API and Streaming API.
Truncate Custom Objects: Truncating custom objects allows you to delete all of the object’s records permanently, but preserve the empty object and its metadata.
Create a Custom Object from a Spreadsheet in Lightning Experience: Use custom objects to track and store data that’s unique to your organization. If you prefer not to create a custom object and its fields manually, you can use a spreadsheet to add the object and its fields and populate all its record data.
Create a Custom Object: Track and store data that’s unique to your organization. Follow different steps, depending on which Salesforce experience you’re using.
Manage Custom Objects: Create, customize, edit, delete, or truncate custom objects to extend the functionality that standard objects, like accounts and contacts, provide.
Custom Object Standard Fields: When you create a custom object, these default fields are automatically assigned to the object.
Defining Custom S-Controls: S-controls provide a flexible, open means of extending the Salesforce user interface, including the ability to create and display your own custom data forms.
Global Variables: When you work with components such as custom buttons and links, formulas in custom fields, validation rules, flows, processes, and Visualforce pages, you can use special merge fields to reference data in Salesforce.
Useful S-Controls: Use these samples to get started using s-controls.
Download API WSDL and Client Certificates: To integrate your applications with Salesforce using the API, download a Web Services Description Language (WSDL) document.
Develop and Deploy with DX Inspector: DX Inspector is a management tool that provides quick access to metadata and data change tracking and visualization. It’s available at the top of a page or builder in your Salesforce sandbox, scratch org, or Developer Edition org.
Create an External Client App: External client apps provide single sign-on (SSO) and use OAuth protocols to authorize third-party applications. When you configure the app and assign appropriate permission sets, DevOps Center appears in the App Launcher.
Lifecycle Center Events in Activity History: View a comprehensive timeline of key DevOps events, including commits, promotions, and synchronizations, to audit activity and troubleshoot errors.
Add Development Environments: Add source-tracked development environments for team members in Lifecycle Center. You can add a development environment manually from the pipeline, or automatically when your team members commit changes from DX Inspector.
Add Metadata Manually: The Change Management tab uses source tracking to automatically track metadata files in your org. However, when you require flexibility to include additional metadata files that source tracking hasn’t pulled automatically, you can add metadata manually.
Add a Release Environment: Connect your production org as the release environment in Lifecycle Center. Every project requires one release environment and at least one development environment.
Add Team Members as Users in the DevOps Center Org: Add any team members who aren’t already users in the DevOps Center org. For each team member, specify the appropriate license and profile based on their role.
Add Team Members to the Bitbucket Repo As Collaborators: In Bitbucket, add team members as repository collaborators. A collaborator is someone who has been granted write access to the project repository. Add everyone who creates customizations or code for your project to the project repository as a collaborator. That way, they have access to the repository through DevOps Center.
Add Team Members to the GitHub Repo As Collaborators: In GitHub, add team members as repository collaborators. A collaborator is someone who has been granted write access to the project repository. Add everyone who creates customizations or code for your project to the project repository as a collaborator. That way, they have access to the repository through DevOps Center.
Access Agentforce Vibes Usage with Agentic Development (Developer Preview): To track and analyze Agentforce Vibes data, enable the Agentic Development dashboard. The dashboard aggregates Agentforce Vibes activity from the last 30 days and provides analytics about AI-powered development, developer productivity metrics, and AI model utilization. Admins can filter data and analytics by Org Type or by a specific model.
Lifecycle Center Analytics: Enable the Analytics tab in Lifecycle Center to track and analyze development and productivity metrics. The Analytics tab includes the Agentic Development dashboard, which aggregates Agentforce Vibes activity from the last 30 days and provides analytics about AI-powered code generation, developer productivity, and AI models utilization.
Assign the DevOps Center Permission Sets: Assign permission sets to everyone working on your project in DevOps Center. Consider who must change project-level settings (such as adding another work environment) and who needs access to only work items.
Lifecycle Center Basics: Lifecycle Center (formerly next-generation DevOps Center) uses concepts that may be new to you—pipeline, branches, work items, and source control. Before setup, understand what these are, how they connect, and how Lifecycle Center handles most of the complexity for you.
Source Control in Lifecycle Center: Lifecycle Center uses source control as the single source of truth for your project changes. It keeps your changes outside the org so your team can collaborate in one shared space.
Source Control Branches: A branch is a local copy of your project where you can make changes without affecting anyone else’s work.
Work with Developers: Salesforce admins and developers work on the same org but make changes in different ways. Lifecycle Center provides a shared space for both roles without changing how either works.
Connect the Bitbucket Repo in DevOps Center: Each DevOps Center project has a corresponding project repository. By connecting the Bitbucket repo to DevOps Center, DevOps Center can interact with the repo to perform operations such as creating feature branches, creating change requests, and committing and merging changes to each pipeline branch (stage).
Create a Bitbucket Project (Beta): After you connect the Bitbucket repository in DevOps Center, create the DevOps Center project associated with this source code repository to help you and your team manage changes for a particular application or customization.
Build Your Pipeline: Define the sequence of stages for your release lifecycle by building a pipeline in Lifecycle Center.
(Optional) Install Salesforce CLI DevOps Center Plugin (Beta): Install the Salesforce CLI DevOps Center plugin to perform DevOps Center actions on the command line for developers who plan to work outside of DevOps Center or want to automate tasks. We plan to roll out new commands over time. The first set of commands support the ability to deploy changes to a pipeline environment and perform a validate-only deployment.
Quick Start: Use Salesforce CLI with Lifecycle Center: Use Salesforce CLI to automate Lifecycle Center tasks from the command line. In this quick start, you create and activate a pipeline, manage a work item, and promote changes to the next pipeline stage.
Combine Work Items in Lifecycle Center: Use combine work items to prevent conflicts when promoting individual work items with custom promotion. When work items in a stage share metadata or depend on each other, promoting them individually results in conflicts or blocked promotions.
Commit Changes to Source Repository: Commit changes to your source repository directly from the Change Management tab. After you make the changes, decide which changes to include for the work item and commit them to the Lifecycle Center project’s source control repository.
Stalled Commits: A stalled commit can occur when the updates from the external services back to DevOps Center are interrupted during the commit operation. After you determine when the failure occurred, you can fix it.
Supported Special Characters in Metadata Component Names: When naming metadata components, DevOps Center and its underlying technologies, such as Metadata API and Salesforce CLI, support a subset of special characters. To avoid issues when deploying or promoting metadata to a pipeline stage, we strongly suggest using only supported special characters in your component names.
Set Up DevOps Center for GitHub: To use GitHub with DevOps Center as your source control repository, some tasks are performed within GitHub, such as creating a repository and adding team members. And some tasks are performed in DevOps Center, such as setting up the associated DevOps Center project, adding development and pipeline environments, configuring your pipeline, and creating and assigning work items to team members.
Configure Session Settings: Due to the underlying technologies that support creating sessions that allow DevOps Center to interact with multiple environments in a project’s pipeline, IP addresses aren’t static. Therefore, you must disable the session setting, Lock sessions to the IP address from which they originated, to avoid seeing errors when attempting to commit and promote changes.
Confirm DevOps Center Package Installation: When installation is complete, you receive a confirmation email. You can confirm the installation on the Installed Packages Setup page.
Connect to a Different GitHub Account: When creating or opening a project, all team members log in to GitHub using the account that has access to the repos that your team wants to use with DevOps Center. If you or a team member logged in with the incorrect GitHub account, a team member with Salesforce admin privileges can delete the authorization information so you or the team member can log in using the proper credentials.
Connect to the Source Control Repository: Connect your GitHub or Bitbucket repository to Lifecycle Center. On connecting, Lifecycle Center creates feature branches and change requests. It then commits and merges changes to each pipeline stage.
Create and Assign Work Items: Use work items to track the progress of changes related to specific objectives, such as user stories or issue fixes. Work items help teams manage changes and releases by providing visibility into the status and progress of changes.
Create a Change Request: Start a peer review of your work item by creating a change request directly from DX Inspector.
Create a Lifecycle Center Project: Create a project to serve as the central workspace for your team’s change management collaboration.
Create a GitHub Project: Create a GitHub project to help you and your team manage changes for a particular application or customization.
Promote Individual Work Items from a Stage: Move approved work items forward without waiting for the entire stage to be ready. Select specific work items for promotion, while others remain in their current stage until they’re ready.
Custom Promotion: Select and promote individual work items that are ready for the next pipeline stage by using custom promotion.
Data Commit and Deployment: Maintain data integrity and keep dependencies intact by moving metadata and data together in a single work item. In Lifecycle Center, you can move configuration data between environments using the same commit and deploy flow that you use for metadata.
Deploy Changes Using Salesforce CLI (Beta): Use Salesforce CLI to deploy changes to a pipeline stage’s environment or to perform a validate-only deployment. You must externally merge any changes in the source control repository before you can perform the deployment using the CLI. While the CLI command runs, you can see the progress of the promotion reflected in the DevOps Center Pipeline Stages tab.
Run a Validate-Only Deployment: To ensure a successful deployment ahead of time, create a validate-only deployment. You can create a validation for only the bundling stage and versioned stages. You can run a validate-only deployment within DevOps Center or using Salesforce CLI.
Are You Sharing a Development Environment?: Changes are associated in Lifecycle Center with the development environment within a project. Therefore, we recommend that all developers have their own development environment. A single development environment can be connected to multiple work items.
Swap a Development Environment: Swap a development environment with another development environment. If your development environment is a Developer or Developer Pro sandbox that was recently refreshed, the connection to the existing environment is no longer valid. You must swap the sandbox to reestablish the connection to it in DevOps Center.
Synchronize Your Development Environment: If you’re working on a team with multiple developers, it’s likely that your dev environment is going to become out of sync with the source control repository. DevOps Center tracks the differences between each development environment and the first pipeline stage’s branch.
Disable API Access Control Setting for Allowlisted Connected Apps: For orgs with API Access Control settings enabled by Salesforce Support, you must disable the “For admin-approved users, limit API access to only allowlisted connected apps” because this setting blocks DevOps Center from interacting with required APIs.
Measure Project Performance with DORA Metrics: Track your team’s delivery speed and stability by using DevOps Research and Assessment (DORA) metrics in Lifecycle Center. These metrics help you understand how quickly work items move to production and how reliably promotions succeed. You can view metric data for up to 90 days.
DX Inspector: Connect your development environment directly to your Lifecycle Center project to manage work items and track changes without leaving your org.
Access Lifecycle Center: Lifecycle Center is enabled by default in your Salesforce org, so you don't have to turn it on. You can open it directly from the App Launcher. The first time you open it, accept the DX Tools terms and conditions.
Environment Management Options: You have several options to manage your environments from the environment’s menu in the Pipeline Environments tab. Which menu options are available is determined by the environment type and whether the pipeline is activated.
Lifecycle Center Environments: Environments are the Salesforce orgs, such as sandboxes, scratch orgs, or production orgs, connected to your Lifecycle Center pipeline. Lifecycle Center uses different environment types for development, pipeline stages, and release.
Exclude Metadata with the .forceignore File: Use the .forceignore file to exclude files or metadata types that you don’t want to commit to the source control or deploy to the target org in your release pipeline. This file makes sure that DX Inspector and Lifecycle Center don’t push or pull unnecessary files, such as IDE configuration files, local test data, or specific profiles, from the development environment.
External Change Requests and Merges: You can create a change request and merge your changes directly in the source control system, which is the first half of the promotion process. You can complete the promotion by deploying all externally merged changes to the pipeline stage’s associated environment within DevOps Center or by using Salesforce CLI.
DevOps Center (Managed Package): After your team manager or Salesforce admin has installed and configured DevOps Center, you’ll be notified that the DevOps Center org is ready for you to log in. As part of the setup process, they created one or more projects, source control project repositories, and work items associated with each project. They also added each team member’s source-tracked development environment.
Access Policy Controls: Policy controls is your central workspace for reviewing and managing the governance policies and rules active in your org.
Enable Lifecycle Center Governance: Enable Lifecycle Center Governance to unlock policy controls in your org and start enforcing policies across coding agents.
How Lifecycle Center Governance Works: Policies are the foundation of how Governance works. Each policy consists of a set of rules—each rule targeting a specific risk area and defining what gets prevented.
What is Lifecycle Center Governance: Lifecycle Center Governance is a centralized policy enforcement layer built into the Lifecycle Center. Through policy controls, Governance defines what coding agents can do across your org—at the point of action, before violations reach your environment.
Get Started with Lifecycle Center Governance (Beta): Lifecycle Center Governance helps you maintain control and compliance across agentic development in your organization. It automatically enforces security and compliance policies, monitors coding agent activity in real time, and prevents violations before they reach your environment.
Lifecycle Center Governance Policies: Lifecycle Center Governance includes a catalog of predefined policies covering the risk areas of AI-assisted development—from security vulnerabilities and unauthorized deployments to code quality and compliance standards.
External Merges: Lifecycle Center detects external changes that you merge directly into a stage’s source control branch.
Integrate Agentforce Vibes IDE with Lifecycle Center: Agentforce Vibes IDE provides a modern developer experience and comes with everything you need to work with Salesforce DX MCP Server and Lifecycle Center tools (previously DevOps Center tools). We recommend setting up Agentforce Vibes IDE if you want to experience the capabilities of the MCP server.
Jira Integration with Lifecycle Center: Connect Jira with Lifecycle Center to import Jira work items and retain planning context throughout development. With Jira integration, your team can reduce duplicate data entry, improve collaboration, and gain visibility into work from planning through deployment.
Manage Environments: Replace or remove environments in Lifecycle Center as your project evolves. Environments are the Salesforce orgs, such as sandboxes, scratch orgs, or production orgs, connected to your Lifecycle Center pipeline. Available operations depend on the environment type and pipeline activation status.
DevOps Center Managed Package Migration (Developer Preview): Move your DevOps Center (Managed Package) projects into Lifecycle Center. Migration includes your projects, pipelines, environments, and eligible work items so your team can continue to release changes in the new experience.
Reconnect DX Inspector to Lifecycle Center: If your team recently migrated from DevOps Center (Managed Package) to Lifecycle Center, remove your existing DX Inspector connection and reconnect to Lifecycle Center so that your commits go to the right project.
Access Lifecycle Center MCP Tools: Set up Salesforce DX MCP Server for use with Agentforce Vibes IDE, integrated with Agentforce Vibes Extension as the MCP client. Use prompts in Agentforce, a part of Agentforce Vibes Extension, to do common DevOps tasks, like managing work items, and resolving merge conflicts.
Merge Conflict Resolution with DevOps Center MCP Tools (Managed Package): The DevOps Center Model Context Protocol (MCP) tools in Salesforce DX MCP Server are a set of capabilities that simplify and accelerate the resolution of merge conflicts. The MCP server uses large language models (LLMs) to analyze conflicts, translate them into natural language explanations, and suggest solutions, so you can use natural language prompts instead of commands. Access these tools through Agentforce Vibes in your Integrated Development Environment (IDE).
Resolve Merge Conflicts with Lifecycle Center MCP Tools: Detect, analyze, and resolve merge conflicts directly within your workflow. You can start this process using the Resolve with Agentforce option in the Lifecycle Center UI, which opens the Agentforce Vibes IDE with the Agentforce Vibes Extension and adds the conflict details to your prompt.
Resolve Merge Conflicts by Using DevOps Center MCP Tools: Resolve merge conflicts by using natural language prompts. The provided prompts are examples that you can customize to suit your needs. The sample response varies based on the LLM that you use.
Tool Descriptions: Find detailed descriptions and sample prompts for each tool.
Lifecycle Center MCP Tools and Skills: Accelerate your DevOps application lifecycle with Lifecycle Center MCP tools and skills. Use natural-language prompts in your IDE to interact with Lifecycle Center, or use skills to automate release workflows. MCP tools and skills simplify and standardize Lifecycle Center workflows.
Manage the Work Item Lifecycle with Lifecycle Center MCP Tools and Skills: Use Lifecycle Center MCP tools and skills to manage your work item’s lifecycle end-to-end. Handle work item creation, code changes, pull requests, and promotions using natural language prompts through your IDE, or automate these actions headlessly with Lifecycle Center skills.
Merge Conflicts: Merge conflicts can occur when multiple work items contain one or more of the same components, especially when multiple developers are making changes that impact the same components in different development environments. Lifecycle Center warns you about potential merge conflicts so you can investigate to ensure that you don’t inadvertently overwrite desired changes.
Migrate to Lifecycle Center: Migrate to Lifecycle Center (formerly Next Generation DevOps Center), which is built into the platform and provides an agentic experience and enhanced workflows for managing and releasing changes.
Resolve Merge Conflicts in Lifecycle Center: Lifecycle Center uses Agentforce to streamline conflict resolution for both low-code admins and developers. By integrating with Agentforce Vibes, Lifecycle Center provides AI-assisted guidance whether you work in the UI or the IDE.
If an Organization Owns the GitHub Repo: GitHub repos owned by an organization aren’t visible in DevOps Center until an organization account owner provides access.
Govern, Manage, and Release Changes with Lifecycle Center: Salesforce Lifecycle Center (formerly next-generation DevOps Center) brings change and release management, governance, analytics, and agentic development together in one place. Admins, developers, release managers, and AI agents collaborate from a common source of truth, apply DevOps best practices, and deliver changes through a repeatable, scalable, and governed process.
Build an Extension Package for DevOps Center: Salesforce partners and ISVs can use scratch orgs as their dev environments when building managed second-generation (2GP) extension packages that expand the functionality of DevOps Center. An extension is any package, component, or set of components that adds to the functionality of a managed package. An extension requires that the base managed package is installed in the org.
Best Practices When Naming Branches: Each pipeline stage has an associated branch in the source control repository, which contains the changes associated with your team’s work items. When building your pipeline, you can specify either an existing branch in the repository, or allow DevOps Center to create one for you. If you allow DevOps Center to create it for you, indicate a unique alphanumeric string.
Activate the Pipeline: A pipeline is ready for your team to use after you activate it.
View Pipeline Events in Activity History: DevOps Center provides a comprehensive history of all key pipeline events, including promotions, synchronizations, and errors (failures). You can use these events and their associated details for auditing, troubleshooting, and general visibility purposes.
Decide How to Build Your Pipeline: After you define development environments and a release (production) org, you have a basic pipeline. However, it’s not recommended that you deploy directly to production. You can use our template to build the pipeline, you can add more stages to the pipeline template, or you can build your own.
Build Your Own Pipeline: Quickly build your own pipeline by modifying the existing template pipeline.
Build Your Pipeline Using the Template: When you specified the release target (production) environment, it automatically became the last pipeline stage. DevOps Center also associates it with the default branch in the source control repository, which is often called main by default. We don’t recommend that you edit the branch for this final pipeline stage.
To Bundle or Not to Bundle, That’s a Great Question: The process and mechanism for promoting changes from one stage to the next can vary as you move from “left to right” in the pipeline. In the earlier (left) stages of the pipeline, you often want more flexibility to promote individual work items from one stage to the next. As you move to the later (right) stages of the pipeline, it’s often desirable to have more predictability and ability to version the sets of changes that are promoted and ultimately released.
Swap a Pipeline Environment: Swap a pipeline environment with another environment. If the pipeline environment is a sandbox that was recently refreshed, you must swap it before anyone can promote changes to the associated pipeline stage. The DevOps Center connection to the current environment is no longer usable.
Plan Your Pipeline: A pipeline defines the sequence of stages that work items progress as they go through the release lifecycle from development through to production (or some other final release stage).
Plan Your Lifecycle Center Setup: Before you configure Lifecycle Center, plan how your team works and what your release process looks like. The decisions you make during setup, such as how many pipeline stages to create, which environments to connect, and which source control provider to use, shape how effectively Lifecycle Center works for your organization.
Add the Release Environment for the Project: At a minimum, projects require a release environment (often your production org) and one developer environment. Be sure all team members are users in this environment if they require access to it to perform deployments to it from within DevOps Center.
Lifecycle Center Project Best Practices: Follow these best practices to plan your Lifecycle Center project. Project is a centralized workspace to manage and deploy a distinct collection of related work items.
Hide a Project: Hide a DevOps Center project so that it doesn’t show up on the Project page. The project still exists but is removed from the Projects list.
Manage DevOps Center Projects: Your team’s central arena for work in DevOps Center is the project. The purpose of a project is to help you and your team manage changes being developed for a particular application.
Update Project Details: Update project details for a DevOps Center project. You can change the name and description for a project after you define the release environment.
Promote Work Items: Move your work items through a predefined sequence of pipeline stages, guiding them from development to production.
Promote All Work Item Bundles: When you promote work item bundles, all unpromoted versioned bundles are promoted together to the next stage. The unpromoted work item bundles and corresponding work items are listed in this stage.
Promote Individual Work Items as a Work Item Bundle: During pipeline configuration, your project manager can define a stage as the bundling stage. Instead of selecting individual work items to promote, you promote work items in this stage as a work item bundle. All unpromoted work items in this stage become part of the bundle.
Combine Work Items in DevOps Center (Managed Package): Prevent potential conflicts during the promotion process by combining work items that share metadata components. In some cases, the source control repository doesn’t know how to reconcile the changes to the same metadata component. Sometimes the promotion is blocked based on a dependency with a shared component. But have no fear, DevOps Center detects the shared components and provides you with a way to promote your changes through the release pipeline with confidence.
Conflict Detection and Resolution: Conflicts can occur when you’re working with multiple development environments and moving changes between multiple pipeline stages. Conflicts can take different forms, and Lifecycle Center (formerly next-generation DevOps Center) provides functionality to help you identify potential conflicts early and resolve them.
View Deployment Status to Dig Deeper: If the deployment error doesn’t provide sufficient information, you can see more details in the Deployment Status in the org.
Mergeability Rules and Merge Settings: Lifecycle Center blocks promotions if there’s a conflict, if a test failed, or if a mergeability rule or merge setting isn’t met.
Promotion Options: The available promotion options depend on if you’re promoting individual work items, work item bundles, or performing a validate-only deployment.
Promote Changes Merged Outside of DevOps Center: If you merge the change request in the source control system, the changes are in a partially promoted state because they’ve been merged but not yet deployed to the associated pipeline environment. You can complete the promotion in DevOps Center or use Salesforce CLI.
Promote Changes Through Your Pipeline: Promotion moves your changes to the next stage in a Lifecycle Center pipeline. When you promote, Lifecycle Center first merges the changes from the current stage’s source control branch to the next stage’s branch, and then deploys them to the org associated with the next stage.
Review and Resolve Conflicts in Your Source Control: In cases where DevOps Center can’t combine work items or you choose not to combine, DevOps Center blocks the promotion. In this case, you manually edit the files directly in your source control to resolve the conflict in the affected branch.
Troubleshoot a Stalled Promotion: A promotion can stall while Lifecycle Center deploys changes to the target environment or merges changes into the target stage branch. Check the deployment and change request to determine where the promotion stalled, and then follow the appropriate recovery procedure.
Fix a Stalled Promotion When Deployment Succeeds But the Branch Merge Fails: If DevOps Center deployed the changes to the target environment but didn’t merge them into the target stage branch, set the associated async request record status to Error. Then refresh the pipeline and try the promotion again.
Fix a Stalled Promotion When the Promotion Failed: If a promotion failed before DevOps Center deployed the changes to the target environment or merged them into the target stage branch, set the associated async request record status to Error. Then refresh the pipeline and try the promotion again.
Fix a Stalled Promotion When the Promotion Succeeded: If DevOps Center deployed the changes to the target environment and merged them into the target stage branch, but the promotion doesn’t appear as completed in DevOps Center, update the associated records to reflect the successful result.
View Promotion Status: When promotion completes, you see a success banner or a failure banner where you can see details of the error. You have several options to validate the promotion or dig into errors.
Promote Individual Work Items: After a work item is considered “ready to promote,” it’s added to the Approved Work Items list. You can then promote individual work items to the first pipeline stage.
DevOps Center Releases: Based on your feedback and our drive for innovation, the DevOps Center team releases new features, product enhancements, and bug fixes on a regular basis. If you want to know all the goodness included in each package version, you’ve come to the right place.
Remove an Environment: Remove an unused development environment from your Lifecycle Center pipeline. You can add a removed environment again later. You can't remove an environment that has an activity history, use replace instead.
Replace and Connect a New Environment: Maintain pipeline integrity by replacing an expired, deleted, or refreshed development or pipeline environment in Lifecycle Center. When you connect a new environment, Lifecycle Center restores the complete branch state, including metadata and configuration data, to keep it in sync with the pipeline.
Replace a Development Environment: After a Developer or Developer Pro sandbox refreshes or a scratch org expires, the connection to Lifecycle Center becomes unusable. Replace the development environment in Lifecycle Center to restore the connection. Lifecycle Center deploys the pipeline stage branch to the new sandbox so that you can continue working with the correct metadata and configuration data.
Replace a Pipeline Environment: Activating a refreshed sandbox permanently deletes the original environment and its data, which breaks the connection to Lifecycle Center. Replace the pipeline environment in Lifecycle Center before your team members promote changes to the associated pipeline stage. Lifecycle Center deploys changes from the pipeline branch to the new environment.
Review Changes with Team Members: After you open a pull request in your source control repository, your team members and collaborators can add comments about the changes.
Run Back Sync: Move changes from the first pipeline stage to your development environment. Running a back sync makes sure that you're working with the most up-to-date, approved changes.
Install and Configure DevOps Center (Managed Package): A Salesforce admin or user with the appropriate permissions can install DevOps Center (Managed Package). A Salesforce admin or user who is assigned the DevOps Center Manager permission set can configure DevOps Center.
Set Up Bitbucket as Your Source Control: Configure your Bitbucket Cloud repository to store project files and manage team access. Each Lifecycle Center pipeline requires its own Bitbucket Cloud repository as the single source of truth.
Determine What Metadata Types to Ignore During Development: Your Salesforce DX project repo contains a .forceignore file that determines what metadata and files to exclude when retrieving files from development environments and deploying changes to environments in your release pipeline.
Enable and Install DevOps Center in the Org: Enable DevOps Center to provide the permissions needed to install the DevOps Center package in the org. You can install DevOps Center in the org that is the final release org in your pipeline, or in another org that is unrelated to the orgs in the pipeline.
Evaluate Lifecycle Center in a Non-Production Org: Lifecycle Center is available in all orgs from the App Launcher. To evaluate it without affecting your production org, access it from a Developer Edition (DE) org and connect non-production orgs as pipeline environments. Connecting non-production orgs keeps your evaluation separate from live business data.
(Optional) Seed a Source Control Repository with Org Metadata: If you’re currently using change sets to move changes to environments in your release pipeline, it’s likely that you don’t have a source control repository that contains your production org’s metadata. Although you can approach this task in any number of ways, this method uses the Salesforce (Developer Experience) DX tools that many of you’re already familiar with. However, those of you who don’t have any experience using DX developer tools can easily follow along.
Add the Local DX Project Files to the GitHub Repository: In Salesforce Extensions for VS Code, add the files you retrieved from your org to the DevOps Center project’s GitHub repository. The GitHub repository has the same name as the DevOps Center project name. After you add the files to the source control repository, the process creates the main branch, which you’ll associate with your release environment. Other branches for pipeline stages are created when you build your pipeline in DevOps Center.
Authorize the Source or Production Org: In Salesforce Extensions for VS Code, connect the release (production) org or source org that contains the metadata that you want to add to the source control repository.
Create a DevOps Center Project Repository: Create a project in DevOps Center, which creates a corresponding GitHub repository with the required Salesforce DX project structure.
Generate a Manifest and Retrieve Metadata From the Org: In Salesforce Extensions for VS Code, use Salesforce CLI to generate the manifest that contains the metadata types you want to retrieve from the production org.
Set Up Your GitHub Project Repositories: A GitHub repository (sometimes called a repo for short) stores project work files — code, text, images, and so on. Each DevOps Center project needs its own repository for storing project changes. While you’re working on the project, the repository is the team’s centralized source of truth to manage changes.
Lifecycle Center Skills: Lifecycle Center skills are reusable instruction packages that enable AI coding tools to set up, query, test, and operate Lifecycle Center according to your team's DevOps standards and workflows.
Get Ready to Use a Source Control System: DevOps Center requires that you use it with a source control system. You can create a new account or use an existing account. Right now, we support GitHub and Bitbucket (beta).
Source Control Setup: Lifecycle Center uses your source control as the single source of truth for all metadata and configuration data changes across your pipeline. A repository stores your project work files, including code, text, images, and so on.
Update the Project’s Source API Version Each Salesforce Release: Because projects in DevOps Center require a source control repository that uses the Salesforce DX project structure, each DevOps Center project contains a configuration file, sfdx-project.json. During each Salesforce release cycle, make a plan to update the source API version to avoid metadata type version mismatch errors when moving changes through your release pipeline.
Specify a Branch for a Pipeline Stage: Each pipeline stage in Lifecycle Center has an associated branch in your source control repository that contains the changes for your team's work items. When you build your pipeline, let Lifecycle Center create a branch for a stage, or specify an existing branch in the repository.
Keep Your Development Environment in Sync: Use back sync to update your development environment with the latest changes from the first pipeline stage. Keeping your environment current helps maintain compatibility with your team’s changes and reduce merge conflicts.
Create and Assign Project Work Items: Create work items so that when your team members open DevOps Center for the first time, project work is already identified and assigned to them.
Add a Quality Gate to a Test Suite: Attach a quality gate rule to a test suite to enforce pass criteria before work items can be promoted.
Add Test Suites to a Stage: Assign test suites to a pipeline stage to automate quality checks when a Review Event or Pre-Promotion Event is triggered for that stage.
Testing Before Promotion to the Next Stage: Lifecycle Center Testing automatically runs assigned test suites before a work item advances to the next pipeline stage, ensuring only validated changes reach Integration, Staging, and Production.
Configure a Test Provider: When you configure a test provider, Lifecycle Center Testing automatically syncs your tests and test suites into the Lifecycle Center pipeline stages.
Create a Quality Gate Rule: Define a quality gate rule that sets the pass threshold, severity limits, or essential test requirements for a test suite.
On-Demand Testing for Pre-Promotion Events: If a Pre-Promotion Event fails, on-demand testing lets you manually verify whether tests are now passing. A new automated execution runs when the promotion is attempted again. This is most commonly used when a promotion is blocked by a failed quality gate and you need to re-trigger testing after resolving the underlying issue.
On-Demand Testing for Review Events: Manually trigger a test run for a review event when automated testing has failed or when you need to verify test results before attempting a promotion.
Quality Gates: Quality gates define the pass thresholds, severity limits, and essential test requirements that changes must meet before advancing in your pipeline.
Unassign Test Suites from a Stage: Unassign a test suite from a stage when it's no longer relevant or when you need to streamline testing for a faster deployment. Removing an assignment does not delete the test suite — it remains available to reassign at any time.
Set Up Lifecycle Center Testing: Configure Lifecycle Center Testing to enforce quality at every stage of your pipeline, from the first review to the final promotion into production.
Shift-Left Testing for Review Events: Lifecycle Center Testing automatically runs assigned test suites when a developer creates a review in DX Inspector, catching issues early before changes advance through the pipeline.
Sync Test Providers: Syncing ensures your pipeline has the latest test data and configurations from your connected test providers. Run a sync whenever test suites are added, removed, or updated in your provider tool.
Test Providers: Selecting the right test provider depends on your testing needs, the maturity of your Salesforce org, and the types of changes moving through your pipeline. You can configure multiple providers and assign different test suites to different pipeline stages — so the right tests run at the right time.
Test Suites: Test suites are the foundational building blocks of your testing strategy in DevOps Center Testing. A test suite is a logically grouped collection of tests from a single test provider — such as a set of Apex unit tests, a Code Analyzer scan configuration, or a partner test package. Rather than running individual tests one by one, test suites let you define meaningful groups of tests that reflect your team's quality standards and assign them as a unit to pipeline stages.
View Test Details for Pre-Promotion Events: Review the test results generated by a pre-promotion test run to assess whether a work item meets quality gate requirements before it advances to the next pipeline stage.
View Test Details for Review Events: Review the test results generated by a shift-left test run to identify failures and assess the quality of changes before promotion.
View Logs for Synced Test Providers: Sync logs give you a record of past sync activity for each test provider, including the number of test suites synced, sync timestamps, and any errors encountered during the process.
View Test Suite Group Execution: Monitor the live status and results of all test suites running as a group during a review or promotion event.
Error: Unable to Reauthenticate Bitbucket After Credential Changes: Your Bitbucket connection with Lifecycle Center works, but when your team revokes tokens or modifies access configurations, the authentication fails. Lifecycle Center prompts you to reauthenticate and the Home page shows that you're logged out.
Lifecycle Center Migration Errors: Here are some tips if you encounter issues while migrating from DevOps Center (Managed Package) to Lifecycle Center.
Tests Tab Not Visible in Pipeline: Troubleshoot issues with the Tests tab not appearing on the pipeline record page in Lifecycle Center.
Lifecycle Center Error: Unresponsive Lightning Page: When you access a Lightning page in Lightning App Builder, you receive a warning message: "You can't add a runtime_alm_devops:{component_name} component there." If you dismiss the warning, the page becomes unresponsive, and you can’t make any further edits.
Troubleshoot DevOps Center Errors: Here are some tips if you encounter issues while using DevOps Center. If needed, get help from your team manager or Salesforce admin to resolve these issues.
Error: Promotion Stopped Due to New Events Dialog: This error can occur if you attempt to promote work items but DevOps Center is processing pending events from the source control system. You sometimes see this dialog in combination with the “Too Many Callouts” error message. To fix this error, you perform a SOQL query to determine if event processing is continuing as expected or has stalled.
Error: Deployment of the work items into the next stage failed: This error occurs when deploying or promoting metadata components with unsupported special characters to a pipeline stage. The error text displays the component name and indicates that it wasn’t able to find the component in the zipped directory. To fix this error, replace the non-supported special characters with their URL-encoded versions.
Uninstall DevOps Center: You can uninstall DevOps Center, if necessary. If you plan to reinstall DevOps Center, don't delete the DevOps Center auth providers. However, if you deleted the auth providers, you can recreate them by re-enabling the DevOps Center preference in Setup.
Delete DevOps Center Authentication Providers: Delete the auth providers only if you don’t plan to reinstall DevOps Center. After you’re done with your evaluation, you can delete the DevOps Center auth providers as the last step to remove all installation artifacts from your org. But proceed with caution. You can’t manually recreate them if you change your mind.
Disable DevOps Center Preference: When DevOps Center was installed, a Salesforce admin first enabled DevOps Center. To ensure that DevOps Center can’t be installed or used, you can disable the DevOps Center preference.
Delete DevOps Center Named Credentials: Remove any named credentials associated with DevOps Center, which manage authentication to your development and pipeline environments.
Uninstall the DevOps Center Package: After you remove the permission set and permission set assignments, you can uninstall the DevOps Center package, which removes the application and all its associated data and objects.
Remove Permission Set Assignments: Before you uninstall the DevOps Center package, remove permission set assignments, then delete DevOps Center permissions sets.
Upgrade to the Latest DevOps Center Version: In most cases, you don’t have to do anything to upgrade to the latest version of the DevOps Center. When we release a new package version, we update your org automatically.
Add View in DevOps Center Button to Project Layout: If you upgraded from a previous version of DevOps Center, the View in DevOps Center button doesn’t always show up in the Project page layout. If this navigational button is missing, add it back so you can easily navigate between the Lightning Experience record pages and the DevOps Center app when creating projects. You can alternatively access the DevOps Center app using App Launcher.
Add Connect Repository Button to VCS Layout: If you upgraded from a previous version of DevOps Center, the Connect Repository button doesn’t always show up in the Source Control System (VCS) page layout. This button is required when initially setting up a source control system vendor, such as Bitbucket.
Add View in DevOps Center Button to Work Item Layout: If you upgraded from a previous version of DevOps Center, the View in DevOps Center button doesn’t always show up in the Work Item page layout. If this navigational button is missing, add it back so you can easily navigate between the Lightning Experience record pages and the DevOps Center app when creating work items. You can alternatively access the DevOps Center app using App Launcher.
Version Control System Synchronization: Maintain consistency between your pipeline and your source control repository by detecting external changes and merges.
View Work Item Events in Activity History: You can view the Activity History for each work item, which provides a comprehensive history of all key events, including promotions, commits, work item status changes, warnings, and errors (failures). This historical view enables you to maintain and view a record of events and associated details for auditing, troubleshooting, and general visibility purposes.
Add Any Metadata Component Manually: A key benefit of DevOps Center is that we track changes for you. However, for those times when you require flexibility to include more metadata than what was pulled automatically, you can select and commit additional metadata source files, not just the ones that DevOps Center determines have changed.
Available Changes List: When you connect a source-tracked development environment to a work item and pull changes, DevOps Center displays a list of all files that it has identified as changed. These changes aren’t associated with the work item until you select and commit them to the source control repository. After a change is committed, it no longer appears in the Available Changes list.
Review Changes in GitHub: Create a change request (pull request) so that a team member can review and approve your changes.
Determine Which Changes to Include for the Work Item: The work item Changes tab is where you can see the changes you made in the development environment. As you make changes in the development environment, the source-tracking feature keeps a record of the component files that have been added, deleted, or changed.
Commit Changes to the Source Control Repository: After you decide which changes to include for the work item, commit the changes to the project’s source control repository. When you commit changes, they’re stored in the repository branch that was created when the work item moved to the In Progress stage.
Work in a Connected Dev Environment: When you choose to work in a connected development environment, you perform much of your development and configuration tasks directly in a Developer or Developer Pro sandbox with source tracking enabled. We also support scratch orgs, which have source tracking enabled by default.
Create a Work Item: All work begins with a work item. A work item captures a logical unit of work, such as a user story, task, or bug. Work items are organized by project and belong to the project where you created them.
Exclude Metadata from the Changes List: When retrieving changes from your development environment, you likely have files or metadata types that you want to exclude from committing to the source control repository. You can exclude individual files or all files in a specific directory with a .forceignore file. DevOps Center provides you the ability to view information about these ignored files but they don’t show up in the changes list.
Work Item Management: A team uses work items to track the progress of changes created to achieve a specific objective or task. These tasks can include enabling a user story, creating a feature, or addressing a bug. Managing releases through work items makes it easier to track the progress of the overall release and identify areas of concern.
Modify Work Item Details: Keep work items up to date to provide full value to the team. For example, if new acceptance criteria is identified, edit the work item to ensure the assignee knows of the change. Or if you’re ready to start on an unassigned work item, assign the work item to yourself, which lets other team members know you’ve picked it up.
Change Work Item Status to Never: Use the Never status when plans change, when you need to start over, or when a change conflicts with another work item’s promotion.
Open a Work Item: When you open a project for the first time, it's likely to contain several work items that your release manager created when configuring DevOps Center. You and other team members can create additional work items as the project progresses.
Pull Changes from the Development Environment: Because the development environment has source tracking enabled, DevOps Center knows what files have been added, changed, or removed. When you pull changes, DevOps Center displays a list of all files that it has identified as changed. These changes aren’t associated with the work item until you select and commit them to the source control repository.
Indicate That Work Items Are Ready to Promote: After the work item is reviewed, a team member approves the work item to be ready to promote. Work items aren’t available for promotion through the pipeline until they are in the Ready to Promote status.
Review Changes with Team Members: When changes for an In Progress work item are committed and ready to share with reviewers, creating a review opens a change request, also called a pull request.
Work Item Lifecycle and Status: A work item includes a status and progress indicator so your team can quickly understand where work stands in the release cycle. Work items move through these statuses: New, In Progress, In Review, Ready to Promote, Promoted, and Closed.
Work Outside of DevOps Center (Managed Package): After a work item is created, you can choose to do your development work entirely outside DevOps Center (without connecting to a development environment). After changes are merged in the source control system, the promotion is completed in DevOps Center or by using Salesforce CLI.
Promote Work Items Through Your Pipeline: You promote work items through a pipeline, which defines the sequence of stages that work items progress as they go through the release lifecycle from development to production (or some other final stage). You can have any number of pipeline stages. Your team manager built the pipeline when configuring DevOps Center.
Work Outside the Lifecycle Center UI: Use your preferred local development tools to work on Lifecycle Center work items and commit changes directly to source control. After merging your changes, complete the promotion in Lifecycle Center.
Analyze Test Reports to Identify Failures: Test reports show you which test suites passed and, more importantly, which ones failed. Use the insights from these reports to proactively address and fix root causes, and improve the quality of your work items.
Change the Retention Period for Test Data: Change the test data retention period as needed to balance legal compliance, business requirements, and performance. The default retention period is 30 days.
Change the Test Severity Level: From the Tests tab, you can change the severity level of tests. Severity levels prioritize failing tests based on their potential impact. DevOps Testing evaluates the quality gate rules according to these severity levels. When creating a quality gate rule, you can set severity-level threshold criteria. If a test with a severity equal to or higher than the threshold fails, the quality gate rule also fails.
Create a Test Suite: You can create new test suites directly from within DevOps Testing if your test provider supports it. After creating a new test suite, you can start a manual sync to make sure it's synced with your test provider.
Create a Quality Gate Rule: Create a quality gate rule based on your testing goals. We recommend establishing criteria that are realistic yet strict enough to maintain quality.
Test Data Retention and Cleanup: In DevOps Testing, the data retention and cleanup processes automatically manage historical test data. A daily cleanup job automatically deletes data older than the set retention period, improving performance and data governance.
Enable or Disable Quality Gate Rules for Test Suites: Enable or disable quality gate rules after they’re assigned to test suites. While we recommend that you do not disable your quality gate rules, you can temporarily disable them if tests are inconsistent or to speed up deployment. After disabling, reevaluate quality gate rules to promote the changes.
Quality Gate Rules: Quality gate rules are checkpoints that make sure only work items that meet your quality criteria move to the next pipeline stage. Use quality gate rules to maintain code quality, ensure reliable deployments, and identify issues early in the application lifecycle. When a quality gate rule fails, you can analyze the reason and resolve any issues before attempting to promote the work item again.
Get to Know the DevOps Testing UI: If you’re new to DevOps Testing, here’s a quick overview of the UI and what you can achieve on each tab.
Improve Release Quality with DevOps Testing: DevOps Testing extends the capabilities of DevOps Center by bringing AI-powered testing and quality control into your DevOps pipeline. Integrate DevOps Testing with testing tools, set quality gates, and run test suites to thoroughly test changes as they move through the DevOps pipeline. This reduces production issues and ensures higher-quality releases.
Install and Configure DevOps Testing: Complete these one-time installation and setup tasks before you move on to the more specific tasks in the rest of this guide.
Integrate Test Providers for Unified Testing: Centralize your test management, even when your test assets are in other testing tools and platforms. On the Test Providers tab, you can integrate both Salesforce testing tools and partner test providers. After you configure the test providers, manage and run test suites directly from DevOps Testing.
Mark a Test as Essential: From the Tests tab, you can mark tests as essential. When you mark a test as essential, the corresponding quality gate rule fails if the essential test fails. This helps to prioritize critical tests and make sure that essential tests are always validated.
Optional Setup Tasks to Integrate Code Analyzer v5 as Test Provider: Make sure that your code adheres to best practices, and identify issues early in the development process with Salesforce Code Analyzer v5. To add Code Analyzer v5 as a test provider, follow these steps.
DevOps Pipeline Stage Assignments: Assign test suites and quality gate rules to your In Progress work items and pipeline stages on the Stage Assignments tab.
Test Provider Limitations: Before you integrate test providers with DevOps Testing, review these limitations and behaviors.
Reevaluate Quality Gate Rules: You can reevaluate failed quality gate rules without rerunning the test suites. Reevaluate these rules after you address an issue and want to quickly verify the quality gate rule results.
Run Test Suites Manually: Run test suites manually against various pipeline stages in DevOps Center. You can manually run test suites and quality gate rules at any time, independently of when DevOps Center events occur. You can easily identify a manual test suite run from the Event column in the Test Suite Executions tab.
Run Test Suites Triggered by DevOps Center Events: Automatic test suite runs streamline the continuous delivery process by minimizing manual intervention. Test suites and quality gate rules assigned to a pipeline stage are automatically run when a create review or promote event occurs in that stage.
Run Your Test Suites: With DevOps Testing, you can run test suites for any test provider. You can run these test suites manually as needed, or automatically based on specific DevOps Center events. After each test suite run, DevOps Testing automatically generates comprehensive test results, which you can review.
Schedule and Run a New Cleanup Job: Customize the cleanup process to meet your specific needs by scheduling a new cleanup job. Review the details of the default cleanup job and create a cleanup job as needed. When you create a cleanup job, you can retain or delete the default cleanup job.
Tests and Test Suites: Tests and test suites are the building blocks of your software testing lifecycle. They ensure quality and reliability of your work items. With DevOps Testing, you can easily view and manage your tests and test suites across multiple test providers.
View Your Test Suites: View your test suites in a single, unified summary. On the Test Suites tab, you can see the test suite details, including the last-run timestamp, status, DevOps Center project, environment, and the test provider from which it was synced. The Related tab on the test suite record page lists the tests included in the test suite.
View Your Tests: View your tests in a single, unified summary. On the Tests tab, you can see the test details, including the type of test, severity, DevOps Center project, programming language, and the test provider from which it was synced. From the Tests tab, you can change the test severity and mark tests as essential. All other test changes must be made within the test provider.
View DevOps Testing Events in DevOps Center Activity History: DevOps Center provides a comprehensive history of all key DevOps Testing events, including quality gate rule evaluation, test suite group run, stage assignments, and errors (failures). You can use these events and their associated details for auditing and troubleshooting.
Test Provider Sync History: See the outcome and details of your test provider sync process in a single, unified summary. It provides the sync status, timestamps, and reasons for any sync failures. Use this information for auditing and troubleshooting issues.
Custom Domains: Provide a branded experience for users who access your external-facing Salesforce content by serving your Digital Experiences or Salesforce Sites on a domain that you own, such as https://www.example.com.
Custom Domain Build Example: Domains and sites can have a many-to-many relationship through custom URLs. See this relationship in action with an example where three custom domains serve one parent site with two different brands.
Prerequisites for a Custom Domain That Uses Your HTTPS Certificate: Before you serve your domain with an HTTPS certificate that you own, confirm that this domain configuration option applies to your configuration. Then update your DNS configuration, and upload your HTTPS certificate.
Set Up a Custom Domain That Uses Your HTTPS Certificate: Upload an HTTPS certificate that you own to Salesforce servers, then serve your custom domain with that certificate. After you set up your domain in Salesforce, that domain can serve your Experience Cloud sites or Salesforce Sites.
Update an Expiring Certificate for Your Custom Domain: If you serve your domain with your HTTPS certificate on Salesforce servers, avoid disruption to your domain by renewing or replacing your certificate before it expires. You can find the expiration date for your HTTPS certificates on the Certificate and Key Management Setup page. Also, admins receive an expiring certificate notification email before the certificate expires.
Change the Domain Name for a Custom Domain: Whether your brand changed or you want to use a different domain to serve your site content, you can change the domain name of an existing custom domain in Salesforce. Review these important steps to ensure a smooth transition and reduce the risk of takeover attacks.
Change the Domain Configuration Option for Your Custom Domain: Change the method for serving your domain. For example, switch from a third-party service or content delivery network (CDN) to the Salesforce CDN. Update your domain in Salesforce to use a different third-party service or CDN to serve your site. Or update a temporary non-HTTPS domain to use HTTPS as required by Salesforce.
Delete a Domain: To stop serving a site via your custom domain, such as https://www.example.com, first delete the custom URLs for that domain. Then delete the domain in Salesforce. Or to point the domain to a different site, set up new custom URLs.
Determine How to Serve Your Custom Domain: To determine the recommended domain configuration option to serve your custom domain, answer a few questions about your domain and your Salesforce configuration.
Custom Domain Management: Keep your custom domain up to date with your business needs. Learn how to manage your domain during org migrations and certificate changes. Edit your domain’s configuration option, move to a different domain name, or enable HSTS preloading. And when you no longer need a custom domain, delete the domain and its custom URLs in Salesforce.
Options to Serve a Custom Domain: Salesforce supports three HTTPS options to serve your domain. Whether you serve content for your domain via an HTTPS certificate that you own, through the Salesforce content delivery network (CDN), or through an external service, we require that you use HTTPS. When initial configuration requires that your domain is available before you enable HTTPS, Salesforce also supports a temporary non-HTTPS option.
Prerequisites for a Custom Domain That Uses a Third-Party Service or CDN: If a non-Salesforce service or content delivery network (CDN) serves your domain, complete these steps before you add your domain in Salesforce. To confirm your domain ownership, update your domain’s Domain Name Service (DNS) configuration. Then work with the third-party provider to ensure access to the required HTTP protocols, configure caching and request handling, and review reverse proxy restrictions. If you’re using a third-party CDN, update the header in your CDN to track IP addresses.
Use a Third-Party Service or CDN to Serve Your Custom Domain: Use a domain that’s hosted by a third-party service to serve your Experience Cloud sites or Salesforce Sites. These third-party services include third-party hosts, web application firewalls (WAFs), and non-Salesforce content delivery networks (CDNs).
Considerations for Custom Domains That Use a Third-Party Service or CDN: Review how IP address tracking works when a third party serves your custom domain. Understand what happens if you update your domain’s external configuration after you activate the domain in Salesforce, and clean up unnecessary Domain Name Service (DNS) records.
Set Up a Custom Domain That Uses a Third-Party Service or CDN: Add a domain in Salesforce that’s hosted by a non-Salesforce service or content delivery network (CDN). After you set up your domain in Salesforce, that domain can serve your Experience Cloud sites or Salesforce Sites.
Enable HSTS Preloading on a Custom Domain: As a security best practice, enable and submit your custom domain for HTTP Strict Transport Security (HSTS) preloading. Connections can be vulnerable when HTTP requests are redirected to HTTPS. An example is a user attempting to access your custom domain using the HTTP protocol. By adding your registrable domain to the third-party HSTS preload list, supported browsers always use HTTPS, protecting your users from attacks during those HTTP redirections.
Maintain Your Custom Domain: To keep your custom domain running smoothly, follow these guidelines. If you serve your domain with your HTTPS certificate, update the certificate before it expires. Optimize your domain that uses the Salesforce content delivery network (CDN). Minimize downtime when you update your domain, and take steps to help prevent domain takeover attacks. And review recommendations for communicating to your users when you change your domain.
Move a Domain to Another Production Org: If you purchase a new production org, your old org continues to serve your sites with your custom domain. To move the domain to your new org, set up the domain, and then delete the domain in your old org. Or if you have multiple production orgs, you can move an existing domain to an org of your choice.
Custom Domains in Salesforce: When you serve your Digital Experiences or Salesforce Sites on a domain that you own, your brand can shine. Learn about domains and custom URLs in Salesforce, and understand the relationship between them.
Custom Domain Prerequisites: Before you serve your site content with a custom domain, register a domain. To get that domain ready to serve your site content, update the Domain Name System (DNS) record to point to your org. Review your site URLs for potential conflicts, and complete the prerequisites for your chosen domain configuration option.
Redirect System-Managed Site URLs to Your Custom Domain: To reinforce your brand, redirect users that visit a system-managed .my.site.com or .my.salesforce-sites.com URL to the custom domain that serves that site’s content.
Serve Your Experience Cloud Site with the Salesforce Content Delivery Network (CDN): Optimize page load times and site performance with our content delivery network. Salesforce partners with a content delivery network (CDN) provider to efficiently deliver publicly cacheable content to users on your Experience Cloud sites. We recommend the Salesforce CDN for custom domains that serve Digital Experiences, including Experiences built with Experience Cloud, Commerce, and Industries licenses.
Test Your Custom Domains in a Sandbox: Develop and test your custom domains that serve content from your Experience Cloud sites and Salesforce Sites in a sandbox before you activate the domain in production.
Activate a Sandbox Custom Domain in Production: After you test a custom domain that serves your Experience Cloud sites or Salesforce Sites in a sandbox, move any updates to your sites and the custom URLs for your domain to production. Then activate the custom domain in production.
Considerations for Custom Domains in Sandboxes: Determine whether you can set up a custom domain in your sandbox, and review considerations for using a content delivery network (CDN) with a custom domain in a sandbox. Learn how to prevent errors when you refresh, clone, or delete a sandbox associated with a custom domain.
Set Up a Custom Domain for Testing in a Sandbox: Test a new domain before you activate it in production, or test changes to your custom domain or to your sites. Create a custom domain in production that points to your sandbox. That domain serves the Experience Cloud sites or Salesforce Sites in your sandbox with the custom URLs in the sandbox.
Use a Temporary Non-HTTPS Domain to Serve Your Custom Domain: Salesforce requires that you serve your custom domain via HTTPS. However, some configuration steps can require a temporary non-HTTPS configuration. If your HTTPS certificate isn’t ready to be uploaded to Salesforce, you can use a temporary domain to start configuring your custom URLs. Also, when your domain serves other content, or when you want to move a custom domain to a new production org, you can use a temporary domain to minimize disruption to your domain.
Troubleshoot Common Custom Domain Issues: Review the potential causes and troubleshooting steps for common issues that you can encounter when you set up a custom domain.
Point Your Custom Domain to Your Salesforce Org: Before you add a domain in Salesforce, point your domain to your Salesforce org in Domain Name Service (DNS). If your custom domain uses your HTTPS Certificate or the Salesforce content delivery network (CDN) partner, add a canonical domain name (CNAME) record for your fully qualified domain (FQDN) to DNS. The CNAME record references your Salesforce org ID and your FQDN. Then, if you plan to use the Salesforce CDN to serve your Experience Cloud site on your custom domain, add a second CNAME record that our CDN partner requires.
View Your Custom Domain Details: Get information about your custom domain. For example, scan the expiration dates for your HTTPS certificates that serve your domains. Or get the target host name for your domain that’s served by a third-party service or content delivery network (CDN). Also, you can view and manage the custom URLs associated with the domain, and view alerts about the domain’s DNS configuration.
Project Management App Deployment Example: Learn how the metadata and data deployment feature in DX Inspector resolves metadata and data dependencies and preserves record relationships, using a sample app.
Activity History: View a chronological timeline of key events in your org, such as commits, deployments, and reviews. Use the Activity History tab in DX Inspector to audit activity and troubleshoot errors.
Working with Metadata and Data Dependencies: Identify, map, and visualize the relationships between metadata components and data records in your org. You can view dependencies early to select all required metadata and data before deployment, which prevents deployment failures.
Align Fields Horizontally in Dynamic Form Field Sections: Control field alignment across columns by using the Align fields horizontally property on Dynamic Forms Field Section components. This property prevents fields in multicolumn Field Sections from collapsing upward when there’s a gap due to differences in field heights. Fields remain horizontally aligned with their neighbors in the same row.
Dynamic Forms Limitations: Keep these general, migration, and packaging limitations in mind when working with Dynamic Forms.
Migrate a Record Page to Dynamic Forms: Some pages have Dynamic Forms enabled by default. For those that don't, you can migrate the fields and sections from your existing record pages as individual components in the Lightning App Builder. Then you can configure them the same way as the other components on the page, so that your users get only the fields and sections that they want. If you have save options on your account, case, or lead record pages, they are migrated.
Dynamic Forms and Mobile Using the Record Detail - Mobile Component: The Dynamic Forms Field Section component and the Field components that go inside were previously only available on desktop. To support mobile users, the Record Detail - Mobile component gives your mobile users a way to see the record details on their mobile devices on a Dynamic Forms-enabled page.
Enable Dynamic Forms on Mobile: With Dynamic Forms on Mobile, your mobile users can have the same customized experience that your desktop users have.
Break Up Your Record Details with Dynamic Forms: The more fields that there are on your page layout, the more that the Record Detail component becomes a monolithic block of fields that you can’t customize. With Dynamic Forms, you can migrate the fields and sections from your page layout to individual components in Lightning App Builder. Then you can configure them the same way as the other components on the page - spreading them out across multiple columns and tabs, and dynamically showing and hiding them based on record data, user details, and device type, so that your users get only the fields and sections that they want.
Required and Read-Only Fields in Dynamic Forms: Universally required fields retain their status when you’re working with them on a Dynamic Forms-based Lightning page. But you can make other fields required or read-only just for the page that you’re working on.
Cross-Object Fields in Dynamic Forms: Drill into lookup relationship fields from the component palette on Dynamic Forms-enabled pages in the Lightning App Builder, and access fields from related objects. Drag the cross-object fields onto your record page to display relevant data from related objects.
Dynamic Highlights Panel: The Dynamic Highlights Panel component displays up to 12 key record fields, which are configured in Lightning App Builder. The Dynamic Highlights Panel is responsive. When you change the size of your browser window, your information stays visible and wraps instead of being truncated.
Configure Interactions in the Lightning App Builder: After you have a custom source component with exposed events in your org, you can assign event targets and configure the event interactions in the Lightning App Builder.
Expressions in Dynamic Interactions Target Properties: An expression is a small chunk of code that can be evaluated to a value. It can be as literal and simple as 1+1 or a more complex combination of variables, operators, and functions. One expression is supported for Dynamic Interactions in the Lightning App Builder: {!Event.eventPropertyName}. You can use this expression when setting target component property values in the Lightning App Builder UI and in Metadata API. The value of the eventPropertyName part of the expression varies based on which properties the developer makes available for the event in the source component.
Dynamic Interactions in the Lightning App Builder: Dynamic Interactions is part of our continuing drive to make Lightning pages more dynamic and interactive. With Dynamic Interactions, an event occurring in one component on a Lightning page, such as the user clicking an item in a list view, can update other components on the page. Dynamic Interactions lets admins create applications with components that communicate and transform based on user interactions, all in the Lightning App Builder UI. It unlocks capabilities that previously were reserved only for developers.
Salesforce Connect Adapter for Amazon DynamoDB: Connect to Amazon DynamoDB to access and integrate DynamoDB data into Salesforce applications. With this adapter, take advantage of the flexible data storage capabilities of Amazon DynamoDB that provides fast and predictable performance combined with customer 360-degree view captured in Salesforce.
Map Salesforce External Object Field to DynamoDB Attributes: External object fields of Salesforce Connect Adapter for Amazon DynamoDB can be mapped to attributes of string, number, and boolean scalar types. If an attribute of string type that represents a date or a timestamp is mapped to an external object field, then date, dateTime, or time must be stored in ISO 8601 format.
Create External Objects for Salesforce Connect Adapter for Amazon DynamoDB: Tables in Amazon DynamoDB map to one or more external objects in Salesforce, combining all your data and content for users in your org. The external objects associated with Amazon DynamoDB data source are searchable objects. Use the search box at the top of every page to search by a specific external object or for a global search across Salesforce. You can also use other search tools available in the Salesforce Platform to find external object records mapped to an Amazon DynamoDB table.
Manage Qualifiers for Salesforce Connect Adapter for Amazon DynamoDB: Amazon DynamoDB uses unique design patterns to model data efficiently that support multiple table and single table designs. To make data stored in Amazon DynamoDB table accessible to external objects, use qualifiers to reinterpret external data. The qualifiers describe the item attributes and indicates whether an item belongs to the schema represented by the external object. For multiple-table schema designs, the table qualifier is optional.
DynamoDB Qualifier Examples for Parsing Formulas: This example shows a simple formula to concatenate two text values. The value of the location virtual attribute is evaluated using the values of city and state attributes. For example, if city is Los Angeles and state is California, location value is defined as Los Angeles, California.
Qualifier Example for One-to-Many and Many-to-Many Relationships in Amazon DynamoDB: An enterprise stores and retains fine-grain transaction details for millions of customers, resulting in data volumes reaching billions of records. In this example, Salesforce is the system of record for core customer information and details of all the customer’s orders are stored in Amazon DynamoDB for scale reasons.
Sort Example for Orders and Order Items in Amazon DynamoDB: To effectively sort orders and order items stored in an Amazon DynamoDB table in a way that benefits a business process, create secondary indexes that identify attribute values as the basis for sorting.
Configure an Amazon DynamoDB External Data Source with Setup Wizard: Define an external data source for an Amazon DynamoDB with fewer clicks using the setup wizard. The guided interface walks you through connecting an Amazon DynamoDB data source and integrating the data in Salesforce.
Edit Users: To change a user's details—such as username, profile, role, or contact information—edit the user account.
Edit Window Open Properties: Custom buttons and links can open in different types of windows. If you configure a custom button or link to open in a window, set the window properties. If you leave the window properties blank, the custom button or link uses the default settings of the user’s browser.
Suggest Options with Recommendation Strategies: Use Einstein Next Best Action to deliver tailored recommendations at the right moment. Define strategies that apply your business logic to surface a few high-value offers such as repairs, discounts, or add-on services. Present the final recommendations in your Automation Lightning app or Experience Builder site.
Einstein Prediction Builder: Harnessing the power of artificial intelligence (AI), let Einstein predict almost any field in Salesforce. Then, use the predictions to power workflow, focus efforts, and work smarter. No models. No algorithms. And, best of all, no code. Point. Click. Predict.
Einstein Prediction Builder Examples: With Einstein Prediction Builder, you can predict the expected value for a number field and the likelihood of Yes for a formula field with “Yes,” “No,” and null options.
Elements of a Formula: Learn the elements you can combine to build a formula: literal values, field references, functions, operators, and comments. Understand what each element does and see an example of how to enter it.
Enable Enhanced Public Group Assignment: With the Enhanced Public Group Assignment, you can assign and remove members such as users, other groups, roles, and portal roles.
Enable Actions in the Chatter Publisher: Enabling actions in the publisher lets you add actions that you’ve created to the Chatter publisher. Actions appear on the Home page, on the Chatter tab, in Chatter groups, and on record detail pages.
External Services Considerations: Here are the semantic, service, and usage constraints to keep in mind when integrating your services into External Services.
Use Flow to Invoke External Service Actions: In this Flow example, design and test the automation that sends a user’s information from Salesforce to the external employee banking system. Create the variables for user phone numbers, and combine different phone numbers into one piece of data. Then use the external service action to create the user.
End-to-end Example with Flow: In this Flow example, design and test the automation that sends a user’s information from Salesforce to the external employee banking system. Create the variables for user phone numbers, and combine different phone numbers into one piece of data. Then use the external service action to create the user.
View an Action’s Unique Apex Name: Use this example to understand how External Services actions in Apex or Flow map to specific actions in an External Service registration. An object’s unique Apex class name is specified in View Actions > More Details. This name also appears when searching for actions in Flow Builder.
View an Action’s Unique Apex Name in Flow: Map an action in Flow to an action in your external service. When searching for an External Service action in Flow Builder, you see the unique Apex name in the list of actions.
Manage Users in the Enhanced User List View: Build dynamic, customized lists that show records tailored to specific criteria in Enhanced User List View. You can also use Enhanced User List View to edit multiple records inline.
Translate Metadata Labels: Create and update metadata translations for customizations you make to your Salesforce organization, such as custom picklist values and custom field labels.
Activate the Partner Event Source in Amazon EventBridge: Salesforce creates a partner event source in Amazon EventBridge in pending status after you create an event relay. Associate the event bus with the partner event source in EventBridge so that the event source is ready to receive events from Salesforce.
Event Relay Allocations: Check out allocations related to the event relays that you can create and events relayed to Amazon EventBridge.
Event Channels: An event relay uses an event channel. A channel is a stream of events in the Salesforce event bus. A single channel can contain multiple types of platform events, including real-time event monitoring events, or change data capture events.
Create an API Destination and Connection in EventBridge: Create an API destination that uses a new connection. In this case, the API destination is a REST API call to Salesforce to publish a platform event back. The connection contains the authentication information for the API call. The connection accepts several authorization methods.
Create a Channel and Channel Members: You can create a channel and add members by using Tooling API. A channel is a stream of events. It contains members that specify the type of events that can be received on the channel. A channel can contain a stream of platform events, including real-time event monitoring events, or change data capture events. For a channel of change data capture events, you can select the standard ChangeEvents channel instead of creating a custom channel.
Create a Connected App in Salesforce for OAuth: To use OAuth to authorize the API call to Salesforce, set up a connected app in Salesforce. The connected app generates a consumer key and secret that you can store in the EventBridge connection in AWS.
Create a Named Credential for Event Relay Setup: A named credential stores your AWS account information. You use the named credential later to set up an event relay. You can create a named credential in the Salesforce user interface in Setup.
Create Prerequisite Items: Create the prerequisite items that your event relay uses, such as a named credential, a channel, a channel member, and optionally a platform event.
Create an Event Relay: An event relay associates the channel in the Salesforce event bus with Amazon EventBridge using a named credential. The creation of the event relay results in a partner event source being created in Amazon EventBridge. The partner event source is created with a pending status.
Create an Event Relay in Setup: After creating the prerequisite items, follow the steps in this section to create an event relay using a point-and-click interface in Setup.
(Optional) Define a Platform Event: If you have a custom platform event defined in your Salesforce org that you want to use for the event relay, you can skip this step. You can also skip this step if you want to use the event relay with a change data capture event. Otherwise, follow the steps in this section to define an example platform event, Carbon_Comparison__e, which the event relay configuration steps use.
Error Recovery Options: If transient errors occur, such as connectivity issues or errors in the event relay configurations, event relay resumes automatically after the connectivity issues are resolved or the configurations are fixed. The event relay attempts to resume sending events from the event bus from where it left off. In rare occasions, if it can't resume after the last relayed event, it uses the error recovery option to determine where to resume from.
Event Integration with Amazon Eventbridge: After creating the event relay in Salesforce, the event relay creates a partner event source in EventBridge. You associate the partner event source with an event bus. After you start the event relay in Salesforce, the event bus in EventBridge receives the events published and relayed from the Salesforce event bus. You can process the received events using AWS services.
Event Relay: Integrate your real-time events with Amazon Web Services (AWS). Use Event Relay to send platform events and change data capture events from Salesforce to Amazon EventBridge.
Processing Events with AWS Services: After receiving the events in EventBridge, you can process them with AWS using rules, or you can send them to third-party and SaaS integrations using API destinations.
Event Relay Security: Event relays send events to Amazon EventBridge securely using HTTP/1.1 with TLS. Event data is encrypted while in transit over the web. Salesforce is a registered partner of Amazon EventBridge and uses EventBridge Partner APIs to send events to Amazon EventBridge.
Send Events from AWS Back to Salesforce Using an API Destination: An API destination is the target of a rule, and it enables you to route events to HTTP endpoints. Specifically, you can use an API destination to publish an event to Salesforce from EventBridge using REST API.
Sending Events to Salesforce using API Destinations: After processing the events in AWS, you can publish an event to Salesforce using an API destination. An API destination is an HTTP endpoint that an EventBridge rule can invoke.
Monitoring Event Relays Using SOQL Queries: You can perform a SOQL query on the EventRelayFeedback Salesforce object to get information about an event relay, including its status, the date and time of the last relayed event, and any error message. The information contained in EventRelayFeedback is available in Setup, on the Event Relays page.
Event Relay Execution Statuses: You can run, pause, or stop the execution of an event relay. After you change the execution state, it can take several minutes for the new state to take effect. During this time, the event relay displays a transitional status in the UI. After the state change completes, the final status appears.
Event Relays in Setup: An event relay is a set of event configurations and a connection to a partner event source in Amazon EvenBridge. An event relay streams events from the Salesforce event bus to EventBridge. You can create an event relay in Setup.
Verify the API Destination: Publish a test event to the event bus that is associated with the rule you created in a previous step, and verify that your subscriber in Salesforce receives the event from Amazon EventBridge.
Create an EventBridge Rule for Logging Events in a CloudWatch Log: To test the connection between Salesforce and AWS and ensure that the event messages are received in EventBridge, add a CloudWatch log as a target of a rule. Incoming event messages from Salesforce are logged in CloudWatch.
Connect Business Processes with Real-Time Events: Publish and subscribe to platform events to connect business processes in Salesforce and external sources through the exchange of real-time event data. Also, use event relays to integrate platform events and change data capture events with Amazon EventBridge.
Event Studio Overview: Salesforce Eventing encompasses Platform Events and Change Data Capture. Event Studio allows you to track existing event publishing and consumption activity on your Salesforce Event Bus based on event publishers and event subscribers.
View Event Publishers and Subscribers: Track existing event publishing and consumption metrics on your Salesforce Event Bus based on event publishers and event subscribers.
External Account Hierarchies Considerations: Account records owned by users with roles in child accounts that are part of an external account hierarchy share data with the parent accounts in that hierarchy.
Validate and Sync an External Data Source: After you configure an external data source, synchronize it to map its tables with external objects in your Salesforce org. The content and data of external objects appear in federated search, together with your Salesforce content and data.
Set Up Your Data Your Way: Optimize your Salesforce data to fit the unique needs of your users. You can create your own objects with data that fits together in the ways that make the most sense for you.
Find Object Management Settings in Salesforce Classic: Salesforce lets you personalize your object model with features like custom fields, page layouts, and validation rules. Depending on which type of object you want to find, these customizations are located in different areas of Setup.
Find Object Management Settings in Lightning Experience: Salesforce lets you customize your object model with features like custom fields, page layouts, and validation rules. Most objects are available from the Object Manager in Setup.
Find Object Management Settings: Salesforce lets you personalize your object model with features like custom fields, page layouts, and validation rules. Depending on which experience of Salesforce you have enabled, these customizations are located in different areas of Setup.
Extend Salesforce with Clicks, Not Code: Ready to go beyond the basics of Salesforce administration? Want to customize your org, push its boundaries, and enhance its functionality? You can do that and so much more without writing a single line of code. All you need is your mouse and a sense of adventure. Enhance your objects, data, and fields, customize your org’s look and feel, augment your business processes, create websites, and even create apps—all using point-and-click tools.
Extend the Reach of Your Organization: Sometimes your users need to work with data and services that are outside your Salesforce org. There’s a variety of ways you can provide seamless access across org boundaries.
Resources for the Point & Click Administrator: In addition to online help, Salesforce creates guides and tip sheets to help you learn about our features and successfully administer Salesforce.
Enhance Salesforce with Code: You can make your Salesforce org even more useful and responsive to your users by developing custom applications and integrating your external applications.
Store Authentication Settings for External Systems: You or your administrator can set up and manage your authentication settings for external systems. With valid authentication settings, you can access external systems from within your Salesforce org.
Define External Data Sources: Create external data sources to connect to content and data that is stored outside your Salesforce org.
Work with External Data Sources: An external data source specifies how to access an external system. Salesforce Connect uses external data sources to access data that's stored outside your Salesforce organization. Files Connect uses external data sources to access third-party content systems. External data sources have associated external objects, which your users and the Lightning platform use to interact with the external data and content.
Example: How Codey Outfitters Uses External Change Data Capture: The fictitious company, Codey Outfitters, distributes outdoor equipment from local small businesses to outdoor enthusiasts around the world. The company handles all logistics, such as complying with import laws for each state and country.
Monitor External Change Data Capture: With external change data capture enabled, Codey Outfitters’ org polls the external system every 30 minutes. To monitor the tracking status, it queries the BackgroundOperation object. Codey Outfitters prefers to run SOQL queries in the Query Editor of the Developer Console, but you can use your preferred tool.
Set Up the External Data Source and the External Object: Codey Outfitters has an OData 4.0 service for its inventory. The company connects its Salesforce org to the inventory by creating an external data source called Gear Inventory and creating an external object called Products.
Subscribe to Changes with Streaming API: When Codey Outfitters runs its Bayeux client, the client subscribes to Streaming API on the products publication channel.
Use External Change Data Capture to Track Data Changes on External Objects: With External Change Data Capture, you can track changes to data that is stored outside your Salesforce org when using the OData 4.0 and 4.01 adapters. You can then build automation in response to the changes to increase productivity or provide a better customer experience.
Change the Polling Interval for External Change Data Capture: By default, the external change data capture feature polls the external system every 30 minutes for tracked changes. You can change the interval to poll the external system as frequently as every 5 minutes.
Subscribe to Change Events: You can use Apex triggers to subscribe to change events. Or you can use a Bayeux client to subscribe to Streaming API on the publication channel.
Lookup Relationship Fields on External Objects: Use a lookup relationship when the external data includes a column that identifies related Salesforce records by their 18-character IDs.
External Object Relationships: External objects support standard lookup relationships, which use the 18-character Salesforce record IDs to associate related records with each other. However, data that’s stored outside your Salesforce org often doesn’t contain those record IDs. Therefore, two special types of lookup relationships are available for external objects: external lookups and indirect lookups.
Validate External Object Connections: After you configure an external data source, run the validator tool on each external object to test and troubleshoot its connections. The tool tests for ID uniqueness and the ability to sort and filter results. Validator is available for external objects from Apex and Odata data sources.
Grant Access to Authentication Settings for External Data Sources: For external data sources that use per-user authentication, grant users access through permission sets and profiles, so users can set up and manage their own authentication settings for accessing the external system.
External Services: Connect your Salesforce org to an external API by using zero lines of code. Use declarative tools and OpenAPI specifications to describe the external API functionality, and External Services automatically creates invocable actions within Salesforce. Use External Services for outbound integrations from Salesforce by using low-code, process-based integrations or to turbocharge your Apex integrations. Call the invocable actions natively from Apex, or create a custom agent action, flow, or Einstein bot that interacts with the external API source.
Add External Service Actions to an Einstein Bot: Integrating your Einstein bot with a registered external service is now as easy as adding an action to a dialog. You can add an external service action to your bot from Einstein’s Bot Builder.
Use Apex to Create a Callout to an External Service: Design and test the automation that sends a user’s information from Salesforce to the external employee banking system. Using the examples provided, create the variables for user phone numbers, and combine different phone numbers into one piece of data. Then use the external service action to create the user.
Invoke External Service Callouts Using Apex: You can call external service registrations natively from Apex. Make a callout to an external service like the Apex Http Class without the need to write boilerplate code. The registered services are strongly typed in Apex with the registration’s schema as Apex types. These Apex types reflect your registered service’s specification, making the Apex compiler do the heavy lifting for you.
Schema Update Support: You can register an updated schema version that includes supported changes to active and inactive components. This section provides details about whether changes are supported.
Asynchronous Callback Operations Using Apex: Use Apex to create, test, and monitor asynchronous callbacks. Callbacks are right for integrations that require potentially delayed responses of more than 120 seconds from an external source. For example, a mortgage application API, a shipping notification API, or a payment confirmation API.
Use Apex to Create an Asynchronous Callout to an External Service: When you register a schema containing a callback, External Services creates an invocable Apex operation with an automatically generated Apex class. Salesforce creates a callback URL on the asynchronous callout (initial callout) that’s read-only. Create an Apex client that’s capable of handling the callback by using the generated Apex interfaces. The client waits for an asynchronous response from the external system for an extended time (up to twenty-four hours).
How External Services Asynchronous Callbacks Work: External Services asynchronous operations are described in an OpenAPI 3.x compliant specification with a callback operation. Asynchronous operations are registered by the system as a special type of invokable action that allows for longer response times. In contrast, External Services synchronous operations time out after 120 seconds. With asynchronous operations, you use Apex to define the callback and the time out for the delayed asynchronous response.
Monitor and Debug Asynchronous Callouts: Asynchronous callouts are monitored as jobs using the Background Operations app or with Apex log lines in the Developer Console. To debug your code at runtime, use Apex log lines.
Use Agentforce to Invoke External Service Actions: Add capabilities to agents with customizable actions configured via External Services. Use External Services to declaratively connect your Salesforce org to an external API. After you register an OpenAPI schema, the actions defined in that schema become automatically available as custom agent actions.
Define a Charset in the Schema: To specify a charset for external callouts, populate the Content-Type header. A charset can be set if specifically defined in the schema.
Define an External Credential and a Named Credential: First, create an external credential to specify an authentication protocol and permission set or profile to use when authenticating to an external system. Second, in order for External Services to authenticate, create a named credential and specify it as the callout endpoint.
Edit an Operation Declaratively: To edit an external service's operation created by HTTP Callout, you can use the same declarative tools you used to create the HTTP Callout in Flow Builder.
Edit the Schema or Named Credential: To edit the details of an external service created by HTTP Callout, you can edit the schema directly, change the Description, or change the Named Credential.
Schema Examples: Explore various scenarios with OpenAPI 2.0 and OpenAPI 3.0 compliant JSON or YAML schemas supported by External Services. The examples cover schema elements like HTTP header as input parameters, and include example usage in Apex. Understanding the examples helps with proper syntax and code placement.
Track Usage and Limits: When you first enter External Services from Setup, five visual (flat) gauges at the top of the page show your current usage and maximum values for each per org limit.
View Actions: View actions available for an external service.
Media Type Mapping in External Service Registrations: You can register specifications with nonsupported consumes, produces, or OpenAPI 3.0 content media type directives by mapping the media types to supported media types. Specify a mapping from a dropdown menu on the registration screen, or provide the mapping with code by using Metadata API.
Register an External Service: Provide an API spec that describes your endpoint's services and methods. The API spec’s schema generates the external service operations with corresponding input and output parameters. You can also edit an exisiting registration, register an external service with a Mulesoft API, or register an external service using Flow Bulder's HTTP Callout functionality.
Defaults and Default Values: Learn about External Services' support for defaults. For OpenAPI 2.0, default values set on properties are used. For OpenAPI 3.0 schemas, the "outermost" default is used. Non-supported configurations are ignored.
Structure Data Using properties and additionalProperties: In an Open API specification, the properties keyword defines one or more properties on an object including the property name and data type. The additionalProperties keyword gives you the flexibility to add additional properties with an undefined schema. The named properties are accessible as Apex properties with a matching data type. The additionalProperties in the spec are accessible in Apex as a Map property.
Testing External Services: Test the example flow MyAtmFlow with a flow action calling the external service MyAtmExternalService by implementing the HttpCalloutMock interface. The interface provides a test response without performing the callout to the external service endpoint. The sample Apex unit test performs a mock test against the same HTTP callout mock implementation.
Update a Schema: For an existing External Services registration, you can update the current schema with a new version.
Manage External Services: Find services that you already registered, view actions for a service, edit, clone, and delete a service. You can update a registered schema version currently in use in flow or Apex, if the update includes supported components.
Apex FAQ: Frequently asked questions about external Web services, supported WSDL Schema types, and differences between a Apex classes and triggers.
Update Experience Cloud Site Membership Using the API: If you aren’t a member of an Experience Cloud site, you can’t access Experience Workspaces to update administration settings, including membership. As an alternative, you can use the API and Data Loader to add yourself and others to a site.
Can I use the same domain name for my Salesforce Sites and my Experience Cloud Sites?: With enhanced domains, your Salesforce org’s My Domain name is the subdomain for Salesforce Sites and Experience Cloud sites. If enhanced domains aren’t deployed in your org, you can’t use the same domain name for Salesforce Sites and Experience Cloud sites.
Feed-Based Layouts in Salesforce Classic: Feed-based page layouts make it easier to work with records by providing two separate views: one for the record’s feed, and one for its details, including related lists.
Test Syndication Feeds: Before you enable a feed for customers, test the feed definition.
Define Syndication Feeds: Syndication feeds give users the ability to subscribe to changes within Salesforce Sites and receive updates in external news readers. Simply by defining a SOQL query and mapping, you can syndicate changes to public data to your end users. You can create one or more syndication feeds for your organization's public sites or any Visualforce page. The syndication feed displays the records specified by a SOQL query. Users can subscribe to the feed and view the feed when they visit the site or page.
About Syndication Feeds: Syndication feeds give users the ability to subscribe to changes within Salesforce Sites and receive updates in external news readers. Simply by defining a SOQL query and mapping, you can syndicate changes to public data to your end users. You can create one or more syndication feeds for your organization's public sites or any Visualforce page. The syndication feed displays the records specified by a SOQL query. Users can subscribe to the feed and view the feed when they visit the site or page.
View Syndication Feeds: View the syndication feed definition, including what records are returned, and which data from the records is displayed.
Field Operational Scope: The fields displayed on the Fields Operational Scope page are referenced through the operational scope under these circumstances.
Default Field Values: Prepopulate field values with defaults to save your users time and improve consistency. Default field values make your users more productive by reducing the number of fields they must fill in manually.
Dependent Picklists: Use a dependent picklist to help your users enter accurate and consistent data. A dependent picklist is a custom or multi-select picklist for which the valid values depend on the value of another field, called the controlling field. A controlling field can be any picklist (with at least one and fewer than 300 values) or checkbox field on the same record.
Classic Encryption for Custom Fields: Restrict other Salesforce users from seeing custom text fields that you want to keep private. Only users with the View Encrypted Data permission can see data in encrypted custom text fields.
About Field Sets: A field set is a grouping of fields. For example, you could have a field set that contains fields describing a user's first name, middle name, last name, and business title.
Validation Rules: Improve the quality of your data using validation rules. Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record.
Roll-Up Summary Field: A roll-up summary field calculates values from related records, such as those in a related list. You can create a roll-up summary field to display a value in a master record based on the values of fields in a detail record. The detail record must be related to the master through a master-detail relationship. For example, you want to display the sum of invoice amounts for all related invoice custom object records in an account’s Invoices related list. You can display this total in a custom account field called Total Invoice Amount.
Custom Address Fields: Improve address data accuracy and the end-user experience with Custom Address Fields. Users can populate a custom address field manually or they can use the Google lookup to search for an address. Admins and APIs can access each address stored in a custom address field as a structured compound data type as well as individual address components.
Create a Custom Address Field: Use the Address field type to create a custom address field that mimics the behavior of standard address fields. For example, add a Warehouse Address field to a standard or custom object. Users can populate a custom address field manually, or they can use the Google lookup to search for an address. Then you can access each address that’s stored in a custom address field, either as a structured compound data type or as individual address components.
Enable Custom Address Fields: After you review the feature limitations and configure the State and Country/Territory picklists, enable custom address fields. Then you can add custom fields to standard and custom objects in Object Manager using the compound Address field type.
Considerations for Custom Address Fields: Before you enable custom address fields, configure State and Country/Territory picklists and review these considerations.
Clone Validation Rules: Create new validation rules quickly by using existing rules as your starting point.
Convert a Text Field to a Picklist Field: By default, an upper bound limit of 4,000 is applied to inactive unrestricted picklists for each field. If you exceed this limit when converting a text field to a picklist field, you get an error message.
Build Cross-Object Formulas in the Advanced Formula Tab: Create a cross-object formula when building a formula in the Advanced Formula tab or for approvals or rules, such as workflow, validation, assignment, auto-response, or escalation rules.
Building Cross-Object Formulas in the Simple Formula Tab: To create a cross-object formula when building a formula in the Simple Formula tab, enter the relationship names of the objects to which you are spanning followed by the field you want to reference. Separate the relationship names of each object and the field with periods.
Create a Global Picklist Value Set: Use a global picklist value set to share values across objects and custom picklist fields, and to restrict the picklists to only the values that you specify.
Create a Custom Picklist Field: Create custom picklist fields to let your users select values from lists that you define.
Deactivate, Reactivate, or Remove a Single Picklist Value: Deactivate, reactivate, or remove a value from a restricted or unrestricted custom picklist. If it’s a global picklist value set, these actions simultaneously update all custom picklists that inherit its value set.
Define Validation Rules: Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record. A validation rule can contain a formula or expression that evaluates the data in one or more fields and returns a value of “True” or “False”. Validation rules also include an error message to display to the user when the rule returns a value of “True” due to an invalid value.
Create a Roll-Up Summary Field: Define a roll-up summary field on the object that’s on the master side of a master-detail relationship.
Delete Picklist Dependencies: If you no longer want the values of a dependent picklist to depend on a controlling field, delete its dependency. Deleting the dependency removes the logic that defines how the values of the picklist depend on the controlling field, but doesn't delete the fields or affect their data.
Create and Edit Field Sets: Salesforce has a drag-and-drop WYSIWYG tool for creating and editing field sets The enhanced field sets editor is enabled by default, and provides all of the functionality of the original editor, as well as additional functionality and an easier-to-use WYSIWYG interface.
Establish a Picklist Upper Bound Limit: You can enforce an upper bound limit of inactive values on existing picklists. The limit is enforced on the inactive values of unrestricted, custom picklists whose numbers don’t exceed the allowable limit. By default, all new unrestricted picklists have an enforced limit of 4,000 inactive values.
Considerations and Guidelines for Capturing Gender-Related Data: Capturing demographic information boosts data quality, builds trust, and lets you personalize offerings to retain and attract new customers. But release of gender information could result in safety concerns for individuals or liability issues for your company. It’s important to classify your data correctly so that you can protect it.
Capture Gender-Related Data: Set up the Gender Identity and Pronouns fields on the Lead, Contact, and Person Account objects to record gender-related data. And, add nonbinary honorifics like Mx. to the Salutation picklist value list to keep the data in sync. You can customize aspects of these fields to suit the unique needs of your company.
Get a List of Custom Picklist Fields with Inactive Values: Get email notifications when custom picklist fields have more than 4,000 inactive values and then use this information to bulk delete the inactive unused values. This feature is available only for custom picklists with predefined values.
Lookup Filters: Improve user productivity and data quality with lookup filters. Lookup filters are administrator settings that restrict the valid values and lookup dialog results for lookup, master-detail, and hierarchical relationship fields.
Define Lookup Filters: Create and define lookup filters. Lookup filter criteria can compare fields of different types as long as they are compatible. Value-based filters are supported in Lightning Experience and Salesforce Classic.
Dependent Lookups: A dependent lookup is a relationship field with a lookup filter that references fields on the source object. For example, you can configure the case Contact field to only show contacts associated with the account selected in the case Account Name field.
Lookup Filter Examples: Various examples for record types, record status, roles, and complex configurations in lookup filters.
View a List of Lookup Filters for a Target Object: You can quickly see a list of all of the lookup filters that restrict the values of each target object. This is useful when creating similar filters for a target object. Also, lookup filters that reference fields on related objects count against the cross-object reference limit, which is the number of unique relationships allowed for a target object. The Related Lookup Filters list lets you see which lookup filters might impact that limit.
Manage Inactive Picklist Values: Establish upper bound limits, deactivate, reactivate, or remove a value from a restricted or unrestricted picklist.
Manage Deleted Custom Fields: Deleted custom fields and their data are stored until your org permanently deletes them or 15 days have elapsed, whichever happens first. Until that time, you can restore the field and its data.
Managing Validation Rules: Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record. A validation rule can contain a formula or expression that evaluates the data in one or more fields and returns a value of “True” or “False”. Validation rules also include an error message to display to the user when the rule returns a value of “True” due to an invalid value.
Manually Restore Attributes of Deleted Fields: Custom fields consist of several attributes that provide additional information about the field. Some of these attributes are not restored automatically after a field is undeleted and must be restored manually.
Merge Fields for Cross-Object Formulas: A Cross-object formula is a formula that spans two related objects and references merge fields on those objects.
Merge Fields for Formulas: A merge field is a field you can put in an email template, mail merge template, custom link, or formula to incorporate values from a record.
Merge Fields for Validation Rules: A merge field is a field you can put in an email template, mail merge template, custom link, or formula to incorporate values from a record.
Bulk Delete Inactive Picklist Values: Managing your inactive picklist values and enforcing limits on the number of inactive values for custom picklists can improve performance and the overall health of your Salesforce org. If you have a picklist with a large number of inactive unused values, you can bulk delete them.
Protect Picklist API Names for Formulas and Integrations: When you create a picklist value, an API Name that matches the Label is assigned. By default, the API Name can be changed at any time, but you can choose to protect the API Name.
Make Your Custom Picklist Field Values Global: When you create a custom picklist, it’s only available to the current object. To share the values with other objects, promote the picklist to a global value set. The original custom picklist references the global value set for its values, and the global value set is also available to other custom picklists.
Purge Deleted Custom Fields: Custom fields you delete from an object are removed from the object but remain in the system for 15 days until they’re hard deleted automatically by Salesforce. During that time, the deleted custom fields continue to count toward your custom field allocation. When your org reaches 75% of its custom field allocation and it has custom fields that are ready to hard delete, Salesforce displays the Purge button. You can use it to initiate the hard delete process and free up custom field allocation for your org before the hard delete takes place.
Find Where a Field Is Used: Find out where a custom field is referenced, such as in a formula or Apex class, with a click of the Where is this used? button. You can see where a field is used and where changes to the field appear before you edit it.
Define a Field as Required Using Field Sets: You can define a field as required when you create or edit field sets. You may want to define a field as required to ensure a user enters the necessary information on a field.
Rich Text Area Field Considerations: Learn considerations for Rich Text Area fields, including where you can use them, their character limits, and how Salesforce returns and handles content.
Considerations for Universally Required Fields: A universally required field is a custom field. It must have a value whenever a record is saved within Salesforce, the Lightning Platform API, Connect Offline, Salesforce for Outlook, the Self-Service portal, or automated processes such as Web-to-Lead and Web-to-Case. Review the following considerations before making your custom fields universally required.
Useful Default Field Value Formulas: How to apply default field values based on maximum discount rate, product language, or tax rate by city.
Examples of Validation Rules: Review examples of validation rules for various types of apps that you can use and modify for your own purposes. Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record.
Sample Account Validation Rules: Validation rule examples for numeric account numbers, account number length, and annual revenue range.
Sample Call Center Validation Rules: Validation rules for requiring a conditional description, preventing cases from being reset, restricting case status, and more.
Sample Date Validation Rules: Examples for date validation rules. For example, how to validate that the value of a custom field is a weekday, a Saturday or Sunday, that a custom date field contains a date within the current month and year, and more.
Sample Number Validation Rules: Examples for how to validate that users can't save a time card record with more than 40 hours in a work week, numbers can't be negative, and even or odd numbers.
Rich Text Editor: Use the rich text editor to format text in custom fields with the rich text area type. You can also use the rich text editor in many other features, such as Chatter publisher and groups.
Use the Field Dependency Matrix: The field dependency matrix lets you specify the dependent picklist values that are available when a user selects each controlling field value. The top row of the matrix contains the controlling field values, while the columns list the dependent field values. Use this matrix to include or exclude values. Included values are available in the dependent picklist when a value in the controlling field is selected. Excluded fields aren’t available in the dependent picklist for the selected controlling field value.
Validation Rule Considerations: Validation rules verify that the data a user enters in a record meets the standards you specify before the user can save the record. A validation rule can contain a formula or expression that evaluates the data in one or more fields and returns a value of “True” or “False”. Validation rules also include an error message to display to the user when the rule returns a value of “True” due to an invalid value. Review these considerations before implementing validation rules in your organization.
View Active and Inactive Picklist Values: You can view the number of active and inactive picklist values and the maximum number allowed from the picklist field detail page.
Common Formula Errors: Review common errors that can occur with formulas and how to fix them.
Automate Tasks with Flows: Automation reduces repetitive work and helps your team complete tasks faster and more accurately. With Flow Builder, you can build simple or complex automations, forms, and guided experiences with no code. You can add forms to Salesforce pages and Experience sites, and launch flows using buttons, record triggers, or schedules.
Start a Flow from a Quick Action: With this feature, users can run a screen flow with the click of a button on a Lightning record page. Create a quick action on an object and configure it to run an active screen flow. Then, add the quick action button to the Lightning record page layout.
Build a Flow: After you model the process that you want to automate, design and build the flow in Flow Builder.
Sending Emails from a Flow: Send emails to your customers, partners, and employees automatically in a flow. There are several different ways to send an email from a flow depending on who you want to send your email to and how you want your email content to look. Determine the best way to send your email based on the functionality that you need.
Creating Flow Formulas: Flow formulas help make your flows more dynamic by performing calculations, manipulating data, and making decisions based on field or variable values. Formulas can facilitate conditional logic, taking the flow down different paths based on criteria
Creating Flow Formulas with Agentforce (Beta): Save time by using generative AI to build formulas in Flow Builder. Simply describe your formula and let Agentforce figure out the functions and operators.
Working with Data in a Flow: The real power of a flow is that it can automate updates to your data, whether the data lives inside your Salesforce org or in an external database. In a flow, you can look up values from records, connect to external systems, create records, update records, and delete records.
Creating a Salesforce Record from a Flow: To create a Salesforce record, use the Create Records element. You can also use a Quick Action element of type Create, but it has limited functionality.
Connecting with External Systems and Data: With a Get Records element, you can easily look up your Salesforce data in a flow. But what if you need data that lives outside of Salesforce? Connect your flow to external systems using built-in Salesforce features such as MuleSoft for Flow: Integration connectors, HTTP callout actions, API Catalog, or by using MuleSoft RPA processes as external services. To extract data from documents, use MuleSoft for Flow: IDP
Update Salesforce Records from a Flow: To update field values on existing Salesforce records, use either the Update Records element or a Quick Action core action. The right element depends on what the rest of your flow is doing.
Add and Edit Elements: Use elements to define actions that the flow can run. When they’re on the canvas, connect them to create the order in which they run.
Example Instructions for Drafting Flows with Agentforce (Beta): Use Agentforce for Flow to create accurate draft flows by providing clear, detailed instructions about your requirements. Base your instructions on example patterns that describe when the flow starts and what actions it should take.
Retrieve Opportunities for a Selected Account Example: This example creates a screen flow that lets users select an account, trigger a flow to retrieve related opportunities, and instantly display the results in a table—all within a single screen.
Extend Your Flow-Building Options: Sometimes your flow has to do more than what Flow Builder provides out of the box. You can extend flows by calling Apex classes or adding Lightning components.
Let Flows Execute Apex Actions: Flow Builder provides many capabilities, but sometimes your flow requires functionality beyond the default elements. In that case, call an Apex class from your flow by using an Apex action.
Extend Flows with Lightning Components: To build a richer flow screen, add Aura components or Lightning web components to your flow. To perform an action without going through the server, add Aura components to your flow.
Invoke a MuleSoft RPA Process in a Flow: After you make a MuleSoft RPA process available to flows, you can start and check the status of the process from a flow.
Drafting Flows with Agentforce (Beta): Save time by describing what you want to automate and letting Agentforce draft a flow and get you started with your automation.
Customize What Happens When a Flow Fails: Learn how fault paths customize what happens when a flow fails. Choose how to notify admins, guide users, and take a follow-up action.
Default Flow Error Handling: Understand how flows behave when they fail to help you decide on error handling strategies. Learn what happens by default so you can determine if you need custom error handling for your specific use case.
Configure Every Fault Path to Send You an Email: As a best practice, we recommend configuring the fault connectors in your flow so that you always receive an email when a flow fails. In the email, include the current values of all your flow’s resources. The resource values can give you insight into why the flow failed.
Other Examples of Error Handling in Flows: Examples of using fault connectors to handle flow errors include requesting corrections from the user and bypassing the error.
Move and Connect Elements to Change a Flow Route: Identify which elements the flow runs and in what order by connecting the elements on your canvas together. To change the run order, move elements and add or remove connectors.
Transform Data in a Flow: Automate how you transform data between Salesforce and an external system using the Transform element. You can create mappings between the source and target data, or set fixed values for the target data.
Make a MuleSoft RPA Process Available to Flows: Configure the connection between MuleSoft Anypoint platform and your org to import MuleSoft RPA APIs. Then, register the APIs as an external service to use them in flows.
Make Your Screen Elements Dynamic with Reactivity: Use supported flow screen components, formulas, and screen actions to update screen components in real time without leaving the screen. With this reactivity, you can build screens that feel like single-page applications and reduce the number of screens that users have to navigate to complete tasks. This reactivity is supported with API version 59.0 and later.
Reactive Screen Flow Components: Not all screen flow components support reactivity. Review which components do and any limitations that apply.
Considerations for Reactivity in Screen Flows: Review these considerations before you set up reactivity in your screen flows. Reactivity is supported with API version 57.0 or later.
Run Active Screen Flows from Slack: You can invoke an active screen flow using an action, a Slack shortcut in a custom Slack app, or a button in a Slack view.
Save a Draft of Your Flow as You Build: You can interact with your flow while an element is open and access the toolbar while editing that element. And you don't need to finish configuring an element before saving your flow.
Send a Flow to Run in Slack: An active screen flow with the Make Available in Slack advanced setting can run in the flow default environment. To send a Slack message that contains a button to run that flow to a Slack channel or group direct message, create another flow that contains an action.
Showing Users Their Progress in a Screen Flow: Keep your users informed about which stage they’re in and how far they’ve progressed in a screen flow. Create stages to designate steps in the flow, and use a progress indicator to show all the stages and highlight the stage that the user is in.
Create Flow Stages: After you plan the stages for each path of your flow, configure the stages so that they show up in a progress indicator on your flow’s screen elements that your users can see.
Planning the Stages of Your Flow: Progress indictors show your flow stages to the running user. Before you start adding stages to your flow, plan for all the possible stages that you want your running users to see in a progress indicator.
Control Which Stages Show in Your Progress Indicator: After you set up your flow's progress indicator, configure how stages appear as users move through the flow. Show the same stages throughout, add or remove stages based on the path the flow takes, or update the highlighted current stage between screens.
Set Up a Progress Indicator for Your Flow: Progress indicators show users where they are in flows. Use the standard progress indicator for a quick setup, or build a custom component for a tailored experience. To get started, turn on the progress indicator for a screen flow.
Use Flows with Slack: Build a screen flow that’s designed to run in a Slack conversation or direct message group. Use another flow, a Slack shortcut, a slash command, or a button in a Slack view to run a flow from Slack.
Flow Builder Keyboard Shortcuts: Use these handy keyboard shortcuts for macOS and Windows to quickly navigate flows and edit elements on the canvas.
Apex-Defined Data Type: With the Apex-defined data type, flows can manipulate the kinds of complex data objects that are typically returned from calls to web services. Create Apex-defined variables in flows and directly process JSON returned from web calls.
Building Blocks of Flows: Flows are built from three core components: elements, connectors, and resources. Elements represent actions that flows run, such as reading or writing Salesforce data. Connectors define the paths that flows can take at run time. Resources represent values that you can reference throughout a flow.
Flow Bulkification in Transactions: When a flow runs for multiple records at the same time, Salesforce creates one flow interview per record. Bulkification groups similar operations when interviews for the same flow reach the same element, helping the transaction use fewer queries and statements.
Flow Environments: A flow environment specifies where a flow can run. For example, if a flow is associated with the Slack flow environment, you can enable users to launch the flow from Slack.
Understanding When a Screen Flow Finishes: Screen flows restart automatically when finished, redirecting users to the first screen. Override this behavior by adding local actions or configuring distribution settings like retURL parameters.
API Version for Running a Flow: Some run-time behavior improvements are delivered as versioned updates, so that you can control when each flow adopts those updates. Test and upgrade your flows one by one and at your own pace. You can even opt to never adopt versioned updates for one or all your flows.
Testing Your Flow Before Activation: Test your flow before activation to catch errors, verify every path, and prevent data issues. Depending on the flow type, use Test Mode or the Flow Builder debugger to test different scenarios with sample data.
How Flows Run in Transactions: Flows run within transactions that group operations as a single unit. When any operation fails, the entire transaction rolls back to maintain data integrity. This includes Apex triggers, escalation rules, and all flow interviews in the transaction.
Triggered Flows: In the Start element of a triggered flow, you can specify what starts a flow. For example, the flow trigger can be a schedule or the new and changed records of a specified object. Without a trigger, you need to set up other things to launch the flow, such as custom buttons, processes, Apex classes, or even Einstein Bots.
On-Demand Flows: On-demand flows are triggered by REST API calls. For example, create an automation to send your customer an SMS message that triggers after a user signs up for a membership program, or after the user clicks a button on your site.
Create a Reusable Template-Triggered Prompt Flow Example: This example creates a sample flow that's available to all prompt templates. Multiple prompt templates can use a single, well-maintained flow for data processing, so this approach saves time, ensures consistency, simplifies development, and improves the reliability of AI-generated outputs.
Before-Save Record-Triggered Flows: Creating or updating a record can trigger a record-triggered flow to make additional updates to that record before it's saved to the database. A record-triggered flow can update a Salesforce record 10 times faster than a record-change process. Configure the record trigger in the Start element of your record-triggered flow.
Schedule-Triggered Flows: A schedule-triggered flow starts at the specified time and frequency for a batch of records. Configure the schedule trigger in the Start element of your autolaunched flow.
Scheduled Paths: Use scheduled paths in record-triggered flows to run some elements on a different path at a scheduled time. You can base the scheduled time on the record-triggering event or on a date or date/time field in the record.
Flow Types: A flow's type determines which elements and resources you can add and how you can distribute the flow. For example, you embed a screen flow on a page to gather information from visitors; or you distribute an autolaunched flow by using a custom button that users click to run the flow in the background. Similarly, you can add a Custom Error element only in a record-triggered flow, whereas you can add a Choice resource type only in a screen flow.
Flow Limits and Considerations: When designing, managing, and running flows, consider the permissions, use limits, and data issues.
Change Set Considerations for Flows: Before you use change sets to deploy a flow, understand the limits and behaviors that are related to component dependencies, deployment, and flow triggers.
Flow Builder Considerations: When you create a flow in Flow Builder, familiarize yourself with its limitations and behaviors. For example, Flow Builder supports only a few locales. Because of intellectual property protection, you can’t open flows installed from managed packages, unless the flows are templates.
Flow Formula Considerations: When you create a formula resource or add validation to a screen input component, understand the behavior of formulas in flows.
Two-Column Flow Considerations: If your org has Lightning runtime enabled, you can control whether a flow displays in one column or two columns. Before you use this feature, understand how the flow layout currently behaves.
Multi-Select Resource and Screen Field Considerations for Flows: Checkbox Group, Multi-Select Picklist, and Choice Lookup screen components let flow users select multiple choices. Before you start using these screen components, understand how they work in flows—both when you design the flow and when your users run it.
Flow Feature Considerations: When designing flows, keep these flow feature considerations in mind. Also, some resources, elements, and screen components have more considerations that are described in their reference topics.
Automated Flow Testing Limits and Limitations: Understand the limits and limitations of automatically evaluated flow test scenarios, whether you test through Flow Builder's Test Mode or with a Data Cloud-triggered flow.
Flow Variable Considerations: Before you create a variable resource, understand the behavior of variables in flows.
Flow Limits per Org: Review per-org, per-interview, and marketing flow limits, including limits for flow versions, active flows, scheduled interviews, and heap size.
Per-Transaction Flow Limits: Salesforce strictly enforces limits to ensure that any runaway flows don't monopolize shared resources in the multitenant environment. Per-transaction limits, which Apex enforces, govern flows. If an element causes the transaction to exceed governor limits, the system rolls back the entire transaction. The transaction rolls back even if the element has a defined fault connector path.
Considerations for Packaging Flows: You can include a flow in a managed or unmanaged package. Before you create, update, or deploy a package that contains a flow, understand the limitations and behaviors of packages.
Read-Only Field Restrictions for Flow Record Processing: Fields the running user can't edit are inaccessible to the flow during record creation and updates. This happens when the user lacks field-level permissions or when the field is a system field.
Control What Happens When a Flow Tries to Set Values for Read-Only Fields: When a flow tries to perform an action, such as create or update records, it uses a flow request to set values for specific fields. But what happens if the running user doesn’t have edit access to all those fields? When you use a record variable or record collection variable in Create Records and Update Records elements, that’s up to you. To control the behavior, select or deselect the Filter inaccessible fields from flow requests preference.
Fix Read-Only Field Errors in Flow: Troubleshoot flows that try to update fields that the running user doesn't have edit permissions for.
Flow Operations and Read-Only Fields: Understand when flows have read-only access to field values. You can control the behavior when a flow tries to update a read-only field and remove read-only field values from flow operations.
Aura Component Runtime Considerations for Flows: Aura components in running flows can behave differently than expected. Review Aura component behavior by distribution method before deployment.
Record-Triggered Flow Considerations: A record-triggered autolaunched flow makes additional updates to the triggering record before or after it’s saved to the database. Understand the considerations and special behaviors of flows that make before- and after-save updates.
Schedule-Triggered Flow Limits and Considerations: A schedule-triggered flow starts at a specified time, runs on a specified frequency, and processes a batch of records. Review these considerations, limits, and special behaviors before creating or activating a schedule-triggered flow.
Flow Usage-Based Entitlements: Like feature licenses, usage-based entitlements don’t limit what you can do in Salesforce; they add to your functionality. If your usage exceeds the allowance, Salesforce contacts you to discuss additions to your contract. In the meantime, your flow interviews run as usual.
Distribute a Flow: After you’ve designed and tested your flow, it’s time to put it to work! Flows can be run in several ways, depending on who the flow is designed for. Internal users, external users, or systems can run a flow, or a flow can be deployed for another organization.
Activate or Deactivate a Flow: You can activate or deactivate a flow from the Automation app Flows tab or the Flow Builder canvas.
Flow Distribution Concepts: Understand which users can run your flow, what data your flow can access, and how your flow looks in Classic and Lightning Experience.
Flow Run Context: Flows run in user context or system context. For a flow running in user context, the running user’s profile and permission sets determine the object permissions and field-level access of the flow. For a flow that runs in system context, whether it runs with or without sharing determines its data access. Understanding context helps you control what your flows can read and update on behalf of your users.
Data Safety When Running Screen and Autolaunched Flows in System Context: Screen flows and autolaunched flows without triggers can expose more data than intended. This potential issue primarily affects Experience Cloud sites accessed by external users. Configure proper user permissions for field-level and record-level security instead of running flows in system context. When system context is necessary, use only the minimum fields and records required.
Distribute Flows to Other Orgs: Flows can be included in Lightning Bolt Solutions, change sets, and packages. The recipient org of the solution, change set, or package must have flows enabled.
Deploy Processes and Flows as Active: By default, processes and flows that are active in a sandbox or non-production org are deployed to a production org as inactive. After deployment, manually reactivate the new versions. In production orgs, you can enable the setting to deploy a new active version of a process or flow via change sets or Metadata API. If you use a continuous integration and continuous delivery model to deploy metadata changes, enable the option to deploy processes and flows as active.
Distribute Flows via Lightning Bolt Solutions: To distribute automated business processes or bootstrap an Experience Builder site with a complete solution or new look, create a Lightning Bolt Solution. A Lightning Bolt Solution can include flows, custom Lightning apps, or Experience Builder templates or pages. Before you create a solution, group flows that you want to include in a flow category.
Distribute Flows to Users Outside Your Org: Let external users run your flow by adding the flow to an Experience Builder site, an external app or page, or an Embedded Service deployment. For finer control over how your flow behaves in external contexts, use a custom Aura component or Visualforce page. Flows in custom Aura components use Lightning runtime, and flows in Visualforce pages use Classic runtime.
Add a Screen Flow to an Authenticated Experience Cloud Site: To add a screen flow to a page on your authenticated Experience Cloud website, use an Experience Builder Flow component. Use this method if you have a customer portal or other website that requires users to log in to use.
Add a Screen Flow to a Public Experience Cloud Site: Create an Experience Cloud site that's available to everyone and add a flow component to a page in the site and select an active screen flow. You can link to the flow page from your company's website. Use this method to share flows with external users who don't have a Salesforce license, such as customers, partners, or other external users. Because users aren't logging into your site, you don't need to purchase Experience Cloud licenses.
Distribute Flows to Users in Your Org: Enable your internal users to run your flow through a custom action, the flow URL, a Lightning page, a Visualforce page, or a custom Aura component.
Run a Screen Flow From a Quick Action: Add a button to a Lightning record page that starts an active screen flow. Send the entire record or the record ID to the flow. Use a quick action to setup the button.
Add a Flow to the Actions & Recommendations Component: Want to use your flow to guide users through complex business processes in Lightning console or standard navigation apps? Associate the flow with records by using a process to create a RecordAction object, or by creating an Actions & Recommendations deployment. Then add the Actions & Recommendations component to your Lightning pages using the Lightning App Builder.
Embed a Flow in a Custom Aura Component: To customize how your flow gets and receives data, add it to a custom Aura component. Then distribute that component through a custom action, Lightning tab, or Lightning page.
Set the Runtime Experience for URL-Based Flows: Are you distributing a flow via a URL? That includes things like direct URLs, custom buttons, and links in Setup. You can flip one switch to upgrade all those flows to Lightning runtime.
Additional Options for Launching a Flow Using its URL: If you're using your flow’s web address (URL) to share your flow, you can customize what happens when the flow ends, and you can send variable values to the flow in the URL.
Choosing Between Lightning and Non-Lightning Flow URL Formats: When you run a screen flow from a URL, you can choose between using Lightning or the non-Lightning URL format, which uses Lightning Out. We recommend using Lightning for a faster, more consistent experience. However, there are times when you need to use the non-Lightning format.
Customize a Flow URL to Control Finish Behavior: By default, after a user finishes a screen flow, the screen flow redirects the user to the first screen. If you want to redirect users to another page within Salesforce when they click Finish, use the retURL parameter in the flow URL.
Add a Flow to a Utility Bar: Want your flow to be accessible from any page in your app? Add it to the utility bar in your Lightning app. The utility bar gives your users quick access to commonly used tools.
Embed a Flow in a Visualforce Page: To customize your flow’s look and feel for internal users, add the flow to a Visualforce page. Then distribute that page through a Visualforce tab, custom button, or custom link.
Customize a Visualforce Component to Control the Flow's Finish Behavior: By default, users who click Finish start a new interview and see the first screen of the flow. After you embed a flow in a Visualforce page, configure the finishLocation attribute to route users to another page in Salesforce.
Lightning Runtime vs. Classic Runtime for Flows: Depending on how a flow is distributed, users see either the Classic runtime or Lightning runtime UI when they run the flow. Like its name suggests, Lightning runtime looks and feels like Lightning Experience.
Limit User Access to Run Flows: Limit which users can run flows based on their user record, profile, or permission set. To apply more granular security to an individual flow, override the default behavior, then grant access to that specific flow based on user profile or permission set.
Distribute Flows to Automated Systems: Some flows don't require any user interaction to start. To enable a system to automatically launch a flow you can use the start Apex method.
Start a Flow from Apex: Flows started from Apex can include complex business logic and enhanced error handling, and can integrate with external systems more effectively. This approach promotes reusability by encapsulating logic within flows that can be called as needed. It also provides greater control over execution context and order of operations. The combination of Apex and flow helps you create more powerful and flexible apps that are easier to maintain.
Set Flow Run Context: Override the default run context of a flow to control what data it can access. Run a flow in system context with or without sharing, or enforce user-level access regardless of the caller.
Launch a Flow from a Process: Just like workflow rules, processes start when a certain object’s records are created or edited. Add a flow action to give a process even more functionality. For example, create a process that checks if a new feed item is a question. If it is, wait a day and then use a flow to check whether a Best Comment has been selected or not. If it hasn’t, use that question to create a case.
Start a Flow from REST API: Use a REST call to run an autolaunched flow by using the invocable action endpoint and setting the path to flow. For example, you can run a flow from a non-Salesforce application or piece of code. The flow retrieves data from Salesforce and returns it as an output variable in your REST call.
Launch a Flow from a Workflow Action: Create a flow trigger workflow action to launch a flow from workflow rules. With flow triggers, you can automate complex business processes—create flows to perform logic, and have events trigger the flows via workflow rules—without writing code. For example, your flow looks up and assigns the relevant entitlement for a case. Create a flow trigger to launch the flow whenever a case is created, so that all new cases are automatically set with a default entitlement.
Define a Flow Trigger: After you create an autolaunched flow, create a flow trigger to launch that flow as part of a workflow rule.
View and Restore Flow Version Edit History: Review a history of saves for the current flow version and restore the flow to an earlier save. Each time you save a flow, a save instance is added to the version edit history. Save instances show the date, the user who saved the flow, and a summary of elements added, edited, or deleted.
Add Records from User Input in Screens Using Repeaters Example: This example uses a screen flow with the Repeater component to gather information from users at run time. You can collect data for multiple items in a group. The Repeater component has one or more child components. The values in these components can be prepopulated on the screen at run time. Users can update, delete, and add values for the group. The changes from the user interaction can be also be committed to Salesforce records.
Creating Flow Formulas with Flow Formula Builder: You can use Flow Formula Builder to build an expression in Formula-type resources or in the Collection Filter or Start elements of a record-triggered flow. To build your expression, select from a list of functions and operators. To catch errors as you work, check the formula syntax for each expression.
Get Started With Flow Builder Learning Map: Whether you’re new to automation or a seasoned expert, when you’re building an automation project, you have a business problem to solve. And after you solve it, measure success and maintain the solution. If you’re looking to create automations in your Salesforce org, this learning map focused on Salesforce Flow products helps you get started with information, resources, and product and feature content.
Connecting to an API Without a Connector Using HTTP Callout: Use HTTP Callout to connect flows to external APIs without coding, eliminating the need for developers or middleware tools. Flow Builder automatically generates external service registrations and Apex classes when you configure the action. Use the API response data as input in Salesforce.
Configure an HTTP Callout Action: HTTP Callout guides you through entering the details about the HTTP web-based service or REST API endpoint that you're connecting to. After you complete the configuration, you invoke the action in a flow. HTTP Callout assumes that you're familiar with the API that you want to call.
Configuring an HTTP Callout Action: Connect Flow Builder to an HTTP-based API without using code. To establish a connection between the API and Salesforce, you create an external credential and a named credential in Setup. Then, HTTP Callout guides you through describing the functionality of your API and the endpoint that you’re connecting to. Based on the information that you enter, Flow Builder generates an external service with a corresponding invocable action that you can use across Salesforce.
Delete an HTTP Callout Action: To delete an HTTP Callout action, you delete the external service registration record. If an external service registration and HTTP Callout action are referenced in any flows, you can’t delete them.
Guidelines for Authenticating HTTP Callout Actions: Before you configure an HTTP Callout action within Flow Builder, set up a named credential to authenticate requests to the external system. From Setup, follow these guidelines to create a permission set, auth provider, external credential, and named credential, in that order; then grant users access to the User Credentials object.
Manage HTTP Callout Actions: When you create an HTTP Callout action in a flow, Flow Builder creates an external service object and an invocable action object. Anyone with permissions in your org can reuse the invocable action in Flow Builder and across Salesforce.
Update an HTTP Callout Action Configuration: To update the configuration of an HTTP callout action, edit it from the External Services page in Setup. For example, update a path URL, keys, or a JSON sample. After you create an HTTP callout action from Flow Builder, you can reuse it in another flow or across Salesforce via Apex, Einstein Bots, or quick actions.
Flow Interviews: A flow interview is a running instance of a flow. A flow is an application built by your administrator that asks you for inputs and does something in Salesforce based on those inputs.
Delete a Flow Interview: If you paused a flow interview and don’t plan to resume it, delete it. By removing unnecessary flow interviews, you make sure that your pending list includes only flow interviews that you still plan to act on.
Pause a Flow Interview: If your administrator has configured a given flow to do so, you can pause its interviews. Pausing is useful, for example, when a call with a customer drops or the customer can't find their account number and plans to call you back.
Resume a Flow Interview: If you paused a flow interview, resume it after you have all the necessary information. If you pause a flow interview and the associated flow is updated before you resume, the resumed flow interview doesn’t use the updated flow. Instead, it uses the version of the flow that was active when you paused.
Planning Your Switch to Flow Builder: Workflow Rules and Process Builder are no longer the preferred tools for automating your business processes. With their pending retirement, now is the time to go with Flow Builder as the future of automated processes. Flow Builder is a foundation for the future and offers built-in extensibility, application lifecycle management, and faster performance.
Switch to Flow Builder Learning Map: Flow Builder combines the capabilities of workflow rules and Process Builder in a single point-and-click tool, making it easier to create a triggered process. If you created triggered processes with workflow rules or Process Builder, use the Migrate to Flow tool to move them to Flow Builder. Start by migrating and testing in a sandbox environment before moving your new flows to production.
Managing and Monitoring Flows: Monitor your org’s usage of flows and processes. See a list of paused interviews and scheduled actions from processes. Control who can view and how they view monitoring information for flows and processes.
View Flow Run for Individual: Trace an individual's actual execution path through a completed flow run to troubleshoot issues, understand personalization outcomes, or investigate specific customer experiences.
Control Your Views of Flows, Paused Interviews, and Scheduled Actions: You have two options for viewing flows, paused flow interviews, and scheduled actions from processes. We recommend using the enhanced option that you get by default. But you can switch to the other option, for example, to use a custom list view that you haven’t recreated with the enhanced option.
Add the Automation Usage Component to View Flow Dependencies: The Automation app shows the automations that a flow version uses and the automation versions that use a flow. The Automation app uses the default Flow Version and Flow pages to show this information. If you customized either page, add the Automation Usage component and save the updated page as your org default.
View Embedded Element Analytics and Detailed Insights: For active and previously run automation event-triggered, activation-triggered, and segment flows, element run data appears on the flow canvas. Access more detailed performance metrics on the element's Analytics tab, including engagement metrics for messaging flow elements across Email, SMS, WhatsApp, and RCS.
View Flow Version Analytics: Monitor overall flow version performance with comprehensive analytics showing run statuses, individual progression, and detailed execution data in summary dashboards.
Determine Flow Usage in Automation Versions: Flow approval process versions and orchestration versions rely on flows to run steps and evaluate complex conditions. Flow versions can use another flow from a Subflow element or an Action element. To understand the relationships between the automation versions that use a flow, view the Usage tab of the Flow page in the Approvals app.
View Flow Dependencies in the Automation App: Flow versions can call other flows from a Subflow element, and they can call flows and flow approval processes from an Action element. Flow approval process versions and orchestration versions rely on flows to run steps and evaluate complex conditions. To understand the relationships between a flow and the automations that it calls and that call it, view the Usage tab of the Flow Version page or the Flow page in the Automation app.
Determine Automation Usage in a Flow Version: Flow versions can use other flows from a Subflow element, and they can use flows and flow approval processes from an Action element. To understand the relationships between a flow version and the automations that it uses, view the Usage tab of the Flow Version page in the Approvals app.
Let Users Pause Flow Interviews: When users can’t finish a flow interview, give them the option to pause it for later by customizing your org’s process automation settings. For example, a customer service representative can pause an interview when the customer doesn’t have all the necessary information.
Viewing Paused Flow Interviews: You can view paused flow interviews on the Home page, the navigation menu in the Salesforce mobile app, or in the Automation app. You can resume paused flow interviews with a single click.
Prepare Your Org for Paused Flow Interviews: A flow interview is a running instance of a flow. Not every flow interview can be completed in one go. Add the Pause button to your flows, so that users can pause flow interviews for later. Update the sharing model for flow interviews, so that other users can resume a paused interviews. And make it easy for users to resume interviews by adding a component to their Home page.
Flow Elements: An element represents an action that the flow can run. Examples include reading or writing Salesforce data, displaying information and collecting data from flow users, runnning business logic, or manipulating data.
Action Element: Launch an action that's available in Salesforce by adding an Action element to your flow.
Activities: Match Email to Records Actions: The Activities: Match Email to Records flow provides several core actions for matching emails to relevant records in your Sales org. To add one of these actions to your flow, make sure that Sync Email as Salesforce Activity is enabled in Einstein Activity Capture. In Flow Builder, add an Action element. Then select Activities: Match Email to Records, and search for the appropriate action.
Create Email Activity with Associations Action: This action creates activity and email message entity records from temporary email records and associates them with specified account, contact, lead, opportunity, and user records. To be used in the Activities: Match Email to Records flow. Requires that Sync Email as Salesforce Activity is enabled in Einstein Activity Capture.
Get Account and Opportunity from Email Addresses Action: This action gets an account record associated with a contact or unmatched email address and also gets an opportunity record related to a contact. To be used in the Activities: Match Email to Records flow. Requires that Sync Email as Salesforce Activity is enabled in Einstein Activity Capture.
Get Contacts and Leads from Email Addresses Action: This action matches email addresses to contact and lead records related to active user records. To be used in the Activities: Match Email to Records flow. Requires that Sync Email as Salesforce Activity is enabled in Einstein Activity Capture.
Get Users from Email Addresses Action: This action gets user records with email addresses that match those addresses in the To, From, or CC address field of a sent email captured by Einstein Activity Capture. To be used in the Activities: Match Email to Records flow. Requires that Sync Email as Salesforce Activity is enabled in Einstein Activity Capture.
Submit for Approval Action: Submit one Salesforce record for approval using Classic Approval Processes. This action doesn't submit a record for approval using Flow Approval Processes.
Post to Chatter Action: This action posts a message to a specified feed, such as a Chatter group or a case record. The message can contain mentions and topics, but only text posts are supported.
Einstein Discovery Action: Get predictive and prescriptive intelligence directly in your flows with Einstein Discovery-powered models. Select the row or fields to use for your predictions and let Einstein Discovery generate predictions, suggested ways to improve predicted outcomes, and other details.
Explore Conversation Action: Answer users' questions about voice or video calls based on the contents of a call transcript.
Get Forecast Context Action: Get forecast context for a specific user. To be used in the Forecast Guidance flow as part of the Get Forecast Guidance standard agent action.
Get Forecast Opportunities Action: Get forecast opportunities for a user that matches the specified criteria. To be used in the Forecast Guidance flow as part of the Get Forecast Guidance standard agent action.
Generate User Data Action: Generate placeholder values for fields that are required to create a user record. Use this action in authentication provider user registration flows if the identity provider doesn’t give you enough information to create a user.
Get Assessment Response Summary Action: Create a printable summary view of assessments taken. This action enables you to extract responses saved in an assessment and create a flow to generate a document.
Get Conversation Intelligence Action: Get intelligence information about a voice or video call, including any insights and a conversation summary.
Get Record Prioritization Data Action: Get record data and field metadata to prioritize records for a user. This action is used in the Get Opportunity Details flow as part of the Prioritize Opportunities standard agent action.
Get User Data from JSON String Action: Retrieve the value of a specific attribute from a JSON object that has been serialized into a string. Use this action to retrieve user information from the user info response or ID token during authentication provider user registration flows. Then, create and update user records with the user information that you retrieved from this action.
Provided Flow Core Actions: Perform an action outside of the flow. Choose from Salesforce-provided actions, like Submit for Approval or Send Email, or from your org’s quick actions and local actions. To add one of these actions to your flow, add an Action element. Then, in the Action field, search for the appropriate action.
Lock Record Action: Locks or unlocks a workflow-enabled or approval-enabled record for editing during an approval and specifies who can edit the record while it's locked.
Open a Page Action: Opens a Salesforce or external page in the user's browser during a screen flow.
Global or Object-Specific Action: Call an object-specific or global action that’s already been configured in your org. Only Create, Update, and Log a Call actions are available.
Quip Flow Core Actions: Quip provides several core actions for organizing, creating, and copying your Quip content in flows. To add one of these actions to your flow, add an Action element. Then select the Quip category, and search for the appropriate action.
Copy Quip Document Action: To use a document as a template, create a copy. By default, copied documents are added to the running user’s Private folder in Quip.
Edit Quip Document Action: Edit content in a document, spreadsheet, or slide. Add or replace content based on a document section.
Export Quip Document to PDF Action: Export a Quip document to PDF to mark it as complete and to keep a copy for your records. You can attach the exported PDF to a Quip document or to a Salesforce record.
Copy with Live Paste Action: Copy content from a source Quip document and paste it to a new document with Live Paste. When the source content is updated, Quip documents with the live pasted content also update.
Send Conversation Messages Action: Send a messaging component to one or more messaging users in an enhanced messaging channel or Enhanced In-App Chat.
Send Custom Notification Action: Send a custom notification to users when a specific event occurs. Custom notifications appear in the notification bell and can be delivered to the Salesforce desktop or mobile app.
Send Email Action: Use the Send Email action in Flow Builder to send emails to individual recipients, apply email templates, add attachments, and optionally log emails to related records' activity timelines. For bulk email to audience segments, use the Send Email Message element instead.
Send Notification Action: Call a notification type to send. Each Send Notification action corresponds to a supported notification type. Send Notification actions are available only for Slack-enabled custom notification types and certain Slack-enabled standard notification types.
Send Surveys Action: Create an action to send an active survey by specifying the name, subject, recipients, and invitation link options in the flow.
Show Toast Message Action: Shows a brief message window on the user's page. The message can include links to external content.
Slack Flow Core Actions: Manage Slack channels, channel members, and messages from flows. As your Salesforce records change, a flow can trigger changes in Slack.
Create a Salesforce Channel in Slack Action: Creates a Slack channel associated with the Salesforce record selected in your flow. This channel becomes discoverable through other flow actions, record unfurls, and Slack list views.
Get Information About Slack Conversation Action: Retrieve the name of a Slack channel and its archived status. Archived channels are closed to new activity, but users can still view and search an archived channel’s message history.
Pin or Unpin Slack Message Action: Pin or unpin a message in a Slack channel or direct message. Pin messages so that they’re readily available from the conversation header.
Send Slack Message Action: Send a message to a Slack channel, direct message, or the Messages tab of a Slack app.
Send Message to Launch Flow Action: Send a message to a Slack channel, direct message, or the Messages tab of a Slack app that includes a button that a recipient can use to launch a screen flow.
Create Consumption Alert: Sends a notification to specified users when consumption for a card meets or exceeds a specified threshold.
Create License Utilization Alert: Sends a notification to specified users when license utilization reaches or exceeds a specified threshold.
Create Product Limit Alert: Creates alerts when product limit utilization reaches or exceeds configured threshold percentages. This action evaluates current utilization against the specified thresholds and creates Utilization Alert records when thresholds are breached.
Add Prompt Instructions Element: Provide data in the form of prompt instructions that are merged into a prompt template in Prompt Builder. This element is available only in template-triggered prompt flows.
Apex Action Element: Call an Apex class. An Apex class functions as an Apex action only if one of its methods includes the @InvocableMethod annotation.
Apex Action (Legacy) Element: Call an Apex class that uses a legacy Apex interface. Apex classes are available as legacy Apex actions only if the Process.Plugin interface has been implemented.
Assignment Element: Set values in variables, including collection variables, record variables, record collection variables, and global variables.
Activate Order Action: In a B2B Commerce Checkout flow, activate a Salesforce standard draft order.
Calculate Cart Promotions Action: In a B2B Commerce Checkout flow, request a full calculation of all line items in the cart that have a promotion.
Calculate Cart Taxes Action: In a B2B Commerce Checkout flow, request a tax cost calculation for all line items within the cart.
Cancel Cart Async Operation Action: In a B2B Commerce Checkout flow, cancel the current checkout so the user can return to an unlocked cart. This operation automatically runs when cart changes are invoked, such as add to cart.
Cart to Order Action: In a B2B Commerce Checkout flow, create a Salesforce standard order in draft mode.
Check Cart Inventory Action: In a B2B Commerce Checkout flow, request a full inventory availability check of all line items in the cart.
Checkout Session Action: In a B2B Commerce Checkout flow, get or create a checkout session, and return the ID of the session to the caller.
B2B Commerce Checkout Flow Core Actions: The B2B Commerce Checkout Flow provides several core actions for implementing a successful checkout process within your Commerce org. To add one of these actions to your flow, add an Action element. Then select the B2B Commerce category, and search for the appropriate action.
Price Cart Action: In a B2B Commerce Checkout flow, request a reprice of all line items in a cart.
Update Checkout Session Action: In a B2B Commerce Checkout flow, the Update Checkout Session action updates the checkout session state if the current state matches the expected state. This action provides consistency during checkout handling and guarantees that if two browsers attempt to update the state, one succeeds and the other fails validation.
Commerce Checkout Flow Core Actions: The Commerce Checkout Flow provides several core actions for implementing a successful checkout process within your Commerce org. To add one of these actions to your flow, add an Action element. Then select the Commerce category, and search for the appropriate action. Cart actions aren’t available in flows for B2B stores built on an Aura template.
Run Agent Element: Use an Agentforce agent to handle tasks dynamically in your flow. Select an existing agent or create an agent with custom instructions and actions.
Custom Error Element: Create targeted error messages in record-triggered flows to display in a window on the overall record page or as an inline error on a specific field for your users. The change that triggered the flow is rolled back until the error is fixed.
Create Records Element: Create or update multiple Salesforce or Marketing Object records by using a record collection variable. Create or update exactly one Salesforce or Marketing Object record by using a record variable or other values from the flow.
Check for Duplicate Records: To prevent duplicate records, check for records that match a set of criteria and specify what happens if the flow finds matching records. Some field-level configurations and validations in your org override the settings in the Create Records element.
Delete Records Element: Identify Salesforce or Marketing Object records to delete by using the IDs stored in a record variable or record collection variable, or by specifying conditions.
Get Records Element: The Get Records element finds all Salesforce or Marketing Object records that meet the filter and sort conditions and stores values from the retrieved records in variables. You can retrieve Salesforce standard and custom object records, or Marketing Object records, by using the Get Records element.
Update Records Element: Identify Salesforce or Marketing Object records to update, and set the values to change in those records. To do so, use the IDs and field values stored in a record variable or record collection variable, or use specify conditions to identify the records and set the field values individually.
Decision Element: Evaluate a set of conditions, and route users through the flow based on the outcomes of those conditions. This element performs the equivalent of an if-then statement.
Email Alert Element: Send an email using an Email Alert action where you specify an email template and a static list of recipients. You add an Action element to your flow and search for the name of your already configured Email Alert action.
Collection Filter Element: Apply criteria to a collection, and then output a new collection that contains only the items that meet the criteria.
Group Element: Organize related elements into a named, collapsible section of your flow. Groups are available only in auto-layout mode.
Loop Element: Start a loop path for iterating over items in a collection variable. For each iteration, the flow temporarily stores the item in the loop variable. To run actions on each item’s field values, use other elements in the loop.
Flow Builder Elements for Marketing Flows: A Flow Builder element represents an action that a flow can run. Examples include decisions based on criteria and creating and deleting Salesforce data. Some Flow Builder elements are available only in Marketing or Data 360, such as Send Email Message and Send SMS Message.
Assign to Queue Element: The Assign to Queue element is a marketing completion action that automatically assigns a lead to a queue that you select.
Assign to User Element: The Assign to User element is a marketing completion action that automatically assigns a lead to a user that you select.
Marketing Completion Actions: Use marketing completion actions to automate routine, follow-up tasks, such as lead assignments and user notifications.
Create Consent Marketing Flow Element: The Create Consent action element updates the consent status for the contact point related to a unified individual in a flow. For a specific channel and communication subscription combination, you can set a contact point's consent status to Opt In or Opt Out.
Determine CRM Record for Individual Marketing Flow Element: Use the Determine CRM Record for Individual action element to find out if a person has a contact, lead, or prospect record. You can set up different paths for each situation and customize how you want to approach an individual depending on your existing records. For example, send specific emails based on whether the person is a lead or prospect, or update their contact record with new information.
Einstein Decision Marketing Flow Element: Determine a user’s level of email engagement by using Einstein Engagement Frequency or Einstein Engagement Scoring. You can also route users through the flow based on that engagement level. This element performs the equivalent of an if-then statement.
Exit from a Flow Marketing Flow Element: The Exit from a Flow action element removes individuals from a specific Marketing Cloud flow. For example, in a segment-triggered flow, you can remove a customer from a marketing email flow when they've made a purchase during a campaign.
Send Email Message Marketing Flow Element: The Send Email Message action element sends an email from your Salesforce CMS to an audience segment. You can configure the action to track clicks and opens, send messages to your opt-in list only, and get help from Einstein for send-time optimization (STO) and identifying which clicks and opens are real.
Send Marketing Cloud Engagement Email Marketing Flow Element: The Send Marketing Cloud Engagement Email action sends an email with send classifications, publication lists, and content in Marketing Cloud Engagement via segment, event-triggered, activation-triggered, or broadcast flow. You can configure the action to target Data 360 audience segments using your existing Marketing Cloud Engagement content and settings without requiring segment activation or data replication. Enable Retain send log data to keep send log information and pass it to Marketing Cloud Engagement for reporting and troubleshooting.
Send RCS Message Marketing Flow Element: The Send RCS Message action element sends an RCS message from your Salesforce CMS to an audience segment. You can configure the action to track clicks and opens, send messages to your opt-in list only, and get help from Einstein for send-time optimization (STO) and identifying which clicks and opens are real.
Send SMS Marketing Flow Element: The Send SMS Message action element sends an SMS message from your Salesforce CMS to an audience segment. You can configure the action to track clicks and opens, send messages to your opt-in list only, and get help from Einstein for send-time optimization (STO) and identifying which clicks and opens are real.
Send to Journey Marketing Flow Element: The Send to Journey action element sends individuals to a specific Marketing Cloud Engagement journey. For example, in a segment-triggered flow, you can send customers to specific journeys depending on each individual’s loyalty program status.
Send WhatsApp Message Marketing Flow Element: The Send WhatsApp Message action element sends a WhatsApp message from your Salesforce CMS to an audience segment. You can configure the action to track clicks and opens, send messages to your opt-in list, and identify which clicks and opens are real.
Create Reservation Action: In Omnichannel Inventory, create one or more inventory reservations at a location or location group.
Fulfill Reservation Action: In Omnichannel Inventory, fulfill one or more inventory reservations at a location.
Get Availability Action: In Omnichannel Inventory, get inventory availability data for one or more products at one or more inventory locations or location groups.
Salesforce Omnichannel Inventory Flow Core Actions: Salesforce Omnichannel Inventory provides several core actions for implementing inventory functionality in flows. To add one of these actions to your flow, add an Action element. Then select the Omnichannel Inventory Service category, and search for the appropriate action.
Transfer Reservation Action: In Omnichannel Inventory, transfer one or more inventory reservations between locations or location groups. This action reduces the reserved quantity at the source and increases it at the destination. It doesn’t change physical quantities.
Add Order Item Summary Action: In Salesforce Order Management, add up to 100 order product summaries to an order summary. This action creates a change order record, an order product record, and an order product summary record. It also creates any supporting adjustment, tax, and summary records.
Adjust Order Item Summaries Preview Action: In Salesforce Order Management, preview the expected results of adjusting the price of one or more order product summaries on an order summary, without running the adjustment. You can only apply a discount, not an increase. The output of this action contains the values that would be set on the change orders created by submitting the proposed adjustment.
Adjust Order Item Summaries Submit Action: In Salesforce Order Management, adjust the price of one or more order product summaries on an order summary. You can only apply a discount, not an increase. This action creates one or more change order records.
Authorize Payment Action: In Salesforce Order Management, authorize a payment on a credit card. You can include details for a new credit card or reference an existing payment method.
Cancel Fulfillment Order Item Action: In Salesforce Order Management, cancel fulfillment order products from a fulfillment order. You can cancel more than one product and specify a quantity to cancel for each of them. This action doesn’t cancel the associated order product summaries, it only reduces their allocated quantities. Usually, you reallocate the canceled quantities to a new fulfillment order.
Cancel Order Item Summaries Preview Action: In Salesforce Order Management, preview the expected results of canceling one or more order product summaries from an order summary without running the cancel. The output of this action contains the values that would be set on the change order created by submitting the proposed cancel.
Cancel Order Item Summaries Submit Action: In Salesforce Order Management, cancel one or more order product summaries from an order summary. This action creates a change order record.
Change Order Summary Preview Action: In Salesforce Order Management, preview the requested changes to an order summary without submitting them. Use this action to review changes before submitting. This action is available in flows running API version 67.0 and later.
Change Order Summary Submit Action: In Salesforce Order Management, submit the requested changes to an order summary, including item, delivery group, tax, and adjustment changes. This action is available in flows running API version 67.0 and later.
Confirm Held Fulfillment Order Capacity Action: In Salesforce Order Management, confirm held fulfillment order capacity at one or more locations. This action decreases a location’s held capacity and increases its assigned fulfillment order count. Confirm held capacity when you assign a fulfillment order to a location.
Create Credit Memo Action: In Salesforce Order Management, create a credit memo to represent the refund for one or more change orders associated with an order summary.
Create Fulfillment Order Action: In Salesforce Order Management, create one or more fulfillment orders and fulfillment order products for an order delivery group summary, which defines a recipient and delivery method. You specify the order product summaries to fulfill and the fulfillment locations to handle them. If you specify multiple fulfillment locations, a fulfillment order is created for each one.
Create Fulfillment Orders Action: In Salesforce Order Management, create fulfillment orders and fulfillment order products for multiple order delivery group summaries, each of which defines a recipient and delivery method. You specify the order product summaries to fulfill and the fulfillment locations to handle them. If you specify multiple fulfillment locations for one order delivery group summary, a fulfillment order is created for each one.
Create an Invoice from Change Orders Action: In Salesforce Order Management, create an invoice to represent the charges for one or more change orders. Create invoices for change orders that increase order amounts, such as return fees. When you ensure the refund for a return, include the invoices for the associated return fees in the input.
Create Order Payment Summary Action: In Salesforce Order Management, create an order payment summary for a payment authorization or payments that use the same payment method and are attached to the same order summary.
Create Order Summary Action: In Salesforce Order Management, create an order summary based on an order. That order is considered the original order for the order summary. Subsequent change orders that apply to the order summary are also represented as order records.
Create Return Order Action: In Salesforce Order Management, create a return order and return order items for order items belonging to an order summary. You can add return fees for any of the order items.
Ensure Funds Async Action: Ensure funds for an invoice, and apply them to the invoice. Optionally, apply the funds in a defined sequence. If needed, capture authorized funds by sending a request to a payment provider. This action inserts a background operation into an asynchronous job queue and returns the ID of that operation so you can track its status. Payment gateway responses appear in the payment gateway log and don’t affect the background operation status.
Ensure Refunds Async Action: In Salesforce Order Management, ensure refunds for a credit memo or excess funds by sending a request to a payment provider. This action inserts a background operation into an asynchronous job queue and returns the ID of that operation so you can track its status. Payment gateway responses appear in the payment gateway log and don’t affect the background operation status.
Find Routes with Fewest Splits Action: In Salesforce Order Management, evaluate ordered product quantities against available inventory to determine the smallest combination of locations that can fulfill the order. If multiple combinations of the minimum number of locations can fulfill the order, the action returns multiple options. Optionally, you can specify a maximum allowable number of locations. By default, the action runs up to 1,000,000 times, stopping when it hits 10,000 results.
Find Routes with Fewest Splits Using OCI Action: In Salesforce Order Management, this core action finds the minimum number of fulfillment locations needed to complete an order by evaluating inventory availability across locations. When multiple combinations of locations can fulfill the order, this action returns multiple routing options. To limit the number of returned options, specify a maximum number of allowed location splits.
Hold Fulfillment Order Capacity Action: In Salesforce Order Management, hold capacity to process fulfillment orders at one or more locations. This action increases a location’s held capacity. Hold capacity when you plan to assign a fulfillment order to a location.
Salesforce Order Management Flow Core Actions: Salesforce Order Management provides several core actions for implementing order management functionality in flows. To add one of these actions to your flow, add an Action element. Then select the Order Management category, and search for the appropriate action.
Order Routing Rank by Average Distance Action: In Salesforce Order Management, calculate the average distance from sets of inventory locations to an order recipient, and return the sets sorted by that average distance. Use this action to compare the average shipping distances for different sets of locations that can fulfill an order.
Release Held Fulfillment Order Capacity Action: In Salesforce Order Management, release held fulfillment order capacity at one or more locations. This action decreases the held capacity of a location without increasing the assigned fulfillment order count. Use this action when canceling a fulfillment order assignment to free up capacity at one or more locations.
Return Order Item Summaries Preview Action: In Salesforce Order Management, preview the expected results of a simple return of one or more order product summaries from an order summary without running the return. The output of this action contains the values that would be set on the change order created by submitting the proposed return.
Return Order Item Summaries Submit Action: In Salesforce Order Management, return one or more order product summaries from an order summary. This action is a simple return that creates a change order but not a return order.
Return Order Items Action: In Salesforce Order Management, process one or more return order line items belonging to a return order. This action creates a change order record for the returned items and makes the processed return order line items read-only. You can include return order fees associated with the return order line items. If you do, a change order record is created for the return fees. If a processed return order line item has a remaining expected quantity, the action creates a separate return order line item representing that quantity.
Path Experiment Element: Experiment with up to 10 different versions of a customer journey to determine the most effective path. The Marketing Cloud Path Experiment element randomly assigns individuals to paths for an unbiased outcome. Use automated path selection for faster optimization. Use manual path selection for added control or if you’re using data from outside Salesforce.
Flow Resume Events: Define the event to wait for if the wait conditions are met. When an event occurs, the flow resumes and takes the path associated with this wait configuration.
Platform Event Message: Resume the flow interview when it receives a platform event message.
Personalize Paths Element: Send each audience member to the path where they're most likely to meet your conversion goal. The system continuously learns from real conversion outcomes and predicts which path performs best for each audience member. Personalize Paths is available in automation event-triggered flows and segment flows.
Recommendation Assignment Element: Generate Einstein Next Best Action recommendations by combining data from records in the recommendation object, records in other objects, values in collections, and manually entered values.
Screen Element: Collect information from or display information to a user who runs the flow.
Adding Record Fields to Flow Screens: Build flow screens faster by adding fields directly from your Salesforce objects. When you add a record field to a flow screen, its name, data type, help text, requiredness, and, in certain cases, existing values are automatically configured. Record fields use a record variable to determine which fields can be placed on a flow screen and their configuration.
Get or Process Data Within a Screen Element with Screen Actions: Screen actions make your screen elements dynamic by using an autolaunched flow to retrieve or process data. Screen actions reduce the need for you to add elements between screens and reduce the need for users to switch between screens to observe data updates. Because users click though fewer screens, they can finish a screen flow faster. Also, users benefit from screens that react to their interactions, increasing their engagement.
Improve Data Quality by Validating User Input: Screen flows are great at reducing manual data entry but it's important that the data you collect is error-free. Make sure your screen flow users are entering information correctly by validating their input.
Standard Flow Screen Components: Salesforce provides several standard screen components that extend the types of input fields available in screens.
Action Button Screen Input Component: Use the Action Button component so the running user can trigger a screen action with the click of a button on a screen. The screen action runs an active autolaunched flow, and the results of the autolaunched flow can be shown on the same screen as the button. Using this component means that you need fewer screens so users can complete screen flows more quickly.
Address Screen Input Component: Simplify gathering address information by adding the Address component to a flow screen. The Address screen component shows a complete address form that’s customized to your settings. It can also use state and country/territory picklists.
Choice Lookup Screen Input Component: Let users search for and select one option from a set of choices on a flow screen. The component supports only Text values.
Data Table Screen Input Component: Display a collection of records in a table so that the user running the flow can select records. The flow stores the selected records as flow variables that the rest of the flow can act on.
Date Screen Input Component: Give the user running the flow a field to enter date values from a flow screen.
Dependent Picklists Screen Input Component: Display picklists in a flow screen in which the options for one picklist depend on the selected value of another picklist. The Dependent Picklists screen component determines which options to display in each picklist by using an existing field dependency in your org. A field dependency connects two picklist fields on the same object.
Display Image Screen Input Component: Easily insert images in flow screens. Upload images to Salesforce as static resources and then you can reference them while configuring the component.
File Upload Enhanced Screen Input Component (Beta): Give users the opportunity to upload files from a flow screen. The File Upload Enhanced (beta) flow screen component is similar to the existing File Upload screen component, but it has some key differences. The File Upload Enhanced (beta) screen component can be used in Aura and Lightning Web Runtime (LWR) sites, instead of just Aura sites. Also, you can require that users upload documents before moving on in the flow.
Lookup Screen Input Component: Let users search for and select existing records in a screen flow. Configure the component with a lookup field and its source object, and store the selected record IDs for use later in the flow.
Choose a Lookup Option for a Flow Screen: Salesforce provides three ways for users to search for and select records on flow screens. Generally, use the Lookup component when you want users to search an unfiltered list of records. Use the Choice Lookup component when you want users to search a filtered list of records or static choices. Use a lookup record field when you want users to have the option to create a record from the lookup field. This table describes the differences between the three options.
Create a Contact for Each Beneficiary on a Policy Example: Add a Repeater component to a screen, and then add child components to represent a beneficiary on a policy. Loop over the output Repeater component to create a collection of Contact records. Then use the collection to create a Contact record for each beneficiary.
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.
Name Screen Input Component: Let users enter multiple name values with one screen component. Instead of the Name screen component, you can use Text input fields to capture name information, but it takes a lot more configuration.
Product Selector Screen Input Component: In Order Management, let users select which fields show in columns during product selector for various transaction types, such as returns or exchanges.
Password Screen Input Component: Let users enter sensitive information in a flow screen, such as a social security number. Text entered by the user is masked.
Radio Button Group Screen Input Component: Provide a compact set of single-select options in a screen flow to save screen space. The options appear in a horizontally stacked button format on desktops and a vertically stacked button format on mobile devices.
Repeater Screen Display Component: Collect information about multiple items of the same type on a screen with the Repeater component. To use the output of the component elsewhere in the flow, loop over the output and save the relevant data in a variable. Use the variable to build a list of records.
Visual Picker Screen Input Component: Use the visual picker screen component to make option selection even simpler. Your users can select tiles that combine text with icons instead of scrolling through dropdown menus at run time.
Send to a Flow Marketing Flow Element: The Send to a Flow action element sends individuals to a specific Marketing Cloud on-demand flow. For example, in a segment-triggered flow, you can send a customer to a specific flow depending on the individual’s loyalty program status.
Collection Sort Element: Reorder the items within a collection and optionally limit the number of items that remain in the collection after the sort.
Start Element: Connect the Start element to the flow element that you want to run first at run time. In an autolaunched flow, you can open the Start element to add a trigger that launches the flow. Without a trigger, you must set up other things to invoke the autolaunched flow, such as custom buttons, processes, Apex classes, or Einstein Bots.
Subflow Element: Launch another active flow that’s available in your org. A flow launched by another flow is called the referenced flow.
Transform Element: Select the flow resources for mapping and transforming source data to target data. You can use the Transform element in screen flows, autolaunched flows with no triggers, and record-triggered flows.
Create Tasks After Waiting for a Platform Event Example: Create a flow that automates your supply ordering by pausing your flow until a platform event confirms shipment, then create a follow-up installation task for the next day.
Wait Until a Single Event Occurs Example: Create a flow that sends an email after waiting for a specific event to occur, such as waiting one day after a contract is activated before sending a feedback request.
Wait for Conditions Element: Resume a flow interview after specific conditions are met. Each wait configuration that you define in a flow has optional wait conditions. At run time, these conditions determine whether the flow waits for the associated resume event.
Wait Until Event Element: Resume a flow interview after an engagement event. Select a standard event, such as Email Link Click or SMS Response, or use a custom engagement signal.
Flow Operators: Operators behave differently, depending on what you’re configuring. In Assignment elements, operators let you change resource values. In conditions and filters, operators let you evaluate information and narrow the scope of a flow operation.
Flow Operators in Data Elements and Record Choice Sets: Filter conditions narrow the scope of records that the flow operates on. For example, use filter conditions to update only the contacts that are associated with the Acme Wireless account. When you add an Update Records element, use filter conditions to narrow the scope to just the contacts whose parent account is Acme Wireless. The In and Not In operators are available only in Create Records, Get Records, and Update Records elements.
Flow Version Properties: A flow version’s properties consist of its label, description, interview label, and type. These properties drive the field values that appear on the flow’s detail page.
Flow Resources: Each resource represents a value that you can reference throughout the flow.
Choice Resource: Create a choice option for a screen component, such as a Radio Buttons or Multi-Select Picklist component.
Constant Resource: Store a fixed value that can be used but not changed throughout a flow.
Formula Resource: Calculate a value when the formula is used in the flow.
Global Variables Resource: System-provided variables store information that can be referenced throughout a flow. For example, it can contain information about the Salesforce org, flow, running user, or triggering record.
Selected Record Flow Resource: Store a record that you sort and filter from a data source. Use a selected record resource to access nested data from data graphs and other data sources, and reference it in flow elements for personalization, decisions, and assignments.
Stage Resource: Stages represent the steps in your flow. To keep users informed about which stage they’re in and how far they’ve progressed in a flow, you can create stage resources and use a progress indicator.
$Flow Global Variables Resource: In a flow, a $Flow global variable provides information about the running flow interview. Some variables contain system-provided values. You can update the other variables throughout the flow by using Assignments or by storing output values in the variables.
Value Map: A reusable lookup table that maps source values to target values.
Variable Resource: Store a value that can be used or changed throughout the flow.
Add Values to a Collection Variable: After you create a collection variable, populate it with values to reference throughout your flow. You can’t use a Get Records element to populate a collection variable, but there are some workarounds.
Test a Data Cloud-Triggered Flow: Create, save, and run automated tests for a Data Cloud-triggered flow. Each time you modify the flow, run the test again to verify its behavior.
Debug a Screen Flow with the Debugger Example: Debug a screen flow that uses information collected from the screen flow's registration form to create a contact for each policy beneficiary.
Translate Flow Screen Components: To use multilingual labels for most flow screen components, use Translation Workbench. Flow screen components in beta and some generally available flow screen components don’t support this functionality. For those generally available flow screen components, use the $Label global variable to specify custom labels. Create the custom labels before referencing them in a flow.
Manage Record-Triggered Flows: See, manage, reorder, and filter your record-triggered flows with Flow Trigger Explorer. Flow Trigger Explorer shows all the flows that are associated with a specified object and that run when a record is created, updated, or deleted. You can navigate between a flow in Flow Builder and other flows that run under the same circumstances.
Troubleshooting Flow Run Time Errors: Learn how to troubleshoot and resolve flow errors and unexpected behavior in your flows that occur after activation. Interpret error emails, and use best practices to identify and resolve issues quickly.
Considerations for Flow Error Emails: Review these considerations for the email sent to the admin or Apex exception email recipients regarding flow interview errors and Screen and Subflow elements.
Select Flow and Process Error Email Recipients: When a process or flow interview fails, a detailed email is sent to the admin who last modified the process or flow. However, sometimes the admin isn’t the best person to act on the details of what ran and what went wrong. In that case, you can send error emails to the Apex exception email recipients.
Troubleshooting Flow URLs: If you’re distributing a flow and the custom button, custom link, or a direct flow URL isn’t working as expected, verify the referenced flow. In addition, verify its variables if you’re passing values into a flow from the URL.
Sample Date Formulas: Use Date, Date/Time, and Date formulas for many common business needs. For example, extract and format parts of a date or time, such as quarter, week, weekday, month name, or the hour, minute, and second. Calculate durations in days, business days, or business hours. Project future and relative dates, and handle issues such as leap years, the last day of the month, and time zone conversions.
Using Date, Date/Time, and Time Values in Formulas: Use Date, Date/Time, and Time values in formulas to manage payment deadlines, calculate contract ages, and support other time-dependent business needs. Learn how to create and compare these values, convert between data types and text, and account for time zones.
Get an Explanation for a Formula and Fix Errors with Einstein for Formulas: Use Einstein for Formulas to get an explanation for a formula and fix syntax errors in a formula used in Formula fields, default field values, and record validation rules. As an admin, you can use Einstein’s assistance for existing formulas or for the new ones that you create.
Get Started: By using Event Relay in Salesforce with Amazon EventBridge in AWS, your Salesforce event-driven apps can use AWS services to process events or send events to third-party and SaaS integrations. You can also send platform events from AWS to Salesforce, where subscribers can process them using Salesforce Platform capabilities.
Manual Sharing: Manual sharing allows users to share individual records with other users, public groups, and roles.
Salesforce Connect Adapter for GraphQL: GraphQL is a standard query language that allows applications to flexibly access required data and provides a modern way to integrate applications. Unlike traditional REST APIs, GraphQL provides granularity in specifying fields and relationships and is more efficient.
Map Salesforce External Object Fields to GraphQL Types: When you map external object fields to GraphQL scalar types, you may want to optimize the type mapping for a better experience in Salesforce. For example, a String in the GraphQL schema can be mapped to a Picklist in Salesforce to improve data quality.
Manage Qualifiers and External IDs for Salesforce Connect Adapter for GraphQL: When you sync a database table to create a Salesforce external object, a table qualifier is automatically generated. The qualifier constructs an external ID for the external object based on the global id field in the GraphQL schema. You can also configure the external ID based on any of the ID field types in the GraphQL schema.
Turn Off Salesblazer Content in the Guidance Center: Optionally, turn off Salesblazer content in the Guidance Center for end users. The Guidance Center icon remains available when Sales Programs, Guidance Sets, or Learning Paths are in use.
Create Custom Home Page Components: Use custom components to configure the Salesforce Classic home page for your users. Add HTML, images, links, and more to enhance your users’ productivity.
Visualforce Area Home Page Components: Use Visualforce Area home page components to add dynamic content to your home page. For example, you can present content from partner apps, display charts with the Reports and Dashboards REST API, or add a canvas app to the home page.
Formulas: How Do I ... ?: A collection of topics around formulas, including common math calculation, text functions, and more.
Deactivate Users: To deactivate a user’s account so they can no longer log into Salesforce, complete these steps.
Capturing Gender-Related Data with Standard Fields: Represent the diversity of your customer base by recording gender-related data in Salesforce. Use standard, optional fields with vetted value sets to help you personalize your data, build trust, and close data gaps in your system of record.
Manage Duplicate Data Privacy Records: Keep your records clean and free of duplicates so that you can reach more customers and maintain better relationships with them.
Fields in Data Privacy Records: Get the skinny on the fields that appear in data privacy records based on the Individual object. Data privacy records store certain privacy settings for your customers.
Tracking Customer Requests for Data Privacy Updates: If you store certain data privacy preferences in data privacy records based on the Individual object, track customers’ requests so that you can honor their wishes.
Best Practices for Tracking Data Privacy: Keep these best practices in mind when storing certain data privacy preferences in data privacy records based on the Individual object.
Install in Existing Sandboxes: To use Data Mask in sandboxes created before you installed the managed package in your production org, additional steps are required.
Merge Fields for S-Controls: A merge field is a field you can put in an email template, mail merge template, custom link, or formula to incorporate values from a record.
Which API Do I Use?: Choose the right Salesforce API for your integration needs. Review the selection of APIs Salesforce offers, including the supported protocols, data formats, and use cases.
Give Integration Users API Only Access: Following the principle of least privilege, we recommend creating and configuring one Salesforce user for every integration. By assigning a different user to each calling system, domain, use case, or API resource, you restrict each of those users to a unique subset of data and functionality. Setting up dedicated integration users gives you more control over operations and traceability of transactions. And it minimizes the impact if a user or integration is compromised. The Salesforce Integration user license supports this best practice by offering a profile that restricts assigned users to API-only access, ideal for system-to-system integration users.
Assign Page Layouts to Profiles or Record Types: After defining page layouts, assign which page layouts users see. A user’s profile determines which page layout he or she sees. In addition, if your organization is using record types for a particular object, the combination of the user’s profile and the record type determine which page layout is displayed when a user views records for that object.
Page Layout Considerations: Keep these considerations in mind when working with page layouts in the enhanced page layout editor.
Customize Page Layouts with the Enhanced Page Layout Editor: Tailor your page layouts to the needs of your users with the enhanced page layout editor. Add, remove, or reorder actions, buttons, fields, and sections on a record’s detail page.
Manage Mobile Cards in the Enhanced Page Layout Editor: Add expanded lookups, components, and Visualforce pages to the Mobile Cards section of your page layout to have them show up as mobile cards in the Salesforce mobile app.
How Page Layout Elements Display in Lightning Experience: When you change your page layouts in Salesforce Classic, it can impact the content shown on object record pages in Lightning Experience. However, in Lightning Experience, the page elements look different, and some features are not supported.
How Page Layouts Work in the Salesforce Mobile App: Use the enhanced page layout editor to customize the layout of an object’s record detail pages, configure actions, and adjust which fields and related lists appear in the Salesforce mobile app.
Page Layout Limitations: Keep these limitations in mind when working with page layouts in the enhanced page layout editor.
Configure Fields on Multi-Line Layouts for Opportunity Products: Before you can add a field to the Opportunity Product multi-line layout, the field must be visible on the Opportunity Product page layout. You make the field visible via the Product related list on an Opportunity object page layout.
Standard Object Record Page Save Options on Page Layouts: With save options, you can make object-specific checkboxes appear on the edit pages for certain standard objects. Save options trigger additional processes when a record is saved. You can also set the checkboxes to be selected by default.
Page Layout Tips: Here are a few tips to keep your page layouts organized and easy to use.
Rule Enforcements: Each Governance rule maps to an enforcement that checks coding agent activity against that rule.
Governance Policy Categories: Policies are grouped into 10 categories based on the type of risk they address. Each category contains a set of policies, and each policy contains a set of rules.
Governance Rules: Each Governance policy is made up of rules. Rules define the specific behavior that Lifecycle Center Governance enforces for coding agents.
Update Rule Status: Turn a rule on or off to control how it's enforced for coding agents.
Lightning App Builder Considerations: Keep these considerations in mind when working with Lightning pages and Lightning apps in the Lightning App Builder.
Create an App Page with the Lightning App Builder: Create a page for an app that you can add directly into Lightning apps and the Salesforce mobile app. Your users can then easily access the objects and items that are most important in that app.
Create Dynamic Actions in Lightning App Builder: With dynamic actions, you can add flexibility and control to actions on your record pages. Assign dynamic actions in the Lightning App Builder instead of in the page layout editor, and then apply filters to control when and where actions are visible to users.
Create Dynamic Related Lists in Lightning App Builder: With dynamic related lists, you can add flexibility and control to related lists on your record pages. Add, customize, and filter related lists in the Lightning App Builder instead of in the page layout editor. To help your users see the most relevant records, set up two or more dynamic related lists with different filters on the same object.
Create and Implement a Quick Action Page (Beta): A quick action page is a Lightning page that defines the UI for a page-based quick action. You can configure the fields, sections, visibility rules, and layout that users see when they trigger the action. You can build a quick action page one time in Lightning App Builder and associate it with multiple quick actions. When you update the quick action page, your changes apply to all actions that use it.
Activate Lightning Record or Home Pages: Is your custom Lightning page ready for your users? Use the Activation function inside the Lightning App Builder to get the page out to them. You can make your custom page the default page for all users, assign it to specific Lightning apps, or assign it to record types and profiles. Assigning the page to a Lightning app, record type, or profile gives your users access to a page customized for the context they’re working in.
Add and Customize Tabs on Lightning Pages Using the Lightning App Builder: With the Lightning App Builder, you can create, update, delete, and change the order of tabs and tab sets on record, app, and Home pages in Lightning Experience. Configure the tabs that your users see, name them whatever you like, and add components to each tab.
Guidance for App Builder: Get suggestions for improving your Lightning pages just when you need them. Guidance for App Builder gives you feedback for enhancing your Lightning pages right in the design phase.
Tips for Creating Mobile App Pages in Lightning App Builder: Here are some best practices for building a mobile app page using the App Builder. For a consistent experience across devices, use the Lightning App Builder to preview your record and app pages.
Get Help for Lightning App Builder: The Lightning App Builder is a point-and-click tool that makes it easy to create custom pages for the Salesforce mobile app and Lightning Experience, giving your users what they need all in one place. The Lightning App Builder is also a one-stop shop for configuring Lightning apps.
Record Page Save Options in Lightning App Builder: With save options, you can define object-specific checkboxes that can be configured as part of a Dynamic Forms-enabled record save. Save options are available when editing an account or when creating, editing, or cloning a case or lead. Optionally, you can set the checkboxes to be selected by default.
Lightning Component Actions: Lightning component actions are custom actions that invoke a Lightning component. They support Apex and JavaScript and provide a secure way to build client-side custom functionality. Lightning component actions are supported only in the Salesforce mobile app and Lightning Experience.
Create a Lightning Component Action: Creating a Lightning component action is similar to creating a regular quick action, and you do it in the same place in Setup. All you need is a Lightning component in your org for the quick action to trigger.
Set Up Authentication for Lightning Out 2.0: For an external app to access components in a Lightning Out 2.0 app, the end user must be authenticated in Salesforce. The external app must also be authorized to access Salesforce resources. To set up authentication and authorization, implement an OAuth 2.0 flow and configure an External Client App (ECA) in your org. Then configure your external app to either call the Lightning Out 2.0 UI Bridge endpoint or the standard Salesforce UI Bridge endpoint. The call generates a frontdoor URL at run time, which is used to establish a Salesforce session for the Lightning Out 2.0 app.
Build a Lightning Out 2.0 App: Create and configure Lightning Out 2.0 apps with the low-code Lightning Out 2.0 App Manager. Add custom Lightning web components (LWCs) to each Lightning Out 2.0 app, and optionally define custom property values that your external apps can pass to these components. Generate a Lightning Out 2.0 code block that you can directly embed into an external app’s HTML markup.
Extend Salesforce to External Apps with Lightning Out 2.0: Embed custom Lightning web components (LWC) into external, non-Salesforce apps by using Lightning Out 2.0, a special Salesforce app that you create and configure in Setup. Developers can embed the generated Lightning Out 2.0 app script into a page of your company’s external app. Lightning Out 2.0 uses session-based authentication that logs users into Salesforce without leaving the external app, so authenticated users can seamlessly interact with the embedded components as if they were in Salesforce.
Prepare to Build a Lightning Out 2.0 App: Before you embed a Lightning Out 2.0 app into an external app, configure some security-related and administrative settings in Salesforce and in your external app. These settings allow Lightning Out 2.0 inline frames (iframes) to load in the external app.
Standard Lightning Page Components: Standard components are Lightning components built by Salesforce. Several standard components are available when creating Lightning pages.
Custom Lightning Page Components: The Lightning App Builder supports custom Lightning components that you create either with Aura or Lightning web components (LWC).
Visibility Rules on Lightning Pages: Control when a component appears on a Lightning page by adding filter conditions and logic to its properties in the Lightning App Builder. For example, you can construct a filter that causes a rich text component on an opportunity page to display when the opportunity’s amount is greater than or equal to US$1 million.
Activate Lightning App Pages: To make your custom app page available to users, you must activate it. You can also rename the Lightning page tab, adjust its visibility, and set its position in the navigation list. The Lightning App Builder’s activation feature makes this process easy.
Gain Insight About Page Performance with the Lightning Usage App: See how your Lightning pages are performing and understand the data in the Lightning Usage App. The Lightning Usage App shows you the most used pages in your org and their page load time by browser or by page.
Lightning Pages: A Lightning page is a custom layout that lets you design pages for use in the Salesforce mobile app or Lightning Experience.
Lightning Page Performance: Several factors can negatively affect your Lightning page’s performance at runtime. For example, your users can run into page performance issues if they aren’t using the latest version of a Salesforce recommended browser to view the page. Some factors you can control, and others you can’t. Here are some ways you can improve performance while configuring your page in the Lightning App Builder.
Lightning Page Templates: Lightning page templates are Lightning components that have been configured to serve as templates for custom Lightning pages. Page templates can support different form factors, such as desktop or phone. When you create a Lightning page in the Lightning App Builder, you can select a page template that matches the device you’re designing the page for.
Lightning Page Types: You can create different types of Lightning pages with the Lightning App Builder. After you set a Lightning page’s type, you can’t change it.
Deciding When to Use Lightning App Builder or the Page Layout Editor: The Lightning App Builder helps you customize Lightning Experience pages. The page layout editor helps you customize Salesforce Classic record page layouts and some aspects of Lightning pages, depending on the page's configuration. Each tool has its own unique capabilities. To help you decide when to use one tool instead of the other, review the uses each one supports.
Lightning Web Component Actions: Lightning web component (LWC) actions are custom quick actions that invoke a Lightning web component. They support JavaScript and provide a secure way to build client-side functionality. LWC actions are supported only on record pages in Lightning Experience.
Create a Lightning Web Component Action: Creating a Lightning web component (LWC) action is similar to creating a regular quick action, and you do it in the same place in Setup for most supported objects. All you need is an LWC in your org for the quick action to trigger.
Override Standard Buttons and Tab Home Pages: You can override the behavior of standard buttons—like New, View, or Edit—in Salesforce Classic, Lightning Experience, and mobile independently. You can also override the tab home page that displays when a user clicks a standard, custom, or external object tab.
Merge Fields for Custom Buttons and Links: A merge field is a field that incorporates values from an object record. You can put merge fields in an email template, mail merge template, custom link, or formula.
Custom Button and Link Samples: Use samples of custom Salesforce buttons and links to determine whether they can work for you.
Custom Button Example: Clone Records: The clone button is available for most standard objects. When a clone button is not available by default for a standard or custom object, you can create a custom clone button or link. This example creates a button that passes the field values of the record you’re on to a record create page.
Custom Button Example: Record Create Page with Default Field Values: Construct custom buttons and links that pass default field values to a record create page. This feature applies to Lightning Experience in all editions. This feature doesn’t apply to Lightning Out, Experience Builder sites, or the Salesforce mobile app.
Custom Button Example: Mass Delete: This example creates a JavaScript custom button for Salesforce Classic that can be added to activity-related lists and list views and allows users to delete selected records at the same time.
Custom Button Example: Pass Record IDs to an External System: You can use Salesforce record IDs as unique identifiers for integrating with an external system. This example creates a button that calls a Visualforce page to determine the record IDs of selected records and passes them in a URL query parameter to an external Web page called www.yourwebsitehere.com.
Custom Button Example: Get Record IDs: This example creates a button that opens a window listing record IDs for user selected records. Getting record IDs is useful when testing to ensure that you have the correct records before processing them further.
Custom Button Example: Reopen Cases: This example creates a button that can be added to cases related lists so that users can reopen several cases on an opportunity at once.
Viewing References to Salesforce Components: View a list of all the areas in Salesforce that reference a component. For example, view the custom links, custom buttons, or page layouts that reference another component, such as a Visualforce page or static resource.
Add an Approval Step to the Approval Process: Add an approval step to determine the records that can advance to that step and the approver, and whether to let an approver’s delegate respond to the requests.
Add Email Alerts to the Approval Process: Link the email templates that you created to the action in the approval process: Initial Submission Actions, Final Approval Actions, Final Rejection Actions, and Recall Actions.
Add Field Update to the Approval Process: Field updates change the selected field after the approval process is complete. For example, when a territory manager approves a shift, the Status field of the shift is updated from tentative to confirmed. You can add field updates for Initial Submission Actions, Final Rejection Actions, and Recall Actions.
Embed Outbound Flows Into Record Pages (Optional): When you embed a flow into a record page, users can schedule or modify appointments directly from the page. They don’t have to use the quick action, which launches the flow in a separate window and blocks users’ access to details on the page.
Add the My Appointments Micro Calendar Console to the Utility Bar: Make viewing past and upcoming appointments easy for service resources and your users by adding the My Appointments micro calendar console to the Salesforce utility bar. The My Appointments micro calendar console isn’t supported on mobile web browsers.
Add the Shift Capacity Component: Add the Service Territory Capacity Summary component to view shift capacity information for a service resource or service territory.
Add Translation Languages and Translators: Add languages for translation, assign translators for each language, and activate or deactivate a language’s translations.
Add Validation Rules to Service Appointment Fields: Add validation rules to ensure that user inputs meet your requirements. You can also use validation rules to override the default error messages. For example, you can add a validation rule that enables users to save an appointment only after they enter a subject.
Add the Video Call Utility Item to the Utility Bar: Make joining a video call easy for service resources and your users by adding the video call component to the Salesforce utility bar. The Video Call utility item isn’t supported on mobile web browsers.
Configure Related Lists for Salesforce Scheduler Object Page Layouts: Configure related lists for Salesforce Scheduler objects so that Salesforce Scheduler users can easily access more details related to an object record. For example, after you create a service territory, from the Service Territory Members related list, you can assign a service resource to the service territory. And from the Service Territory Work Types related list, you can assign a work type to the service territory.
Configure, Test, and Verify Your Agent: After you’ve set up the agent, configure, test, and verify your agent. When testing your agent, verify that other subagents don’t affect booking appointments with the Appointment Management subagent.
Create an Agentforce User: Clone the Einstein Agent User profile and create a user using the profile.
Enable Additional Features for Agentforce: Enhance the functionality of Agentforce for Scheduler by customizing their instructions. Add new instructions to the Appointment Book for Scheduler Agent topic to enable these optional features.
Set Up Agentforce for Guest Users: By default, the verification subagent verifies emails for users in your org as contacts or users. To enable Agentforce for users that aren't in your org (guest users), map new variables to agent actions and update the flows that the agent uses.
Set Up Email Notifications for Agentforce: For Agentforce to send email notifications, set up org-wide email addresses and add an email template to the flow that the agent action uses.
Set Up Agentforce for Scheduler: Agentforce gives you an easy way to manage appointments within Scheduler with natural language interactions.
Appointment Details Shown in the My Appointments Micro Calendar Console: The My Appointments micro calendar console shows upcoming and past appointments. The console makes getting into an appointment easy by showing basic appointment details, such as account information, appointment topic, and appointment type. The console shows the service appointments in the time zone of the logged-in service resource.
Appointment Distribution: Appointment distribution lets you allocate appointments quickly and evenly among service resources. An equitable distribution of appointments ensures efficient use of service resources and increased productivity. Salesforce Scheduler uses service resources’ utilization scores to identify and suggest the least occupied eligible service resources for appointments. For an anonymous appointment, the least occupied eligible resource is automatically assigned to the appointment.
Appointment Statuses and Status Categories in Salesforce Scheduler: Using service appointment statuses, users can track the status of appointments throughout the appointment lifecycle. Each appointment status is mapped to one of the standard, out-of-the-box service appointment status categories. Status categories can be used to create and use custom statuses while maintaining a consistent work classification for tracking and reporting. You can create custom appointment statuses but you can’t create status categories.
Update the Default Asset Sharing Setting (Optional): The default sharing setting for assets is Controlled by Parent, which requires a parent account and/or contact to be defined for an asset. However, assets do not always require parent accounts. To remove this restriction, change the default sharing setting.
Launch the Salesforce Scheduler Setup App: The Salesforce Scheduler Setup app provides all the Salesforce Scheduler resources in one place (in the form of object tabs) and makes it easier for administrators to create, configure, and manage those resources. Assign the Salesforce Scheduler Setup app to the user profile of your admin who will create and manage Salesforce Scheduler resources.
Assign Record Types to Profiles: Assign record types to profiles that have the corresponding roles. For example, you can assign the Territory Manager Status record type to the bank manager Adam who is assigned the role of a territory manager.
Assign Service Resources to Service Territories in Salesforce Scheduler: Assign service resources to service territories to ensure that appointment attendees are associated with the correct locations. Service resources assigned to a service territory are referred to as service territory members.
Add Assigned Service Resources as Recipients: Retrieve the list of service resources assigned to a service appointment and add them as recipients to the email notification list.
Enable Automatic Resource Assignment and Anonymous Scheduling: You can enable automatic service resource assignment to let users schedule appointments without selecting service resources. Customers or guest users don’t always know the names of service resources. And sometimes they don’t care about which resource they’re assigned. After you enable automatic resource assignment, service resources are automatically assigned based on the time slots users select. Also, you can hide the assigned resources’ names on the appointment summary page to protect their privacy.
Capabilities of Salesforce Scheduler: Salesforce Scheduler provides the tools to manage the data involved in scheduling appointments. You can also embed appointment scheduling into standard Salesforce workflows, such as leads and referrals, cases, opportunities, and accounts. Salesforce Scheduler also enables your users to book appointments by using Salesforce Lightning Console, Experience Cloud Sites, and your websites.
Change Labels in Flow Screens: To use your company's terminology, change the tab names and field names of Service Resource, Service Territory, Service Appointments, Work Type Group, and Work Type.
Check In Drop-In Customers: When a participant —customer— arrives at a business location, a greeter captures their information and then assigns the participant to a waitlist based on their reason for visit.
Configuration of Email Notifications for Unauthenticated Users: To send notifications about upcoming video appointments to unauthenticated users, create a Record-Triggered flow on the Service Appointment object. Configure the flow to retrieve the recipient’s email address and the assigned service resource name. Then, update the service appointment record to add the service resource name to a custom field. You can then create an Apex action to send email notifications that use the available Virtual Appointment Email templates.
Configure Appointment Email Notifications with the ICS File: Send internal and external users email notifications along with an Internet Calendar Scheduling (ICS) file for their upcoming appointments. The ICS file includes the appointment information, such as the date, time, and duration. You can configure a record-triggered flow to email a notification to a group of recipients or individually to each recipient.
Configure Guest User Access for LWR Sites: Unlike Aura sites, manually enable guest user access for Lightning Web Runtime (LWR) sites to allow unauthenticated (guest) users to book appointments.
Configure the Inbound New Guest Appointment Flow: Assign email notification templates that are sent to the guest users when they create an appointment. The email notification templates include a link that invokes the Modify Guest Service Appointment flow. To invoke the flow, set the URL for the experience site that has the Modify Guest Service Appointment flow added.
Configure the Modify Guest Service Appointment Flow: Assign the confirmation email notification templates that are sent to the guest users when they modify or cancel their appointments. The email notification templates include a link that invokes the Inbound New Guest Appointment flow. To invoke the flow, set the URL for the experience site that has the Inbound New Guest Appointment flow added.
Configure the Outbound New Appointment Flow for Group Appointments: Service resources can create group appointments and send email notifications to your customers, partners, and prospects after you configure the Outbound New Appointment flow. Configure the Outbound New Appointment flow to generate enrollment URLs for two experience sites, an enrollment URL for guests, and an unenrollment URL.
Configure Shift Settings: Add engagement channel types and topics to a shift. You can also define maximum appointments that customers can schedule for each of these associated topics.
Configure Shift Sharing Rule: To share shifts with external users, define shift sharing rules. For example, contractors are external users with whom a service territory manager shares shifts for approval. To share shifts, use the contractors public group and then select the roles in that group to whom you want to grant access.
Configure Video Calls: After you set up your AWS account and your connection to Salesforce, configure video appointments.
Connect Your Salesforce Calendar with External Calendars: Use Einstein Activity Capture app to connect Salesforce calendar with an external calendar, such as Microsoft® Outlook® or Google Calendar™. If you use Einstein Activity Capture, tell your users which calendar to use to edit events based on the sync direction you set.
Considerations for Capacity-Based Scheduling: An appointment is assigned to a shift and service resource based on the shift’s availability and capacity. When a particular shift or work type reaches capacity, the additional appointments are scheduled in the next shift or with another service resource with available capacity.
Considerations for Creating a Custom Review Service Appointment Screen: If you want to customize the Review Service Appointment screen beyond the inbuilt customization options, create your own screen. For example, create a custom Review Service Appointment Screen if you want to prefill values on the Review Service Appointment screen for guest flows.
Create an Appointment Status: Create and map custom appointment statuses to appointment categories. You can create multiple appointment statuses with the same status category, but you can’t map multiple status categories to the same appointment status.
Create an Apex Class for the Apex Action: Create an Apex class that you can link to the Apex action. The email template name in the Apex class refers to the email templates that are used to send email notifications for video appointments to unauthenticated users. You can rename the template based on your setup.
Schedule an Outbound Appointment in Salesforce Scheduler: A regular appointment represents a meeting—in person, or by phone or video—with a customer and an assigned resource or resources. A group appointment represents a meeting where you can add multiple person account, lead, or contact records as attendees.
Set Up a Custom Outbound Flow (Optional): To give your users access to a customized version of the Outbound New Appointment flow or Outbound Modify Appointment standard flow template, create an action and add it to the relevant page layout.
Create Email Templates: Define email templates for each status of a shift. For example, you can create email templates for creating, approving, or rejecting a shift.
Create Engagement Channel Types: To define engagement channels for service appointments and to add the channels to shifts, create engagement channel types.
Create a Quick Action to Launch the Flow: With quick actions, you can launch and navigate through workflows and perform a series of actions with just a few clicks. For example, to generate invitations quickly, create a quick action for generating the appointment invitation flow.
Create Holidays in Salesforce Scheduler: Create holidays for a day or for specific hours of a day. For example, create a holiday called Independence day for July 4 or a holiday called Christmas Eve between 2 PM and 11 PM for December 25.
Schedule an Inbound Appointment in Salesforce Scheduler: Customers, partners, and prospects can schedule a meeting—in person, by phone, or by video—with service resources. They can also create a group appointment and add multiple person accounts or contact records as attendees.
Create an Invitation URL Prefix for Community Sites: To generate an appointment invitation URL, create a URL prefix first. Then enter the URL prefix in the InvitationURLPrefix flow variable of the Select Service Appointment Time flow screen component.
Create Operating Hours in Salesforce Scheduler: View, create, and modify operating hours and time slots on the Operating Hours tab in the Salesforce Scheduler Setup app. Or use the Operating Hours component on a work type, service territory, or service territory member record page.
Create a Queue: A queue defines the roles that receive email notifications. Create a queue to send email notifications to territory managers or services resources when the status of a shift is updated.
Create a Record-Triggered Flow: Create a flow on the Service Appointment object so that you can configure email notifications.
Create Record Types for Shift Statuses: To make the required shift status options available for the roles that you created, create record types. For example, a service territory manager can create confirmed shifts or can create tentative shifts and then request the service resources to confirm them. For this process, you can create a record type called Territory Manager Status for the role of Territory Managers, and then select Tentative and Confirmed statuses. When territory managers create shifts, they can only view the Tentative and Confirmed options in the Status field.
Create Service Resources in Salesforce Scheduler: Service resources are individual users who can attend customer appointments. Create service resources so that you can assign appointments to them.
Create a Salesforce Scheduler Email Prompt Template: Save your end users time from manually writing appointment invitation emails. Create a Salesforce Scheduler Email prompt template to direct a Large Language Model (LLM) to generate personalized appointment invitations by using up-to-the-minute data from your Salesforce objects.
Create Service Territories in Salesforce Scheduler: Create service territories to organize your service resources and ensure that the service resources are assigned to appointments near their home branch.
Create Shifts in Salesforce Scheduler: Create shifts that vary daily or weekly. You can use shifts to assign service resources for periods that follow a flexible pattern. For example, different working hours at the same service territory or availability of the same service resource at different service territories.
Create Shifts in Bulk by Using a CSV File: Capture shift information in a CSV file, convert the CSV file to a JSON file, and then use Bulk API to create shifts in Salesforce Scheduler.
Create Skills in Salesforce Scheduler: To get started with skills for Salesforce Scheduler, create basic skills in your org. When you assign skills to service resources or mark them as required on work types, you can add details like skill level and duration.
Create Work Type Groups in Salesforce Scheduler: A work type group represents an appointment topic, such as home loan or investment. Create appointment topics that are relevant for your users.
Create Work Types in Salesforce Scheduler: Work types are templates that are included in a work type group —appointment topic— and service territory —branch location, saving you time and making standardizing your appointment scheduling easier. You can set parameters such as the default appointment duration, buffers before and after your appointment, and the appointment availability horizon.
Create and Use Custom Scheduling Policies in Salesforce Scheduler: You can use one or more custom scheduling policies in Salesforce Scheduler flows or API calls. For example, you can create two scheduling policies with different appointment start time intervals. Then, customize your flow to invoke one or the other scheduling policy depending on the work type that users select when scheduling an appointment.
Customize Appointment Booking in Salesforce Scheduler: Customize the Salesforce Scheduler standard flow templates, flow screens, and flow screen components to provide a tailored appointment booking experience for your users, customers, and prospects.
Customize Standard Flow Templates: The flows in Salesforce Scheduler are installed as standard flow templates. You can customize any of the flows to suit your business needs.
Customize the Lobby Management Page: Choose which fields you want to show for the service appointment and waitlist participant cards on the lobby management tab. You can also configure the button names and define the wait time durations.
Customize the Select Appointment Type Screen and the Select Engagement Channel Screen: By default, Salesforce Scheduler shows the Select Appointment Type screen for users to select appointment mediums from. But if the engagement channels are enabled, then Salesforce Scheduler shows the Select Engagement Channel screen. Learn how to customize the screens and the options that appear on the screens.
Customize the Sequence Number on Waitlist Participant Cards: Use a custom field on the waitlist participant object to replace the system-generated 1, 2, 3 prefix on waitlist participant cards. Lobby Management renders whatever value the mapped field contains, so your business logic decides what each card shows.
Data Model Overview: Learn about the objects and relationships within the Salesforce Scheduler data model that represent appointments and employees who can be scheduled to attend appointments.
Debug a Salesforce Scheduler Flow as Another User: Test and debug a flow as another user without logging in as that user. You can troubleshoot a flow by seeing the flow’s debug log as a user sees it.
Define an Appointment Assignment Policy: Define an appointment assignment policy and specify the parameters that are used to calculate the utilization score for service resources.
Appointment Time Slot Calculation for Concurrent Shifts: A territory manager or a service resource creates concurrent shifts by defining the maximum number of appointments for the associated topic. If they create overlapping shifts with a different concurrency for each of these shifts, then Salesforce Scheduler selects the maximum number of concurrency for a shift duration and minimum concurrency while determining the overlapping time slots within these shifts.
Determine Appointment Time Slots with Shifts: To determine time slots with shifts, enable shift-related rules in the scheduling policy. To consider a service territory member’s shifts instead of the service territory member’s operating hours, enable the Use service territory member’s shift option. However, if you want to consider the intersection of shifts and the service territory’s operating hours, then enable the Use service territory’s operating hours with shifts option along with the Use service territory member’s shift option. To consider the account’s operating hours along with the intersection, enable the Enforce Account’s Visiting Hours option.
Salesforce Scheduler Developer Resources: Learn about the various developer resources that are available with Salesforce Scheduler. These resources include REST APIs, Connect REST APIs, Salesforce Platform Events, and Apex classes.
Set Up Outbound Scheduling: Salesforce Scheduler provides standard flow templates to let your internal users (employees) quickly schedule appointments with customers. Users can easily search for and select the right person, topic, location, and date and time of the appointment. You can either use the provided standard flow templates or create flows based on those templates and customize them to suit your business needs.
Manage Drop-In Customers: Territory managers and admins can share waitlists with greeters. If a greeter is assigned to multiple territories, they can manage waitlists for more than one service territory. Based on the reason of the customer’s visit, a greeter checks in a customer to a waitlist, which then notifies the appropriate service resources.
Embed Salesforce Scheduler Flows into Other Flows: You can call a Salesforce Scheduler flow from within another flow that is of the Salesforce Scheduler flow type. For example, you can create and add a Salesforce Scheduler flow to the account page that asks users whether they want to create or modify an appointment. And then it launches the related flow.
Enable Anonymous Resource Scheduling: When anonymous scheduling is enabled, users don’t get to choose service resources during the scheduling process. Also, assigned resources’ names aren’t shown on the appointment summary page. Hiding service resource names from users protects their privacy. It also gives you the flexibility to assign different resources to appointments if the resources initially assigned become unavailable.
Enable Appointment Distribution: Enable the Appointment Distribution and Aggregate Resource Use settings. Then define an appointment assignment policy to calculate resource utilization and link the assignment policy to your scheduling policy.
Enable Appointment Distribution Settings: To enable appointment distribution, enable the Appointment Distribution and Aggregate Resource Use settings. The Appointment Distribution setting provides access to the appointment distribution feature. And the Aggregate Resource Use setting starts the utilization score calculation for service resources. A utilization score is required for appointment distribution to work as expected.
Enable Automatic Service Resource Assignment: When automatic service resource assignment is enabled, your customers or guest users can schedule appointments without selecting a service resource. Based on the selected time slot, an appropriate service resource is automatically assigned to the appointment. You can also configure your flows to give users the option to manually select a service resource or have one assigned automatically.
Enable Capacity-Based Scheduling: To view and control the number of service appointments at a shift and work-type level, enable capacity-based scheduling.
Enable Concurrent Scheduling: Enable Concurrent Scheduling to let users schedule multiple appointments within the same time slot.
Enable Data Translation: Enable users to translate the data for Work Type Group, Service Territory, and Service Resource objects.
Enable Drop In Appointments: To manage customers who visit the branch without prior appointments, enable the Drop In Appointments setting.
Write Salesforce Scheduler Appointments to Salesforce Calendar: Use the Event Management setting to write appointments to Salesforce calendar. Service resources see their scheduled appointments as events on their Salesforce calendar. When you add the Service Appointment field to the Event page layout, the event details page shows a link to the corresponding service appointment in Salesforce Scheduler. Service resources can use the link to open the service appointment directly from the event on their Salesforce calendar. The Assigned Resources related list on the service appointment page also shows a link back to the event on the Salesforce calendar.
Enable the Main Service Resource Setting: To use Omni-Channel service resources with the Agent resource type in Salesforce Scheduler, enable the Main Service Resource setting. When you enable the setting, we recommend that you create only one service resource per user.
Enable Multiple Service Resource Event Setting: To group individual events and view the list of all service resources under a single event, enable the Multiple Service Resource Event setting.
Enable Multiple Time Zone Selection: In your appointment flows, when you set the Show Time Zone Pick List attribute to True, the appointment time slot pages show a dropdown list with all the time zones supported in Salesforce. When scheduling appointments, users can select the time zone in which they want to see the appointment time slots.
Enable the Multiple Topics for Shifts Setting: To add one or more topics to a shift, enable the Multiple Topics for Shifts setting. After you enable this setting, you can’t disable it.
Enable Multi-Resource Scheduling: Turn on Multi-Resource Scheduling to let users schedule groups of resources, as well as assets, for customer appointments.
Enable Service Resource Filtering: Let users schedule appointments faster and with the most suitable service resources by applying service resource filters in your appointment flows. Use the Filter by Resource IDs attribute on relevant flow pages to specify a comma-separated list of service resource IDs. Salesforce Scheduler limits its search to the specified list of resources when getting service resources or service territory slots for appointments. On the service resource selection page, service resources appear in the order in which you specify them in the comma-separated list.
Enable Translation of Custom Field Data: Enable translation of custom field data for Work Type Group, Service Territory, and Service Resource objects. You can enable data translation for custom fields with Text, Text Area, Text Area (Long), Text Area (Rich), and URL types.
Enable Translation Workbench: Use Translation Workbench to specify languages for translation, to assign translators, and to manage your translations.
Engagement Channel Types: Engagement channel types are mediums, such as Phone, Video, and In Person that service resources use to meet customers. Enable the Schedule Appointments Using Engagement Channels setting so that territory managers and service resources can use the engagement channel types and the channel types' junction objects. Territory managers and service resources can define the availability of resources for the engagement channel types by adding one or more channel types to a shift. Salesforce Scheduler shows service resources and resource time slots based on the channel type that a user selects when creating an appointment.
Show Appointments as Events on Salesforce or External Calendars: When you enable the Event Management setting, Salesforce Scheduler writes service resources’ appointments as events on their Salesforce calendar. To write events from Salesforce calendar to external calendars, use a calendar sync tool such as Einstein Activity Capture. If a calendar sync tool doesn’t work for you, enable the Publish Appointments as Platform Events setting to trigger platform events when appointments are created, modified, or deleted in Salesforce Scheduler. Then, subscribe to the new AppointmentSchedulingEvent platform event and use an API to write the platform events to an external calendar.
Write Salesforce Scheduler Appointments to External Calendars: Enable the Publish Appointments as Platform Events setting, subscribe to the AppointmentSchedulingEvent platform event, and then use APIs to write appointments to external calendars.
Extend Location Search: Enable location search to let users search for and select appointment locations when scheduling appointments.
Filter Work Type Groups: Let users schedule appointments faster and with relevant work type groups by applying work type group filters in your appointment flows. Specify a list of comma-separated work type group IDs in the Filter by Work Type Group IDs attribute on the Select Work Type Group flow page. Salesforce Scheduler shows only the work type groups that you specify in the list of work type groups. For example, a customer wants to book an appointment with a banker who has expertise in wealth management and is also fluent in the Spanish language. For this customer, you can only specify work type groups IDs that match the criteria. On the work type group selection page, work type groups appear in alphabetical order.
Customize Flow Screens: You can customize flow screens to meet your business needs. For example, you can change labels to use your company's terminology and change the preselected values.
Flow Action: Cancel Appointment: Use the Cancel Appointment action to cancel appointments and to capture cancellation reasons.
Salesforce Scheduler Flows: Salesforce Scheduler includes standard flow templates that are specific to scheduling inbound and outbound customer appointments. Use the provided Salesforce Scheduler flows or customize them according to your company’s needs.
Flow Screen Component: Configure Rates: Users can configure the rate card for selected work types and service territories by using the Configure Rates component.
Flow Screen Component: Payment Link: Users can generate a payment link to email or share using other communication channels by using the Payment Link component.
Flow Screen Component: Payments Page: Users can enter their payment details to pay for service appointments by using the Payments Page component.
Flow Screen Component: Select Payment Parameters: Users can select an object (such as service territories or work types) to define their payment configuration by using the Select Payment Parameters component.
Flow Screen Component: Select Service Resources: With the Select Service Resources Flow Screen component, users can select service resources (internal appointment attendees) for an account, case, lead, or opportunity record.
Flow Screen Component: Service Appointment Summary: Users can review service appointment details and enroll in or unenroll from the service appointment by using the Service Appointment Summary component.
Flow Screen Component: Service Appointment Confirmation: Users can use the Service Appointment Confirmation component to show the confirmation and summary information for a service appointment based on its action status.
Field-Level Security (FLS) Permissions Checklist: With field-level security (FLS) settings, you can restrict your users’ access to view and edit specific fields. You can also use FLS settings to provide access to fields that are required to create and modify appointments. If you face FLS permission errors, ensure that users have the necessary field-level permissions.
Checklist to Troubleshoot Flow Screens in Salesforce Scheduler: Salesforce Scheduler uses various settings, policies, and filters to show records on flow screens. When users don't see records on flow screens, troubleshoot using these steps. Before you troubleshoot, check data permissions and field-level permissions to confirm that users have the necessary access.
Generate an Appointment Invitation URL: Generate appointment invitation URLs to share with your customers. Customers can use appointment invitation URLs to quickly book an appointment.
Generate QR Codes for Lobby Management: Greeters can generate QR codes for service territories and waitlists. You can also download the QR code for display, printing, and offline use.
Get Started with Salesforce Scheduler: Learn about the capabilities of Salesforce Scheduler, who can use it, the licenses required to use it, and what it provides. Also, learn about the key terms, roles, the data model, and available resources.
Grant Guest Users Required User and Object Permissions: To schedule appointments, guest users need certain user and object permissions. You can grant these permissions to guest users through the guest user profile for your Experience Cloud site.
Set Up Salesforce Scheduler and Book Appointments: Salesforce Scheduler, formerly Lightning Scheduler, gives you the tools to simplify appointment scheduling in Salesforce. Create a personalized experience for scheduling customer appointments—in person, or by phone or video—with the right person at the right place and time. Optimize resource scheduling by using advanced features, such as appointment distribution and service resource filtering. Provide appointment booking experience from Salesforce Lightning Service Console, Experience Cloud sites, and your company websites.
Appointment Sharing: This topic explains how appointment sharing works when you enable the resource appointment sharing feature.
How Salesforce Scheduler Determines Available Time Slots: When users schedule a service appointment, Salesforce Scheduler uses multiple factors, such as field values, scheduled appointments, absences, Scheduler Settings, and Scheduling Policies to determine available time slots.
How Salesforce Scheduler Tracks Appointments: When a lead is converted or when accounts are merged, Salesforce Scheduler updates the Parent Record field for associated service appointments. Salesforce Scheduler also updates the Related To field for associated Salesforce calendar events.
How Work Types, Work Type Groups, and Service Territories Work Together: Work types are appointment templates that define key parameters, such as appointment duration, preparation and wrap-up buffers, and availability time frame. Work types also map skill requirements for work type groups to ensure that users can create appointments only with service resources who have the necessary skills. A work type links service territories (branch or office locations) to work type groups (appointment topics).
Identify Missing Permissions: Verify if a user is missing permissions based on the selected scheduling policy. Salesforce Scheduler Troubleshooter only checks whether the minimum permissions required to schedule an appointment are met. You can also check whether the user is missing access permission for a record.
Identify Validation Issues with Records: Check whether a record or record relationship has a validation issue. To validate a single record requires one object and a corresponding record. To validate a record relationship, you additionally provide a primary record ID and multiple related record IDs.
Set Up Scheduling for Authenticated External Users: With Salesforce Scheduler, your authenticated external users (customers and partners) can use standard flow templates to quickly schedule appointments with your employees. Users can easily search for and select the right person, topic, location, and date and time of the appointment. You can either use the provided standard flow templates or create flows based on those templates and customize them to suit your business requirement.
Key Roles in Salesforce Scheduler: Learn about the roles in Salesforce Scheduler—such as administrators, service resources, service territory managers, and customer care representatives—and what each role can do.
Key Terms in Salesforce Scheduler: List of key terms—such as service resource, service territory, work type group, work type, and skills—and their descriptions.
Licenses for Salesforce Scheduler: Users who book customer appointments, users who take customer appointments, and assets require different licenses.
Lightning Web Components (LWC) for Salesforce Scheduler: With Spring '26, Salesforce Scheduler now supports all flow screen components as Lightning Web Components. This enables you to deploy any scheduling flow in Lightning Web Runtime (LWR) sites. Previously, some flow screen components used Aura components and were limited to Aura-based sites.
Lobby Management: Use lobby management to manage customers who prefer to visit the branch location—with or without a scheduled appointment. With lobby management, greeters can manage scheduled service appointments and drop-in appointments. They can also view the estimated wait time for appointments.
Estimate Wait Times: When a customer joins a queue, Lobby Management can calculate and estimate their wait time.
Lobby Management for Drop In Appointments: With Drop In Appointments, you can easily manage customers who visit your business locations without prior appointments. Territory managers can create waitlists—virtual queues— for their service territories, while greeters can capture and add customer details to the waitlists. Service resources get notified about and can accept drop-in appointments while customers wait in the lobby.
Lobby Management for Scheduled Service Appointments: Greeters can use lobby management to check in customers, monitor their wait time, or mark them as a no-show. Greeters can also reschedule or reassign an appointment if the assigned service resource is unavailable. Lobby management notifies service resources when their customers are waiting to be attended.
Subscribe to Lobby Management Greeter Dashboard Events: When a greeter changes the service territory in the Lobby Management dashboard, Salesforce Scheduler publishes a Lightning Message Service (LMS) event on the lightning__appointmentBooking_greeterDashboard channel. Subscribe from a custom Lightning web component or Aura component to keep custom waitlists, appointments, or data views in sync with the selected territory.
Roles in Lobby Management: Learn about the roles in lobby management—such as administrators, greeters, and drop-in customers—and what each role can do.
Guest Service Appointment Management in Salesforce Scheduler: Guest users can modify appointments to reschedule them or change service resources, and cancel appointments. To notify guest users of their scheduled appointment, configure email notifications by using the available email templates. The email templates include the links that invoke the flow that modifies and cancels a guest user service appointment. If a guest user cancels the appointment, the confirmation email template includes a link to create another appointment.
Manage Availability and Exceptions in Salesforce Scheduler: Specify the availability of service resources, operating hours of service territories and work types, and visiting hours for accounts. Manage exceptions, such as holidays, absences, and manually created calendar events. To specify the rules that must be used by Salesforce Scheduler Engine to determine the available time slots, configure scheduling policies and Scheduler settings. Set up features to handle appointment distribution, multiresource scheduling, and concurrent scheduling.
Manage Objects’ Data Translations: You can manage data translation for Work Type Group, Service Territory, and Service Resource objects. Use data translation to build Scheduler’s appointment booking experience in multiple languages. For example, you can translate the work type group names and their description to Spanish for a customer who uses the website in Spanish to schedule appointments.
Configure Who Can Be a Service Resource: Service resources are individual users in your org who can attend appointments with clients. Before you can create service resources, create or identify users who you want to be available as service resources. Then, assign them the Salesforce Scheduler permission set license via a permission set to make them available for appointments.
Manage Scheduled Appointments Using Lobby Management: In lobby management, the Scheduled Service Appointments list shows current, upcoming, and past appointments. Use various options in the Scheduled Service Appointments list to view and manage appointments scheduled for a day.
Manage Shifts in Salesforce Scheduler: Shifts enable service resources to set up and update their frequently changing work hours. Service resources can set up shifts for different work hours for the same service territory, set up shifts beyond their service territory’s operating hours, and even set up shifts for more than one service territory.
Manage Time Zones for Appointments: Preset a default time zone for appointment time slot pages or dynamically set a time zone for them. Enable the time zone dropdown list on time slot pages to let users schedule appointments in the time zones they prefer.
Manage Waitlists: Waitlists are virtual queues that a greeter uses to check in drop-in customers and to notify service resources while the customers wait in the lobby. Territory managers can create waitlists for their service territories and relate work types and service resources to these waitlists.
Set Up the Outbound Modify Appointment Flow: To give your users access to the Outbound Modify Appointment flow, add the Modify Service Appointment action to the service appointment page layout.
Modify a Guest Service Appointment: Guest users can reschedule a service appointment to change the appointment date and time or the selected service resources.
Make the Inbound Flow Available as an Outbound Flow: To provide the inbound flow as an outbound flow, use the Outbound flow available to community users attribute. With the outbound flow enabled, service resources who are contractors can create and manage service appointments for either an account, opportunity, or lead. Contractors can also request their assistants to book appointments on their behalf.
Modify the Review Service Appointment Screen: To modify the Review Service Appointment Screen layout for users, change the Service Appointment layout assigned to the users' profile.
Multiple Service Resource Events: After enabling the Multiple Service Resource Event setting, Scheduler groups individual events and lists all attendees (service resources) under a single event.
Multiple Topics for Shifts: To add one or more topics (work type groups or work types) to a shift, enable the Multiple Topics for Shifts setting.
Considerations for Multi-Resource Scheduling: In multi-resource scheduling, a primary service resource anchors the appointment and must be marked required. The primary service resources are the only service resources whose skills are matched to the skill requirements for an appointment. Other required service resources are matched to the appointment based on their availability and the primary resource’s service territory. Resources not marked required are considered optional.
Manage Appointments with Salesforce Scheduler: Salesforce Scheduler (formerly known as Lightning Scheduler) gives you the tools you need to simplify appointment scheduling in Salesforce. Create a personalized experience by scheduling customer appointments—in person, or by phone or video—with the right person at the right place and time.
Determine Service Resource Availability by Work Type Groups: Salesforce Scheduler uses an intersection of operating hours of Service Territory, Service Territory Member, Work Type, and Account to determine service resource availability based on the scheduling policies and scheduler settings. If you want Salesforce Scheduler to also use work type groups to determine availability, enable the Operating Hours for Service Territory Members for Work Type Groups preference in Scheduler Settings. Then, enter work type groups for service territory member operating hours in service territory member records. This setting is enabled by default for orgs created after Summer ’21.
Before You Begin: Before you turn on payments in Salesforce Scheduler, set up Salesforce Payments.
Set the Payment Method Set Key: When booking a paid appointment, Salesforce Scheduler uses the specified payment method set to show payment options.
Configure Rate Cards: Salesforce Scheduler determines the price of a service appointment using its related work types and service territories. To set prices for service appointments, select combinations of work types and service territories and then set their base price.
Turn On Payments: Enable payments in your Salesforce org to enable paid service appointments.
Prerequisites for Using Engagement Channel Types: Salesforce Scheduler uses the Shift Engagement Channel junction object to relate engagement channel types to shifts and the Engagement Channel Work Type junction object to relate the engagement channel types to work types. Before you enable the Schedule Appointments Using Engagement Channels setting, complete these prerequisites.
Prerequisites to Enable Multiple Topics for Shifts Setting: The Multiple Topics for Shifts feature uses the Shift Work Topic junction object to manage topics supported by shifts. Salesforce Scheduler flows and APIs also use this junction object. Before you enable the Multiple Topics for Shifts setting, migrate information related to supported topics from shift records to shift work topic records and clear the existing work type and work type data.
Preselect an Option on the Select Service Resources Page: Save a click when scheduling an appointment by preselecting an option on the Select Service Resources page. Enter an appropriate value in the Selected Option attribute, depending on the option you want preselected on the page. Or use the selectedTriageOption variable to set the value of the attribute.
Preset a Time Zone for Appointment Time Slot Pages: Use the Default Time Zone attribute in Salesforce Scheduler flows to set a default time zone for all the pages that show appointment time slots. Or dynamically set a time zone for each page according to the selected service resource, service territory, customer, or browser time zone.
Manage Access to Salesforce Scheduler Flows: Use flow access to limit users who can edit and run flows, with the Salesforce Scheduler Flow process type, based on their user records, profiles, or permission sets. To apply more granular security to an individual flow, override the default behavior of the flow. And then grant access to the flow based on user profiles or permission sets.
Salesforce Scheduler Standard Flow Templates: The Salesforce Scheduler standard flow templates walk users or customers through scheduling, modifying, and canceling appointments.
Check External Calendars to Determine Resource Availability: When you run a Salesforce Scheduler flow or make an API call, the Apex interface makes a synchronous call to the Apex class. The Apex interface passes the details of the requested service resources and timelines for which Salesforce Scheduler wants to find the resources’ availability on the external calendar. The Apex class checks the external calendar events and returns the time slots where resources aren’t available. Salesforce Scheduler excludes the unavailable time slots during appointment scheduling.
Check External Systems to Determine Availability of Service Resources: Use the provided LxScheduler.ServiceResourceScheduleHandler Apex interface to write an Apex class that checks external systems, such as external calendar events, to find time slots where service resources are already booked. Then associate this Apex class with Salesforce Scheduler flows or API calls through the Check External Systems for Resource Availability scheduling policy rule.
Check Salesforce Calendar to Determine Resource Availability: Enable the Check Salesforce Calendar for Resource Availability scheduling policy rule if you want Salesforce Scheduler to avoid scheduling conflicts with manually created calendar events.
Reassign Multiple Service Appointments: Reassign multiple service appointments of a service resource to change the primary or required service resource. You can either select a preferred service resource to reassign service appointments or reassign service appointments to the service resources that Salesforce Scheduler suggests based on the availability.
Update Flows to Refresh Inputs: Configure your Salesforce Scheduler flows to ensure that when users go back to a page and make changes during appointment scheduling, the changes are reflected on the subsequent pages. Otherwise, if a user doesn't select the right value on a previous page, they must cancel the scheduling process and start over.
Restrict Service Resources from Modifying Shifts for Two Weeks with an Apex Trigger: Service territory managers work with their service resources to plan shifts in advance. For example, you want to make an appointment booking available for two weeks starting from the current day. As a result, you want to prevent service resources from modifying their shifts during that period. To restrict a service resource from making any updates to shifts for two weeks, create an Apex trigger.
Restrict Working Hours Selectively: If you enable the Use service territory’s operating hours with shifts scheduling policy, Salesforce Scheduler uses the intersection of shifts and service territory operating hours to determine the availability of all service resources. However, if you want to restrict working hours to service territory operating hours only for a few service resources, use triggers.
Salesforce Scheduler Resources: A list of resources—such as videos, Trailhead, developer guide, and implementation guide—that help you work with Salesforce Scheduler.
Set Up the Outbound New Appointment Flow: To give your users access to the provided Outbound New Appointment flow, add the Schedule Appointment action to lead, account, person account, and opportunity page layouts.
Cost-Effective Alternative for Creating Service Resources: Salesforce Scheduler is an add-on based product. It requires a base license, such as Sales Cloud, Service Cloud, Lightning CRM, or Platform Starter, to operate. If you’re looking for a cost-effective alternative to these base licenses, try the Platform Starter license, a license with limited capabilities. Assign the Lightning Platform Starter license and the Salesforce Scheduler add-on to users, such as sales associates and healthcare providers, who don’t schedule their own appointments. Users, such as customer service representatives, community users, or guest users, can create service appointments for these service resources.
Select Scheduling Policy Rules to Enforce: If you don’t create and use a custom scheduling policy in your flows or API calls, the Default Appointment Scheduling Policy is used. You can edit the Default Appointment Scheduling Policy and select the rules that you want to enforce during appointment scheduling.
Define Rules for Finding Appropriate Service Resources in Salesforce Scheduler: Use a scheduling policy to enforce rules to help your users find the best service resources for an appointment. The scheduling policy ensures that an appointment meets the criteria that the policy rules define. For example, it considers service resources’ skills and service territory membership when searching for service resources. You can modify the Salesforce Scheduler Default Appointment Scheduling Policy or create custom scheduling policies and associate them with flows or use them in API calls.
Service Resource Availability Sharing by Using an Actionable List: Make it easy and convenient for potential customers to book appointments with service resources. Use the actionable list to create an appointment invitation URL with a service resource’s availability and share the invitation URL with the potential customers via email. You can also use the actionable list to track the appointments that were booked by using that appointment invitation URL.
Set a Time Zone for the Review Appointment Page: By default, the appointment review page shows the scheduled appointment time in the same time zone that was selected on the appointment time slot page. However, you can override the default behavior and set a different time zone for the review page using the Time Zone attribute.
Manage Business Information in Salesforce Scheduler: Manage information related to your business and stakeholders, such as service locations, resources, skills, topics, and appointment templates. To use your company’s terminology, change tab names and field names.
Enable and Configure Capacity-Based Scheduling: Control the number of appointments that can be scheduled for a given shift and type of work. Service resources can control the number of appointments per shift to meet customer needs. Territory managers can choose whether to distribute capacity in a shift for a work topic or across multiple work topics
Enable and Configure Concurrent Scheduling: With concurrent scheduling, it’s easy to schedule multiple customer appointments in the same time slot. For example, a doctor’s office can let several patients book a Monday 1-2 PM appointment to ensure against downtime. Appointments appear as overlapping events on the Salesforce Calendar.
Set Up Group Service Appointments: Use group service appointments to create appointments for a large group of customers, and provide them with the flexibility to enroll in or unenroll from the service appointment. For example, create and allow multiple users to enroll in a resume workshop. Also, directly enroll lead records and authenticated users to the appointment or share the group appointment enrollment URLs with unauthenticated users via email.
Set Up Scheduling for Guest Users: Salesforce Scheduler provides a standard flow template, Inbound New Guest Appointment, to let your unauthenticated external users (leads or prospects) quickly schedule appointments with your employees. Users can easily search for and select the right person, topic, location, and date and time for the appointment. You can either use the provided standard flow template or create a flow based on the template and then customize the new template per your business needs.
Set Up Holidays in Salesforce Scheduler: Service territories can be non-operational due to state or regional holiday, or due to unforeseen circumstances. Territory managers can create holidays and link the holidays to the service territories to avoid bookings on days when the service territory is closed. For example, territory managers can create a holiday for Independence day or for a day when there’s heavy snowfall predicted due to which the branch has to close temporarily. Appointments that are already booked for an unplanned holiday require rescheduling.
Set Up Inbound Scheduling: Set up and configure the provided standard inbound flow templates to let your authenticated external users (customers and partners) and unauthenticated users (prospects) quickly schedule appointments with your employees.
Set Up Guest Service Appointment Modification: Unauthenticated users (prospects) can modify or cancel their appointments after you configure the Inbound New Guest Appointment flow and Modify Guest Service Appointment flow templates. Set up the email notification templates that are sent when your users modify or cancel their service appointments.
Enable and Configure Multi-Resource Scheduling: Multi-resource scheduling lets users create appointments that include more than one required service resource. An appointment can have a maximum of five required service resources: one primary required service resource plus four required service resources, including asset resources.
Set Up Operating Hours in Salesforce Scheduler: Operating hours represent the time slots during which appointments can be scheduled. For example, if a bank allows mortgage appointments at a branch only Monday through Wednesday, from 8 AM to 2 PM, create operating hours for the mortgage work type that reflect this requirement.
Set Up Payments in Salesforce Scheduler: Streamline appointment bookings with the ability to pay for service appointments. Salesforce Scheduler uses Salesforce Payments to integrate payments into inbound and outbound appointment booking flows.
Configure State and Country Picklists: Set up state and country picklists to let users select states and countries from a predefined, standardized list instead of entering state and country data into text fields.
Set Up Roles and Hierarchies for Shifts: Roles and hierarchies define who reports to whom and help define the approval process for shifts. You can assign users who own a specific role for various service territories. For example, Adam is a bank manager and John is a retail banker. You can create a territory manager role and a retail banker role, where the retail banker reports to the territory manager. Assign the territory manager role to Adam and the retail banker role to John. By using this hierarchy, Adam can create shifts and then ask John to confirm his availability by approving shifts.
Set Up Approval Process for Shifts: Streamline updating shift statuses by enabling the approval process. With the approval process, service resources and territory managers receive email alerts when a shift is created, approved, or rejected.
Set Up Service Territories in Salesforce Scheduler: Create and configure service territories to organize your service resources and ensure that they’re assigned to appointments near their home branch.
Set Up Video Appointments with Amazon Chime: Salesforce Scheduler provides integrated Amazon Chime for video calls. The feature operates in the Bring-Your-Own-Application (BYOA) model and requires that you have an Amazon Chime account. After you enable and configure video call settings, Salesforce Scheduler uses Amazon Chime for all video appointments. Salesforce Scheduler also provides Virtual Appointment Email templates that you can use to send notifications to unauthenticated users for upcoming video appointments.
Explore the Salesforce Scheduler Setup Assistant (Optional): The Salesforce Scheduler Setup app includes a Salesforce Scheduler Setup Assistant tool that you can use to perform key setup tasks, including assigning permission sets, creating appointment resources, and embedding appointment scheduling into leads and referrals, cases, opportunities, and accounts. Alternatively, you can perform these tasks from Setup and object tabs in the Salesforce Scheduler Setup app.
Share Service Appointments with Assigned Service Resources: When you enable the Resource Appointment Sharing setting, Scheduler automatically shares a newly created service appointment with all assigned service resources. This setting provides appropriate permissions to service resources to manage their service appointments.
Share Service Resource Availability by Using an Invitation URL: Service resources or their assistants can share the time period during which the resources are available for appointment booking. They can define and share the appointment criteria with users by creating an invitation URL. Users can navigate to the invitation URL and book an appointment. The URL directs users to the starting week of when the service resource is available.
Share Service Resource Availability with Actionable List Members: Make it easy for potential customers to schedule an appointment by sharing your availability. You can send an email invitation to customers with a URL to your calendar. You can generate an appointment invitation only for your availability and not on the behalf of any other service resource.
Manage Your Shifts in Schedule View: Schedule view shows shifts grouped by service resources or by work type group in a calendar format. The view makes identifying tentative, published, and confirmed shifts easy. The view also shows service resources’ absences and service territories’ holidays.
Show Images on Service Resource Cards: Use formula fields to show various types of information, such as ratings and status, as images on service resource cards.
Skip the Service Territory Selection Screen: If you want to use virtual territories or set a default service territory, modify the flow to set a default service territory and skip the Select Service Territory screen. You can skip the service territory selection screen for the Outbound New Appointment, Inbound New Appointment, and Inbound New Guest Appointment flows and their instances. You can also show the service territory address on the review screen if necessary.
Supported Licenses for Authenticated External Users: To configure inbound scheduling in your Experience Cloud site or on your website, your authenticated external users must have one of these communities licenses. Communities licenses are used with Experience Cloud sites and legacy portals. Browser support for Experience Cloud sites varies by the device on which you access the site or the template.
Troubleshoot Issues with Appointment Scheduling: Verify whether your users have the required field-level permissions to manage appointments. Identify and fix issues related to the availability of records on flow screens that can occur when your users are managing appointments.
Salesforce Scheduler Troubleshooter: Salesforce Scheduler uses scheduling policies and other settings and permissions to show records and time slots for appointment scheduling. Salesforce Scheduler Troubleshooter verifies whether the data is set up accurately, users have the relevant permissions, and the object records are shared appropriately. Users with the out-of-the-box System Administrator profile can run Troubleshooter at any time—before or after setup—to identify and fix issues related to org, service resource, and Experience Cloud user setup.
Troubleshoot Service Resources: Use these steps when Salesforce Scheduler doesn't show a service resource when users run a flow.
Troubleshoot Service Territories: Use these steps when Salesforce Scheduler doesn't show a service territory when users run a flow.
Troubleshoot Time Slots: Use these steps when Salesforce Scheduler doesn't show time slots when users run a flow.
Identify Missing Time Slots: While scheduling an appointment when you can’t find a specific time slot, you can look into the reason, such as the service resource is already booked or doesn’t have the required skills.
Troubleshoot Work Type Groups: Use these steps when Salesforce Scheduler doesn't show a work type group when users run a flow.
Reasons for Missing Time Slots: The Salesforce Scheduler Troubleshooter identifies these reasons for missing time slots.
Record Validations: Salesforce Scheduler Troubleshooter can return these reasons when validating objects and related objects.
Update Field-Level Security for Multi-Resource Scheduling: Update the field-level security settings on the Primary Resource field on the Assigned Resource object for all user profiles that need to access multi-resource scheduling.
Set Email Field-Level Security to Share Availability Using an Actionable List: To invoke the Send Appointment Invitation to Actionable List Members standard flow for sharing availability using an actionable list, configure the field-level security on the Email field on the contact, lead, and person account objects.
Update Service Appointment Record: Add the service resource name to the Comments field of the service appointment. You can customize the flow to add the service resource name to a custom field.
Use Service Territory Time Zone on Flow Screens: By default, Salesforce Scheduler shows time based on the time zone of the user who's scheduling the flow. But sometimes it makes more sense to show time based on the time zone of the selected service territory. For example, when customer service representatives schedule appointments for multiple locations. In such scenarios, set the value of the DefaultTimeZone variable to use the service territory time zone.
Define Shift Rules in Scheduling Policy: To use shifts instead of the service territory member’s operating hours when determining available time slots, enable shift-specific rules in the scheduling policy.
View Maximum Schedulable Assets in Salesforce Scheduler: Each active asset type resource is included in the schedulable asset limit for your organization. You can view your asset limits and usage counts in the Usage based entitlements report.
Change an Actionable List Member Status and View Appointment Details: After a service resource shares their availability with the actionable list members, Salesforce Scheduler updates their status. If the status isn’t updated automatically, you can update it manually. You can also view the appointments a customer creates using the appointment invitation.
Virtual Territories: Admins and territory managers can create virtual territories to give customers and service resources the flexibility to take appointments from anywhere. A virtual territory is a service territory that is created without an address for a group of service resources that are available for appointments on virtual channels, such as phone and video.
What’s Included in Salesforce Scheduler: Salesforce Scheduler provides the objects required for appointment scheduling and an app that makes it easy to set up Salesforce Scheduler. It provides preconfigured, customizable flows and rules that provide appointment booking experience. It also provides business APIs to create appointment booking experiences.
Create and Manage Outbound Appointments in Salesforce Scheduler: Use Salesforce Scheduler to schedule an appointment with a customer and an assigned resource or resources. Modify an appointment to reschedule it to a different date or time or to add more service resources. Cancel the appointment if the customer can no longer make it. After you schedule an appointment, deleting service resources, modifying work type durations, or modifying the appointment to remove assigned service resources can result in unexpected behavior.
Create and Manage Inbound Appointments in Salesforce Scheduler: Customers, partners, and prospects can use Salesforce Scheduler to schedule appointments with your service resources. They can also modify appointments to reschedule them or add service resources, and cancel appointments. After an appointment is scheduled, deleting service resources, modifying work type durations, or modifying the appointment to remove assigned service resources can result in unexpected behavior.
Apex-Based Custom Lightning Types: An Apex-based custom Lightning type uses an Apex class to define its schema. Instead of manually creating fields, you map the type directly to your Apex class structure. This method is ideal when you have a complex data structure already defined in your Apex class code.
Create a Custom Lightning Type: Define data structures and user interface configurations for supported platform features. You can base your type on an Apex class to ensure data consistency, or define a custom structure manually by using a JSON schema.
Lightning Types: Lightning types are JSON-based data types used to structure, validate, and display data. While Salesforce provides a set of standard Lightning types, you can create custom Lightning types to customize the UI experience based on your business requirements.
Object-Based Custom Lightning Types: With an object-based custom Lightning type, you can define a schema manually by specifying fields. This method is ideal when you want to structure data without referencing an Apex class.
Custom Lightning Types Overview: Learn about custom Lightning types, the benefits they provide, and how field mapping works.
Manage Public Group Membership: In public groups, you can assign and remove members such as users, other groups, roles, and portal roles. Where you manage public group membership depends on the type of updates that you’re making.
See Your Managers in the Role Hierarchy: The Managers in the Role Hierarchy related list shows all of the users above you in the hierarchy. These users have the same access to your data as you do—they have access to all data you own or that has been shared with you.
Set Page Layouts and Field-Level Security: Use field-level security as the means to restrict users’ access to fields; then use page layouts primarily to organize detail and edit pages within tabs. This reduces the number of page layouts for you to maintain. For example, if a field is required in the page layout and read-only in the field-level security settings, the field-level security overrides the page layout and the field is read-only for the user.
Manage Scratch Orgs: The scratch org is a source-driven and disposable deployment of Salesforce code and metadata, made for developers and automation (CI/CD). A scratch org is fully configurable, allowing developers to emulate different Salesforce editions with different features and preferences.
Sharing and Record Access Features: In Salesforce, you can control access to data at many different levels. Set up the access that users have to records they don't own using the various sharing and record access features, all of which achieve a different use case.
Manual Sharing Considerations: When you grant access to records with manual sharing, there are some considerations to keep in mind.
Mass Quick Actions: With mass quick actions, users can create or update up to 100 records from a list view or related list. Users can select one record in the list to update only that record, or multiple records to perform bulk updates. To help users understand the changes they’re making, the action window includes a Fields to update section when users update more than one record.
Mass Quick Action Considerations: Review these guidelines and considerations before setting up and using mass quick actions in list views.
Set Up a Mass Quick Action for List Views: With mass quick actions on a list view, users can create or update records in bulk rather than one at a time. You can configure a mass quick action for cases, leads, accounts, campaigns, contacts, opportunities, work orders, and custom objects that support quick actions and have a list view button layout in Lightning Experience.
Set Up a Mass Quick Action for Related Lists: With mass quick actions on a related list, users can create or update related records in bulk without leaving the page. You can configure a mass quick action on related lists for any related object that supports quick actions.
Merge Field Syntax: A merge field’s syntax can vary depending on where you use the field. To make sure that you use the correct syntax, select merge fields from the dropdown list in the editor where you use the merge field.
Merge Field Tips: Here are a few pointers for getting the most out of merge fields.
Metadata and Data Deployment from DX Inspector: Quickly move metadata and configuration data from your current Salesforce org to a target org in a single orchestration. This type of direct deployment from DX Inspector is ideal for moving small, specific changes without using a full DevOps pipeline.
Migrate from Profiles to Permission Sets: To simplify user management and encourage the principle of least privilege, we recommend that you use permission sets and permission set groups to manage your users’ access, rather than profiles. Before you transition to a permission set and permission set group-led security model, review this guidance on successfully planning and executing this migration.
Modify Field Access Settings: From the field accessibility grid, you can change a field’s accessibility in the page layout or in field-level security.
Modify Standard Auto-Number Fields in Salesforce Classic: The unique identifiers for solution, case, and contract records are standard auto-number fields. Each record is assigned a unique number with a specified format upon creation. You can modify the format and numbering for these auto-number fields in Salesforce Classic.
Manage API Usage Notifications: When you create a request usage notification, you specify an administrator to receive an email notification whenever your organization exceeds a specified limit for the number of API requests made in a specified span of hours.
Enable MuleSoft Direct: Let Salesforce admins discover and deploy pre-built MuleSoft Direct integrations directly from Salesforce.
Enable API Catalog Support for MuleSoft APIs and MCP Servers: Let API Catalog sync MuleSoft APIs and MCP servers from Anypoint Platform. Salesforce admins can then use API Catalog to activate actions for MuleSoft APIs and allow tools for MuleSoft MCP servers to use in Agentforce.
Manage Capabilities for MuleSoft in Salesforce: After you establish a trusted connection between your Anypoint Platform and Salesforce organizations, you can enable and disable MuleSoft capabilities supported in the Salesforce organization.
About Next Best Actions: Create and display offers and actions for your users that are tailored to meet your unique criteria. Develop a strategy that applies your business logic to refine those recommendations. Your strategy distills your recommendations into a few key suggestions, like a repair, a discount, or an add-on service. Show the final recommendations in your Lightning app or Experience Builder site.
Display Recommendations: After creating a strategy, choose a page to run your strategy and display your recommendations. You can use a Lightning record page, an app’s home page, an Experience Cloud site page, a Visualforce page, or an external site, depending on where you want recommendations to appear.
Building a Strategy: A strategy determines when and how to present an Einstein Next Best Action recommendation on a Salesforce Lightning record page. For example, if you want to offer a discount to a subset of customers, create a strategy that collects the appropriate customer records and identifies the discount option to present. To create a strategy, you can use Flow Builder (recommended) or Strategy Builder.
Flow Builder Strategies: A Flow Builder strategy specifies business logic and generates output for an Einstein Next Best Action component on a Salesforce Lightning record page.
Strategy Builder Strategies: You can create strategies for Einstein Next Best Action using Strategy Builder or Flow Builder. Flow Builder is the recommended method.
Use Customer Satisfaction to Drive Recommendations: Use Einstein Next Best Action to tailor recommendations based on customer satisfaction scores. For example, offer a service contract discount to customers with low satisfaction or a new product preview to those with high satisfaction. Drive retention and upsell with targeted offers.
Offer a Gift Basket to Each Account: Use a Next Best Action component on the Lightning Account record page to offer a gift basket to each of your accounts. When a customer accepts the offer, a form opens to collect the recipient’s name and shipping address. After the form is submitted, a request email is sent to the shipping department.
Get Started with Einstein Next Best Action: Just getting started with Einstein Next Best Action? Follow these steps to complete each phase of the Next Best Action setup process, create personalized recommendations for your users, and put decisions into action.
Einstein Next Best Action Component: Einstein Next Best Action uses strategies that apply your org’s business rules to display context-sensitive suggested offers and actions on your Lightning record pages.
Launch a Flow When a Recommendation Is Accepted: Each recommendation is associated with a single flow. By default, Next Best Action launches a flow when a user accepts a recommendation. The flow then performs an action, such as updating a case or sending an email.
Launch a Flow When a Recommendation Is Accepted or Rejected: Each recommendation is associated with a single flow. By default, Next Best Action launches a flow when a user accepts a recommendation. The flow then performs an action, such as updating a case or sending an email. But you can also launch a flow when a user rejects a recommendation, which gives you more flexibility. For example, a flow could run an automated process, write to another system, or create a reminder email when a recommendation is rejected.
Add a Limit Repetitions Element to a Next Best Action Flow: You can add a Limit Repetitions element to your Recommendation Strategy flow to limit the number of times that the same recommendation or offer appears on the same record or for the same user during a time period.
Einstein Next Best Action Entitlements: Einstein Next Best Action has usage-based entitlements. All orgs receive a free monthly allowance of Next Best Action requests. If your usage exceeds your allowance of free monthly requests or any entitlements that you purchase, Salesforce contacts you to discuss additions to your contract. To track your usage, from Setup, navigate to Company Information.
Create a Custom Notification Flow for Next Best Action: Create a trigger in Process Builder to receive direct notifications about errors occurring in your strategies. Launch a flow to send error information to your desired targets.
Recommendation Fields: Recommendations are suggested actions that users see and interact with through Einstein Next Best Action strategies. When creating a recommendation, use these fields to define its look and feel.
Create Recommendations: Create offers or actions to recommend to users using Einstein Next Best Action. Recommendations are standard Salesforce records, similar to accounts and contacts, that are processed by strategies and associated with flows. Strategies determine which recommendation records are surfaced using business rules, predictive models, and other data sources. The result of this process is context-specific recommendations that you present to your users.
Report On and Track a Recommendation: Create a custom report type to report on and track recommendation data and strategy metrics. You can see the monthly total recommendations that a Salesforce org’s strategies served. And you can analyze which recommendations are accepted and rejected, who responds to them, and more.
Create a Strategy with Strategy Builder: Once you’ve created flows and recommendation records, use Strategy Builder to funnel the correct recommendations to your users at the right time.
Tour the Strategy Builder Interface: Before you start building your strategy, learn about the primary pieces of Strategy Builder and how they work together.
Strategy Builder Elements: Use this page to quickly access a list of Strategy Builder elements and learn how they work together to create unique strategies.
Strategy Builder Branch Selector Element: Filter multiple branches through a branch selector and create unique expressions for each branch. If the expression is true, recommendations in the branch are allowed through and combined into a single branch.
Strategy Builder Enhance Element: Get AI-driven predictions from services such as Einstein Discovery and Einstein Prediction Builder to enhance Next Best Action recommendations with additional information, such as propensity scores. The Enhance element allows you to modify a set of recommendations on the fly, every time a strategy is executed. These recommendations can be static and live as records in Salesforce, or dynamic and sourced from external data sources or other Salesforce objects.
Strategy Builder Filter Element: Create an expression that allows you to block or filter out undesirable recommendations, depending on the context. The expression is evaluated for every recommendation that passes through the branch.
Strategy Builder First Non-Empty Branch Element: The first non-empty branch element allows you to filter branches in the order they appear on the canvas. The first branch that contains recommendations is allowed through, all other branches are blocked.
Strategy Builder Generate Element: With the Generate element, you can dynamically generate personalized recommendations where a large number of possibilities makes it inconvenient to create recommendations manually. The Generate element allows you to create in-memory, on-the-fly recommendations, either from an external data source or from other Salesforce objects.
Strategy Builder Limit Reoffers Element: Determine how often a user sees the same recommendation. You can decide how many times the user must react to a recommendation and how many days to wait before displaying the recommendation again.
Strategy Builder Load Element: Load is the first element in a strategy branch. Load and filter the records of a Recommendation object. Or load and filter the records of any object, and convert them into recommendations at the end of the strategy using the Map element. Your load elements determine which of your recommendations are evaluated when your strategy executes.
Strategy Builder Map Element: The Map element creates Recommendation fields and modifies existing fields using formulas instead of Apex code. Use it to pass data from a Recommendation field with one name to a flow input with a different name, or to personalize Description, Name, and other fields with context-specific data.
Strategy Builder Sort Element: Choose how recommendations are ordered within a branch and reorder them using Recommendation fields.
Write a Strategy Builder Expression: Create unique expressions using logic from the Salesforce expression builder to filter recommendations, select or deselect branches, and determine which recommendations are available for consideration in a strategy.
Create, Package, and Distribute a Strategy Builder Template: Enterprise developers can create and package strategy templates from Developer Edition orgs for use in multiple Salesforce orgs. Independent software vendors can also publish templates on AppExchange for distribution to their subscribers. Strategies not marked as templates in managed packages have intellectual property (IP) protection and can’t be edited or cloned. IP protection safeguards proprietary information in your strategies.
Assign a Default Experience to a User Profile: Assign a default experience to a user profile to associate that profile with a specific community, portal, or site. Any links in the notification lead back to the default experience—no more news from nowhere.
Delegate Site Administration to an External User: Delegate the administration of your site to an external user to increase your site’s capacity for growth and reduce bottlenecks. External administrators can add, update, and disable members, and they can reset passwords and manage user permissions.
SEO Best Practices and Considerations for Guest Users: To configure your site for search engine optimization (SEO), Salesforce uses the guest user profile to identify the public pages and objects available for indexing. A search engine is considered a guest, or unauthenticated, user. For Experience Builder sites, Salesforce automatically generates a sitemap with a list of the publicly accessible content. For sites built with Salesforce Tabs +Visualforce, you’re responsible for creating the sitemap and indicating which pages are included.
About High-Volume Community or Site Users: High-volume community or site users in Experience Cloud are limited-access users intended for orgs that have thousands to millions of users.
External User Access Best Practices: External user access allows individuals outside your organization, such as customers, partners, or contractors, to access specific information and features by logging into your Salesforce environment or a site. To ensure your data is secure, make sure that external users have only the access and abilities required to complete their work.
Configure the Site Guest User Record: Each time an Experience Cloud site is created, Salesforce creates a guest user profile and a site guest user record. The site guest user record is the only user record associated with the guest user profile.
Discover Which Records Are Available to Guest Users: Use Authenticated and Guest User Access Report and Monitoring, available for free on AppExchange to see which objects and permissions users can access from your public sites. The report shows you the total number of records per object that users can access. The report also categorizes records owned by users, records shared with manual or Apex sharing, and queue or public group membership information.
Delegate Account Management to an External User: Give external users the power to manage account members and account brand information. Administrators, internal users, and partner users with the Delegated External User Administrator permission can create and edit a member, reset a member’s password, and activate or deactivate a member. They can also upload brand logos and save company information for co-branded email templates to partner users, and create marketing campaigns, deal notifications, and websites.
Create Reports for Account Relationships: Create a custom report using the Account Relationship object to track your account relationships. Once you’ve created the report, share your information in a dashboard.
Best Practices for Account Relationships: Looking for best practices and use cases to help you get the most out of your account relationships and account relationship sharing rules? You’ve come to the right place.
Assign Records Created by Guest Users to a Default User in the Org: To increase the security of your Salesforce data, guest users are no longer automatically the owner of records they create. Instead, when a guest user creates a record, the record is assigned to a default active user in the org, who becomes the owner.
Create an Account Relationship: When you’ve created an account relationship data sharing rule, assign it to an account relationship to begin sharing.
Configure Account Relationship Data Sharing Rules: After account relationships are enabled, set up an account relationship data sharing rule. This rule defines the relationship type, the type of information shared, and the record access granted.
Considerations for Creating Experience Cloud Site Users: All users who log into an Experience Cloud site must have a record in Salesforce. Their record is created either as a person account or as a contact connected to a customer or partner business account. External users are enabled from the contact record as a customer or partner user, depending on your business relationship.
Set Custom Site Roles: Experience Cloud site members are typically assigned the role of partner, customer, or employee. However, you can create custom roles for users that replace standard ones. You can also choose to display the member’s company name in place of a role.
Add Members to Your Experience Cloud Site: Use profiles and permission sets to manage site membership during the setup process. Adding a profile or permission to a site’s membership gives access to the site to users with that profile or assigned the permission set.
Show Nicknames Instead of Full Names in an Experience Cloud Site: Enabling nickname display in your Experience Cloud site allows more privacy and protects member identities. This protection is especially helpful in a public site where unregistered visitors can access member profiles.
Give External Users Access to Manage Other Accounts: Authorize external users to manage permission sets for other users, reset passwords, activate, deactivate, or add members to other accounts. With the Account Switcher component, external users can easily access the other accounts.
Manage External Users: Create and manage the external customer and partner users who log in to your Experience Cloud sites, and external-facing sites using other clouds such as Commerce Cloud, Financial Services Cloud, Health Cloud, and Work.com.
Files Best Practices and Considerations for Guest Users: To view a file on a record, Experience Cloud site users need access to the record, and record file visibility must allow site users. Use the Customer Access switch on a file’s sharing detail page to allow customers to see individual files on records. Files shared with users, Chatter groups, and topics follow the same sharing model as the objects that the files are shared on. Files in Libraries can be exposed to site users, but the user must be added as a member of the library.
Guest User Setup Checklist: Setting up guest users in your Experience Cloud site requires a number of different settings and configurations. Use this high-level checklist to help you keep track of all the tasks and considerations.
Guest User Security Policies and Timelines: To improve data security for orgs with guest users, Salesforce made some security improvements. Use this topic as a starting point to understand all the security improvements and updates, including timelines for enforcement and how to prepare for the changes.
Review Guest User Object, Record, and Field Access for Sites: When you allow public access to your Experience Cloud sites, make sure that unauthenticated guest users are able to access only the data that you want them to access. Use the Guest User Sharing Rule Access Report page in Setup to quickly see what objects, records, and fields are accessible to your guest users using guest user sharing rules. Experience Cloud sites are used in many ways. While the Guest User Sharing Rule Access Report page evaluates your configuration and flags potentially misconfigured sharing rules, only you know your site’s business needs. Carefully decide which records and fields are accessible to your guest users.
Membership Processing Best Practices: Processing membership when many members are added in a single transaction can result in significant lockout times. Limiting the number of users per transaction can speed up processing time. Follow these best practices to minimize the impact of processing times on members.
Migrate Community Users Between Licenses: You can move community users between certain licenses using Data Loader. For example, you can migrate users between the Customer Community Member and Customer Community Login licenses. Before moving a user to another license, set up a profile for the new license type you are moving the user to.
Account Relationships and Account Relationship Data Sharing Rules: Account relationships and account relationship data sharing rules give you granular control over how account information is shared. They allow you to share object records related to an account, such as cases, opportunities, and contacts. The shared records don’t have to be owned by a user of that account, they just have to be associated with it. You can also determine the access level granted, such as read or write.
Allow External Users to Manage Partner Brands: In addition to administrators and internal users, partner users with the Delegated External User Administrator permission can update and access partner brand information. They can also create co-branded emails, marketing campaigns, websites, and apps for channel sales from information uploaded to the Branding tab.
Allow External Users to Manage Partner Members: In addition to administrators and internal users, partner users with the Delegated External User Administrator permission can activate, deactivate, create, and edit members. They can also reset member passwords.
Partner User Roles: When you enable the first external user on a partner account, a user role hierarchy is created for that account. This role hierarchy rolls up to the account owner (typically, the channel manager). The three roles in this hierarchy are Partner User, Partner Manager, or Partner Executive. When you create contacts on the partner account and convert them to external users, assign one of these roles to them.
Optimize Account Roles to Improve Performance and Scale: If you expect a large volume of business accounts with a single Experience Cloud user, we recommend enabling Account Role Optimization (ARO) to ensure the best performance possible. ARO minimizes the number of roles created for users with licenses that require external user records to be associated with roles. The fewer the roles, the better the performance of your Experience Cloud site.
Sharing Considerations for Using Account Role Optimization in Experience Cloud Sites: The combination of role-based sharing and account role optimization (ARO) provides access to records and reports across accounts in Experience Cloud sites. Consider using targeted sharing access when you activate account role optimization. By using ARO and role-based sharing, an account’s records are exposed to other accounts that roll up to the same shared person role.
Use a Shared Person Account Role for Site Users: Convert single-user accounts associated with sites to use a shared person account role. A shared person account role is one role that the platform creates and assigns to all external role-based users that are in a single-user account.
Give Secure Access to Unauthenticated Users with the Guest User Profile: Use a guest user profile to control public access to data, content, and objects in your site that don't require authentication. For example, you can create a customer support community where existing and potential customers can view public discussions, known issues, and solutions posted by other members or support without logging in.
Reassign Records Owned by Guest Users: After the enforcement of the security policies introduced in Winter ’21, any record created by guest users is assigned to a default internal owner. However, guest users still own records they created before Winter ’21.
Remove Records Shared Manually or via Apex Managed Sharing: With the Guest User Access Report, you can find records that were shared with guest users manually or via Apex sharing before the Winter ’21 enforcement of the guest user security policy. You can then delete the records manually or by using DataLoader.
Remove Guest Site Users from Queues and Public Groups: Queues and public groups created before the Winter ’21 enforcement of guest user security policies can still have guest site users as members. Guest users being part of a queue or public group is a concern because any record shared with the public group is visible to the guest user, which can be anyone on the internet. Also, it’s possible that other members in the group aren’t aware of the guest user’s access to their records.
Securely Share Your Experience Cloud Sites with Guest Users: Experience Cloud sites help you connect with customers and partners. When building your site, you can use various settings and permissions to protect your data and your customers’ data, and publicly share the site with guest users. Keeping your data secure is a joint effort between you and Salesforce.
Secure Data Accessible by Guest Users: Protect your data by securing the data created by unauthenticated guest users prior to Salesforce’s enforcement of the guest user security policies in the Winter ’21 and Spring ’21 releases.
Create a Sharing Set for Experience Cloud Site Users: Give Experience Cloud site users access to records using sharing sets. A sharing set grants site users access to any record associated with an account or contact that matches the user’s account or contact. You can grant access to records via access mapping, which defines access for each object in the sharing set. Access mappings support indirect lookups from the user and target record to the account or contact. For example, grant site users access to all cases related to an account that’s identified on the user’s contact records. A sharing set applies across all sites that a user is a member of. Record access granted to users via a sharing set isn’t extended to their superiors in the role hierarchy.
Upgrade Experience Cloud User Licenses: Upgrading an Experience Cloud user license allows you to give them access to more data within your site. With the right combination of permissions via the user’s new license, profile, role, and permission sets, you can preserve the user’s record and Chatter history.
Site User Visibility Best Practices for Guest Users: Site members and guest users must often see one another in a public setting. Guest user visibility is useful when you implement a public forum, like a self-service community, or build a public-facing app, like ideas. Keep these guest user visibility practices and considerations in mind when setting up your public-facing forum or site.
Who Can See What in Experience Cloud Sites: Experience Cloud sites contain different user types who require varying levels of access. What users can see in a site depends on their user type and which tabs the administrator selects when creating the site. This topic offers a set of tables that describes what users with different access levels can see and do with different site features.
Application Lifecycle Management Journey with Lifecycle Center: Here's a high-level overview of your Application Lifecycle Management (ALM) journey. Start by setting up Lifecycle Center (formerly next-generation DevOps Center), then build your apps in your development environment, and finally, deploy your changes with Lifecycle Center.
Check Promotion Status and Deployment Details: After a promotion completes, confirm the result from the pipeline, the work item record page, or Activity History. If the failure details don't provide enough information, review the deployment details in Setup.
Get Started as a Deployment Manager in Lifecycle Center: Promote approved work items through your pipeline stages from development to production. Coordinate releases, review test results, and ensure quality changes reach production safely. You don't require a developer background for this role.
Fix a Stalled Promotion in Lifecycle Center: If a promotion remains in progress after its deployment succeeds or fails, cancel the associated request record. You can manually clean up a stalled promotion in Lifecycle Center.
Get Started with Lifecycle Center: Lifecycle Center brings modern application lifecycle management and release management to your whole team. Because every change is captured in source control, you get a single source of truth for your team’s changes, so admins, developers, and release managers can collaborate. Follow this learning map to set up governed development environments, coordinate work across teams, validate quality, and deploy changes predictably from development to production.
Get Started with Lifecycle Center by Role: Lifecycle Center (formerly next-generation DevOps Center) supports four roles: admins, development team members, testing managers, and deployment managers. These roles collectively manage projects, code commits, quality gate rules, and pipeline promotions.
Update IP Allowlist for Lifecycle Center: If your source control has IP restrictions, add the required Lifecycle Center IP addresses. Apply these to both the Lifecycle Center Hub org and the target org used by DX Inspector.
Manage Work Items: Use work items to track the progress of changes created for a specific task, such as a user story, feature, or issue. Tracking releases through work items makes it easier to monitor progress and identify concerns.
Promotion Options: Select the promotion type, which changes to apply, and which Apex tests to run when you promote a stage or selected work items.
Run a Validate-Only Deployment: Run a validate-only deployment to check whether a promotion succeeds without saving metadata to the target org or finalizing the merge into the target stage branch. If the validation succeeds and remains eligible, complete promotion within 10 days to deploy the validated changes without rerunning Apex tests.
Set Up Lifecycle Center: Configure Lifecycle Center (formerly next-generation DevOps Center) to manage your release management lifecycle. Review the prerequisites, access the feature, manage users, and set up your projects and pipelines.
Get Started as a Team Member in Lifecycle Center: After your team manager or Lifecycle Center Admin sets up Lifecycle Center, they notify you when the Lifecycle Center org is ready. As part of the setup process, they create one or more projects, pipelines, and work items. They also add each team member’s source-tracked development environment.
Troubleshoot Common Lifecycle Center Issues: Use this quick reference when a work item, environment sync, or source control connection doesn't work as expected in Lifecycle Center.
Validate-Only Deployment: Run a validate-only deployment to find deployment errors, Apex test failures, and code coverage issues without changing the target org or merging branches. If the validation succeeds and remains eligible, complete the promotion within 10 days without rerunning Apex tests..
Lifecycle Center: Lifecycle Center (formerly next-generation DevOps Center) brings modern DevOps best practices to your team with an AI-powered, click-based user interface (UI). Built on the principles of DevOps Center (Managed Package), Lifecycle Center serves as a central development hub where your team can collaborate—with built-in governance that keeps coding agents and users safe and compliant.
Manage Your Notifications with Notification Builder: Keep your users in the know with timely notifications, whether they’re at their desks or on the go. Create custom notifications to give your users new information and reminders. Choose whether Salesforce notifications appear on desktop, mobile, Slack, or at all.
Add a Mobile Action Group for Actionable Notifications: You can now add actions to custom notifications. These notifications appear on a user’s screen, depending on their settings, and can be used for a variety of actions, such as approving requests, following up on deals that might be at risk, or closing a case.
Considerations for Notifications: Learn about the considerations for sending and viewing notifications, such as notification limits.
Create and Send Custom Slack Notifications: Create custom notifications that appear on Slack when important events occur. Use a flow in Flow Builder or the invocable action API to send the notification.
Create a Slack Notification: Define the custom notification’s details, select which Slack app distributes the notification, and then configure the Slack message.
Create and Send Custom Desktop or Mobile Notifications: Create custom notifications that appear on Salesforce desktop or mobile when important events occur. Use a process in Process Builder, Apex code, or the invocable action API to send the notification.
Other Ways to Send a Custom Notification: We’ve made it easy to build notifications using clicks, not code. But if your business needs are more complex, we also support flows and programmatic solutions.
Merge Fields in Slack Notifications: To show record-specific information in your Slack notification, include merge fields in the notification content.
Ways to Send a Slack Notification: Use a flow in Flow Builder to configure how your Slack notification is sent using clicks, not code. But if your business needs are more complex, you can use the invocable action API to send your notification.
OData Adapters for Salesforce Connect: Connect to your back office for a complete view of your business. With the OData 2.0, 4.0, or 4.01 adapter, Salesforce Connect uses Open Data Protocol Version 2.0, Version 4.0, or Version 4.01 to access data that’s stored outside Salesforce.
Lightning Experience Considerations for Salesforce Connect OData Adapters: Users can access external objects from the Lightning Experience app. But some requirements and special behaviors apply when the external data is accessed via the OData 2.0, 4.0, or 4.01 adapter for Salesforce Connect.
OData 2.0 Query Options: By default, the search query string is used as the substringof value in the $filter system query option.
OData 4.0 and 4.01 Query Options: By default, the search query string is used as the contains value in the $filter system query option.
Socrata™ Considerations for Salesforce Connect—OData 2.0 and 4.0 Adapters: Socrata Open Data Protocol™ is commonly used for health data and for collaboration between governments and their citizens. Salesforce Connect can access data from endpoints that are backed by Socrata Open Data Portal. To accommodate Socrata-specific requirements, set the Special Compatibility field on the external data source to Socrata.
External IDs and OData Entity Keys: When you access external data with the OData 2.0, 4.0, or 4.01 adapter for Salesforce Connect, the values of the External ID standard field on an external object are derived according to the entity key that’s defined in the OData service metadata document.
Client-Driven and Server-Driven Paging for Salesforce Connect OData Adapters: It's common for Salesforce Connect queries of external data to have a large result set that's broken into smaller batches or pages. You can decide whether to have the paging behavior controlled by the external system (server-driven) or by the OData adapter for Salesforce Connect (client-driven).
OData Query String Options: The OData adapters for Salesforce Connect use a subset of the OData 2.0 and 4.0 and 4.01 system functions and filter expression constructs to query external systems.
OData Type Mapping: Salesforce Connect maps OData types to Salesforce metadata field types when syncing metadata and converting values between Salesforce and external systems.
OData 2.0 Type Mapping: Understand how the OData 2.0 adapter for Salesforce Connect maps OData types to Salesforce metadata field types.
OData 4.0 and 4.01 Type Mapping: Understand how the OData 4.0 and 4.01 adapters for Salesforce Connect maps OData types to Salesforce metadata field types.
About Flow Orchestration: Review Flow Orchestration permissions, editions, limitations, considerations, and entitlements.
Handle Stage Errors in Orchestrations: Configure fault paths to manage stage errors in orchestrations. Add elements and Go To connectors that run when a stage or its steps encounter errors. These paths help orchestrations complete successfully instead of failing.
Build an Orchestration: Use Flow Orchestration to build sophisticated business processes by combining and coordinating flows.
Make Assigned Work Items Accessible on a Record Page: Add the Orchestration Work Guide component to the record page layouts for record types referenced by interactive steps. Configure the component so that assigned users can access and complete their work items.
Make Assigned Work Items Accessible on an Experience Cloud Site: Add the Orchestration Work Guide component to object detail pages in your Aura and LWR Experience Cloud sites for record types related to interactive steps. Configure the component so that assigned credentialed site visitors can access and complete their work items.
Create a Step to Interact with Users: To assign a step in an orchestration to a person, group, or queue, create an interactive step. An orchestration run creates a work item for each interactive step that it executes.
Use Automatic Output in Orchestrations: An orchestration has access to output for its stages, steps, and decisions. Query the status of any stage or step in the orchestration. Use output parameters from any step’s associated flow. In an orchestration configured to run on API version 58.0 and later, referenced automatic outputs that contain a record or a record collection are refreshed with their latest values each time the orchestration run resumes.
Integrate an Orchestration with External Systems: Add a MuleSoft step to your orchestration to call an imported MuleSoft action. You can also use the $Orchestration.Instance system variable to integrate external systems with your orchestration.
Redirect an Orchestration Path: Flow Orchestration uses Auto-Layout in Flow Builder. In Auto-Layout, elements on the canvas are spaced and connected automatically. Use Go To connectors when you have elements that don’t follow the usual consecutive auto-layout path.
Add an End Element to an Orchestration Path: All elements in an orchestration are connected automatically or connected by Go To connectors that you add manually. To finish a path in your orchestration, add an End element.
Make Work Accessible to Assigned Users: When an orchestration runs an interactive step, it emails a notification to the assigned user, group, or queue. Credentialed Experience Cloud site visitors can see and access their assigned Flow Orchestration work items on the Orchestration Work Item List object page. Internal users and credentialed Experience Cloud site visitors complete their assigned work in the Work Guide.
Create and Use Orchestration Templates: Save orchestrations as templates to reuse them as starting points for new orchestrations. Distribute templates through managed packages so subscribers can build orchestrations based on them.
Publish an Orchestration Event: To allow an external system to make a paused orchestration evaluate its stage and step conditions, add a custom field to the affected object, configure a background step that calls the external system, and then use a record-triggered flow to publish an orchestration event.
Define Requirements for Stages and Steps in an Orchestration: Use requirements to resume an orchestration when a record changes. Define up to 10 requirements to determine when a step is ready to start or when to mark an interactive step or stage complete.
Route Orchestration Work Items with Omni-Channel: To use Omni-Channel routing in Service with orchestration work items, you must have at least one queue associated with the Orchestration Work Item. When you assign an interactive step to that queue, members of the queue receive notifications via the Omni-Channel widget based on your routing logic. Unless you disable default email notifications for work items, queue members also receive email notifications.
Trigger an Evaluation of Orchestration Stage and Step Conditions: Every time a step within the current stage completes, the orchestration evaluates the conditions for that stage and its steps. You can also publish an orchestration event from a flow to trigger an evaluation of orchestration stage and step conditions.
Orchestrations: An orchestration uses stages, steps, and decisions to organize complex business processes.
Error Handling in Orchestrations: Error handling manages unexpected issues that occur in stages during an orchestration run. Configure fault paths for stages to define recovery actions when stage errors occur, ensuring orchestrations complete successfully instead of failing.
Flows in Orchestrations: Each background and interactive step in an orchestration runs an associated flow. If the logic for controlling stage and step execution calls for more than 3 requirements, use an evaluation flow to create more complex criteria.
Evaluation Flows in Orchestrations: When you need more than 3 requirements to control stage and step execution, use an evaluation flow. Select the Evaluation Flow tile in the New Flow window to create an evaluation flow.
Running Context of an Orchestration: The running context determines the access that an orchestration has to Salesforce data and the context used by a paused orchestration to resume. By default, the running context of an orchestration is the Automated Process User in system context.
Orchestration Stages: A stage groups related steps, organizing them into a logical phase. Stages run sequentially, and only one stage in an orchestration can be in progress at a time. You configure the conditions that the stage requires before it’s completed.
Orchestration Steps: Steps are grouped in stages and can be run sequentially or concurrently. Interactive steps assign the completion of an active screen flow to a person, group, or queue and require user intervention. Background steps run an active autolaunched flow synchronously or asynchronously and have no user interaction. MuleSoft steps run an action imported from a MuleSoft operation and have no user interaction.
Flow Orchestration Background Steps: A background step launches an active autolaunched flow and has no user interaction. You can control when a background step is ready to start.
Flow Orchestration Interactive Steps: An interactive step references an active screen flow and generates an orchestration work item. An assigned user completes the active screen flow in the Flow Orchestration Work Guide on the related record page. You can control when an interactive step is ready to start or when its status is set to completed. All interactive steps are processed asynchronously.
Flow Orchestration MuleSoft Steps: A MuleSoft step asynchronously runs an operation imported from a MuleSoft API and has no user interaction. You can control when a MuleSoft step is ready to start.
Triggers for Orchestrations: Create record-triggered orchestrations to respond to record changes that require user input or additional record updates. Specify whether to trigger the orchestration based on new and changed records of a specific object in the Start element. Use Flow Trigger Explorer to manage the order of record-triggered automations.
Orchestration Types: An orchestration’s type determines how the orchestration can be distributed.
Orchestration Versioning: Flow Orchestration has two levels of versioning: the version of the orchestration and the version of a flow called by an orchestration.
Flow Orchestration Work Items: When an interactive step in an orchestration runs, it creates a work item and assigns it to a user, group, or queue. The orchestration run then sends an email with a link to the specified record page to all assigned users. They complete the work in the Orchestration Work Guide component on the specified record page.
Flow Orchestration Entitlements: Flow Orchestration is included in certain editions with no usage-based limitations. An orchestration run is a running instance of an orchestration. An orchestration is an application built by your admin that uses stages, steps, and decisions to organize a complex business process.
Customize Emails to Assignees: By default, each time an orchestration run creates an orchestration work item, assignees receive a notification. To change the email notification sent when an orchestration work item is created, customize the associated approval step.
Deploy Orchestrations with Change Sets: Create, test, and debug your orchestrations in a sandbox. Use a change set to send the orchestration and its associated flows to production when you’re ready to deploy.
Deploy an Orchestration: After you design and test your orchestration, it’s time to put it to work!
Activate or Deactivate an Orchestration: You can have multiple versions of an orchestration in Salesforce, but only one version of each orchestration can be active at a time. You can activate or deactivate an orchestration in Flow Builder or from the orchestration’s detail page in Setup.
Automate Complex Processes with Orchestrations: As your company grows, so does the complexity of your workflows. Processes often require input from multiple users in multiple departments across multiple time zones. This increased complexity results in an increased amount of time spent waiting for each person to complete their task in the proper order. Flow Orchestration helps you streamline this process with orchestrations: multi-step processes that interact with multiple users and systems.
Manage Orchestrations and Work Items: Manage orchestrations and work items with list views. Cancel or suspend a running orchestration. Resume an orchestration run that failed within the previous 14 days because of an error in an action or flow called by a step. Or resume an orchestration run that was manually suspended. Reassign work items that have been assigned, but not completed.
Disable All Email Notifications for Work Item Assignments: By default, an orchestration sends an email notification when an orchestration work item is assigned or reassigned to a user, group, or queue. Disable all work item notifications to stop sending emails to internal users and credentialed Experience Cloud site visitors.
Determine Flow Usage in an Orchestration Version: Orchestration versions use flows to run interactive and background steps. Orchestration version stages and steps can use flows to evaluate complex criteria. Those criteria can determine when a background, interactive step, or MuleSoft step starts and when to mark a stage or interactive step as completed. View the flows that an orchestration version uses to understand the relationships between an orchestration version and the flows it references.
Resume a Failed Orchestration: When an orchestration run failed within the previous 14 days because of an error in an action called by a step, you can fix the error and resume the orchestration.
Resume a Suspended Orchestration: Resume a suspended orchestration run to continue its processing. When a suspended orchestration run is resumed, the suspended stage is also resumed. When the orchestration run is resumed, it evaluates the status of in-progress steps and updates the step status where appropriate. Stored outputs from steps that were in progress when the orchestration run was suspended are processed.
Suspend an In-Progress Orchestration: Suspend an orchestration run to wait until you’re ready to continue. When you suspend a running orchestration, the current stage is also suspended. In-progress steps continue to run, but no new steps are started. If an in-progress step has output, it’s stored so it can be processed when the orchestration is resumed.
Use Orchestration Reports: Use sample Flow Orchestration reports to track orchestration usage. Sample reports include Orchestration Runs, Orchestration Stage Runs, Orchestration Step Runs, Orchestration Work Items, and Orchestration Run Logs. These sample reports are based on the Orchestration Runs Spring ’24, Orchestration Stage Runs Spring ’24, Orchestration Step Runs Spring ’24, Orchestration Work Items Spring ’24, and Orchestration Run Logs Spring ’24 custom report types.
View Orchestration Runs: Use the Orchestration Runs list view to see all in-progress, canceled, and completed orchestration runs in your org. Access orchestration details and history through the orchestration runs list view.
View Orchestration Dependencies in the Automation App: Orchestrations rely on flows to run steps and evaluate complex conditions. To understand the relationships between an orchestration and its referenced flows, view the Usage tab of the Orchestration Version page in the Automation app.
View All Orchestration Work Items: Use the All Work Items list view to see all work items. Use the All Open Orchestration Work Items list view to see all assigned but not completed work items. Assigned users can see and access only their pending work items in the All Open Orchestration Work Items list view.
View Orchestration Work Items on Records: Assigned orchestration work items appear directly on record pages in the Orchestration Work Guide component. Sort items by date, prioritize tasks, and track completion status.
Orchestration Run: An orchestration run represents an instance of a running orchestration.
Flow Orchestration Reference: Bookmark this page for quick access to information about orchestration elements, resources, events, and more.
Flow Orchestration Connectors: Connectors determine the available paths that an orchestration can take at run time. On the canvas in Flow Builder, a connector looks like a line that connects one element to another.
Flow Orchestration Elements: Each element represents an action that the orchestration can execute. Orchestrations can contain Decision and Stage elements.
Decision Flow Orchestration Resource: Evaluate a set of conditions, and then route users through the orchestration based on the outcomes of those conditions. This element performs the equivalent of an if-then statement.
Flow Orchestration Operators: In conditions and filters, operators let you evaluate information and narrow the scope of an orchestration operation.
Flow Orchestration Version Properties: An orchestration version’s properties consist of its label and description. These values drive the field values that appear on the orchestration’s detail page.
Flow Orchestration Resources: Each resource represents a value that you can reference throughout the orchestration.
Global Variables Flow Orchestration Resource: Use system-provided variables that reference information about the Salesforce org or running user, such as the user’s ID or the API session ID.
$Flow Global Variables Flow Orchestration Resource: A $Flow global variable provides information about the running orchestration. Some variables contain system-provided values. You can update the other variables throughout the orchestration by storing output values in the variables.
Troubleshoot Orchestrations: To troubleshoot a failed orchestration run, use the orchestration fault email. To test an orchestration and observe what happens as it runs, use the debug option.
Debug an Orchestration: Debug an orchestration in Flow Builder to better understand the path an orchestration takes in different scenarios and the values that variables have at points within the automation. Use rollback mode to debug without making changes to your data. Or debug while making changes to your data.
Debug an Orchestration and Keep Data Changes: Test and troubleshoot your orchestration with database updates. Set a start point to skip earlier stages, an end point to stop before later stages, or both to isolate a middle segment. You can also set mock outputs for steps. A step that uses mock output doesn't run its referenced flow or make changes to the Salesforce database. You’re the assigned user for all interactive steps that meet their entry conditions.
Debug an Orchestration Without Changing Your Data: Debug your orchestration in Flow Builder to ensure that it runs as expected or to determine the cause of unexpected errors. Use rollback mode to debug your orchestration without making changes to your Salesforce data.
View Failed Orchestration Run Details from Email: When an orchestration run fails, Salesforce sends an error email. The email is sent to either the admin who last modified the associated orchestration or the Apex exception email recipients.
View Details for Orchestration Runs: Troubleshoot orchestration issues and monitor progress by reviewing run details. View details from the Orchestration Runs list view or from email notifications for failed runs.
View Details for a Failed Orchestration Run: Troubleshoot a failed orchestration, and gain insights about why it failed. You can view failed orchestration run details within 14 days of it failing.
View Details of an In-Progress Orchestration Run: View details for an in-progress orchestration run to better understand the path an orchestration takes with different scenarios and the variable values at points within in the automation.
Compare Flows and Orchestrations: Compare Flows and Orchestrations to choose the right automation tool for your business processes. Understand key differences in capabilities, use cases, and implementation approaches.
Org-Level Settings: Configure Org-Level settings for data masking outside of Objects and Fields.
Manage Additional Sharing Settings: Besides configuring the organization-wide defaults and sharing rules, you can configure these settings on the Sharing Settings Setup page.
Object Relationships Overview: Create relationships to link objects with each other, so that when your users view records, they can also see related data. For example, link a custom object called Bugs to cases to track product defects that are associated with customer cases.
Own from Salesforce: Own from Salesforce offers a suite of products that protect against data loss and corruption while helping you build scalable, efficient, and secure solutions. Manage security controls from a single view and monitor your data security posture. You can also address privacy requirements in production and development environments without slowing down the pace of work. Own from Salesforce also offers targeted data backup and recovery solutions for Salesforce, Microsoft, Workday, and ServiceNow.
Create a Page-Based Quick Action (Beta): Page-based quick actions are object-specific and use a "Quick Action Page" type of Lightning page to define their layout. You configure the fields, sections, visibility rules, and layout that users see when they trigger the action in the Lightning App Builder.
Visualforce: Visualforce is a framework that allows developers to build sophisticated, custom user interfaces that can be hosted natively on the Lightning Platform. The Visualforce framework includes a tag-based markup language, similar to HTML, and a set of server-side “standard controllers” that make basic database operations, such as queries and saves, simple to perform.
Browser Security Settings and Visualforce: Some Visualforce pages are run from *.force.com servers. If you set your browser’s trusted sites to include *.salesforce.com, you must also add *.force.com to the list.
Create Visualforce Pages: You can create Visualforce pages either by using Visualforce development mode, or by creating pages in Setup.
Visualforce Components: Visualforce components are small, reusable pieces of functionality—think widgets, panels, user interface elements, that kind of thing—that you use in Visualforce page markup. You can use standard Visualforce components, and create your own custom components.
Defining Visualforce Custom Components: Visualforce components are small, reusable pieces of functionality—think widgets, panels, user interface elements, that kind of thing—that you use in Visualforce page markup. You can use standard Visualforce components, and create your own custom components.
Enable Development Mode: Although you can view and edit Visualforce page definitions on the Visualforce Pages page in Setup, enabling Visualforce development mode is the best way to build Visualforce pages.
View and Edit Visualforce Pages: View and edit Visualforce page details, including when it was created, when it was last modified, and the Visualforce markup associated with the page.
How Do Visualforce Pages Compare to S-Controls?: Visualforce pages are considered the next-generation of s-controls and should be used instead of s-controls whenever possible, both for their increased performance and the ease with which they can be written.
Manage Visualforce Pages: After creating Visualforce pages, you can customize, edit, and delete them.
Merge Fields for Visualforce Pages: A merge field is a field you can put in an email template, mail merge template, custom link, or formula to incorporate values from a record.
Visualforce Page Security: You can specify which users can execute a particular Visualforce page based on their profile or an associated permission set.
Visualforce Pages: Visualforce pages are the top level container for custom apps built with Visualforce. Create Visualforce pages by adding Visualforce components (standard or custom), static HTML markup, and CSS styles and JavaScript to the page.
Static Resources: Static resources allow you to upload content that you can reference in a Visualforce page, including archives (such as .zip and .jar files), images, style sheets, JavaScript, and other files. Static resources can be used only within your Salesforce org, so you can’t host content here for other apps or websites.
Define Static Resources: You can use static resources to upload content that you can reference in a Visualforce page, including archives (such as .zip and .jar files), images, style sheets, JavaScript, and other files. You can use static resources only within your org, so you can’t host content here for other apps or websites.
Manage Static Resources: After creating static resources, you can customize, edit, and delete them.
Create Visualforce Tabs: Build Visualforce tabs so that users can access Visualforce pages from within Salesforce.
Uncaught Exceptions in Visualforce: Visualforce displays extra information when a page encounters errors during execution. This information can help you resolve problems with the page’s code, or at least track down an owner to look further into the problem.
The Editor for Visualforce or Apex: When editing Visualforce or Apex, either in the Visualforce development mode footer or from Setup, an editor is available.
Manage Version Settings for Visualforce Pages and Custom Components: Visualforce pages and custom components have version settings for the API and Visualforce. Managed packages referenced by the page or component also have their own version settings. Package versions can be used to evolve components without breaking existing customer integrations using the package.
Install the User Access and Permissions Assistant: To use the User Access and Permissions Assistant, enable the Tooling API. Then download the app from AppExchange, and assign the packaged permission set that comes with the app.
Manage Object Access in Object Manager: See the permission sets, permission set groups, and profiles that grant access to an object, and the level of access granted. You can also update the object permissions enabled in custom permission sets and profiles.
Permission Set Groups: A permission set group streamlines permissions assignment and management. Use a permission set group to bundle permission sets together based on user job personas or roles. Permission set groups make managing access easier when you're maintaining multiple personas with overlapping permissions.
Permission Set Groups and Combined Permissions View: The Combined permissions section provides a centralized view of all the permissions included in permission sets that make up your permission set group.
Create a Permission Set Group: Before you create a permission set group, assess your existing permission sets and users. Evaluate the types of job functions that your target group of users have, and group the permission sets based on their job functions.
Mute a Permission in a Permission Set Group: You can mute one or more permissions in a permission set group. If you mute a permission in a permission set group, only the permission set group is affected. The permission sets themselves aren’t affected.
Create Session-Based Permission Set Groups: To allow users functional access to permission sets only during specified sessions, create a session-based permission set group. For example, grant access to an application only during an authenticated session. Then activate the session-based permission set group in a flow or via the API.
Add Permission Sets to Permission Set Groups: After you’ve created a permission set group, you can add permission sets to the group based on the needs of a particular user job role or persona.
Permission Set Groups from Managed Packages: Partners can organize permissions into permission set groups to include in managed packages. Understand how to work with permission set groups installed from managed packages.
Muting Permission Sets: Use a muting permission set to mute, or disable, selected permissions in a permission set group. If you don’t want to assign users all of the permissions in a permission set included in a permission set group, you can use a muting permission set.
Permission Set Group Muting Dependencies: When you mute a permission in a permission set group, the muted permission impacts permissions that depend on it within the group. Understand how muting dependencies work and the effects of muting permissions on your users.
Session-Based Permission Set Groups: A session-based permission set group applies to a specific user session and grants users functional access to the permission sets included in the permission set group.
Permission Set Group Status and Recalculation: A permission set group calculates the combined permissions from the included permission sets. The permission set group status indicates whether the calculation and resulting permissions in the group are up-to-date and available for the assigned users.
App and System Settings in Permission Sets: In permission sets, permissions and settings are organized into app and system categories. These categories reflect the rights users need to administer and use system and app resources.
Enable User Permissions in Permission Sets: User permissions specify what tasks users can perform and what features users can access. In permission sets, you enable user permissions in the App Permissions and System Permissions sections.
Report on Custom Permission Set and Permission Set Group Assignments: To help you manage users, report on your users’ assigned custom permission set and permission set groups. Create a custom report type before building reports on custom permission set or permission set group assignments.
Create Permission Sets: Create permission sets that contain the permissions necessary for your users to complete a specific job or task.
Enable Custom Permissions in Permission Sets: Custom permissions give you a way to provide access to custom processes or apps. After you’ve created a custom permission and associated it with a process or app, you can enable the permission in permission sets.
Integration Permission Sets: Integration permission sets define the scope of data access by Salesforce integration-related features and services.
Manage Permission Set Assignments: You can assign permission sets to a single user from the user detail page or assign multiple users to a permission set from any permission set page.
Enable Object Permissions in Permission Sets: Object permissions determine the base-level access users have to create, read, edit, and delete records for each object. Permissions sets are the recommended feature for managing object permissions.
Permission Sets: A permission set is a collection of settings and permissions that give users access to various tools and functions. Permission sets extend users’ functional access without changing their profiles and are the recommended way to manage your users’ permissions.
Standard Permission Sets: A standard permission set consists of a group of common permissions for a particular feature associated with a permission set license. Using a standard permission set saves you time and facilitates administration because you don’t need to create the custom permission set.
Manage Permissions in the Permission Set and Permission Set Group Access Summaries: To help you manage your users’ permissions, you can see and update all object, user, field, and custom permissions that are enabled for a permission set or permission set group in its summary page. You can also manage which permission set groups the permission set is included in and vice versa.
Types of Permission Sets: Salesforce offers several types of permission sets to help your users achieve their business goals.
Work with Permission Set Lists: Create list views to help view and manage your permission sets. You can also edit permissions in multiple permission sets at the same time using list views.
User Access and Permissions Assistant: Streamline your access and permissions management with the User Access and Permissions Assistant app from AppExchange. Convert profiles to editable permission sets. Analyze and report on permissions and access in your org. Manage your permission set groups and the permissions that they contain.
Analyze Object Permissions: Find the permission types that are assigned to your selected object using the User Access and Permissions Assistant app.
Analyze Your Permission Assignments: Review your org’s permission assignments using the to quickly determine the permissions that a user has and the configuration that grants a specific permission.
Analyze Permission Set Groups: Find details about permission set groups using the User Access and Permissions Assistant app.
Analyze User Permissions: Find the permissions assigned to the selected user using the User Access and Permissions Assistant app.
Converting Profiles to Permission Sets: If your custom or standard profiles have a Salesforce license, you can use the User Access and Permissions Assistant app to convert them into a permission set that you can edit and assign.
Create a Permission Set to Use the Named Credential: Create a custom permission set to enable users to use the Tooling API for the User Access and Permissions Assistant. You can assign this permission set to any users who use the app.
Manage Permission Set Groups: Use the User Access and Permissions Assistant app to create, modify, or remove permission set groups. You can also assign or unassign permission set groups and add or remove permission sets to groups.
User Access Policies: With user access policies, you define aggregated access for your users in a single operation. Automate your users’ assignments to permission set licenses, permission sets, permission set groups, package licenses, queues, and public groups. You can create policies that grant or remove access whenever users are created or updated, or in a one-time manual migration.
Permissions and Access Settings: User, object, and field permissions and access settings can be specified in profiles and permission sets. To use them effectively, understand the differences between profiles and permission sets.
Set Assignment Expiration Details for Users in Permission Sets and Permission Set Groups: Use the assignment expiration option to determine the effective time period that users receive certain permissions. You can set assignment expiration dates via permission sets and permission set groups. Assigned users receive access to all aggregate permissions until the expiration date.
How Is Record Type Access Specified?: Assign record types to users in their profiles or permission sets (or permission set groups), or a combination of these. Record type assignment behaves differently in profiles and permission sets.
Revoke Permissions and Access: You can use profiles, permission sets, and permission set groups to grant access but not to deny access. Permissions granted from profiles, permission sets, and permission set groups are honored. For example, if Transfer Record isn't enabled in a profile but is enabled in a permission set, the assigned user can transfer records regardless of whether the user owns them. To revoke a permission, you must remove all instances of the permission from the user.
Tab Settings: Tab settings specify whether a tab is visible in its associated app. They also determine whether a tab appears in the All Tabs page in Salesforce Classic and whether objects appear in the Lightning Experience App Launcher and navigation menus. Tab settings labels in permission sets differ from the labels in profiles.
Picklist Limitations: The maximum number of characters that you can have in a picklist depends on the type of picklist. Each picklist value includes a line break and a return character that aren’t visible but that count in the character limit.
Plan and Prepare for Deployment: A successful deployment starts with a solid plan. To avoid conflicts or missing dependent metadata and configuration data during deployments, review these prerequisites, best practices, and limitations.
Salesforce Connect: Salesforce Connect provides seamless integration of data across system boundaries by letting your users view, search, and modify data that’s stored outside your Salesforce org. For example, perhaps you have data that’s stored on premises in an enterprise resource planning (ERP) system. Instead of copying the data into your org, you can use external objects to access the data in real time via web service callouts.
Choose Which Salesforce Connect Adapter to Use: Salesforce Connect uses a protocol-specific adapter to connect to an external system and access its data. When you define an external data source in your organization, you specify the adapter in the Type field.
Salesforce Connect Support for Quick Actions: External objects support quick actions, except when the actions involve features or functionality that are incompatible with external objects.
Salesforce Connect Support for Record Feeds: View the Chatter feed associated with external object records you follow to see updates about the record. Following records helps keep you up to date on important changes to the external objects.
External Objects in Salesforce Connect: External objects behave similar to custom objects except that they map to data stored outside Salesforce in an external data source. Each external object maps to a data table, and the object fields map to accessible table columns.
Salesforce Connect Support for the Salesforce Console: You can access external objects from the Salesforce console only in Salesforce Classic. Other consoles, such as the Salesforce console in Lightning Experience, aren’t supported.
Salesforce Connect Support for Reports: Depending on network latency and the availability of the external system, reports that include an external object can take a long time to run.
Sync an External Data Source for Salesforce Connect: When you validate and sync an external data source, it creates or overwrites Salesforce external objects that map to the external system’s schema. Syncing doesn’t copy any data into your Salesforce org or write data from your org to the external system.
Writable External Objects in Salesforce Connect: Select Writable External Objects when you define an external data source and use Salesforce Connect external objects to create, update, and delete data. External objects are read only by default.
Named Credential as Callouts for Salesforce Connect OData 2.0 or 4.0 Adapters: When you define an external data source for the Salesforce Connect OData 2.0 or 4.0 adapters, you can enter a named credential URL as the URL for reaching the OData producer. This example shows how Salesforce Connect OData 2.0 or 4.0 adapters can make callouts using the authentication settings defined in a named credential.
More Features Supported by Salesforce Connect: External objects are available to Salesforce APIs, SOQL queries, SOSL and Salesforce searches, packages, Metadata API, change sets, and Lightning Experience app.
Identity Type for External Data Sources: On the external data source configured for Salesforce Connect, the Identity Type field specifies whether your organization uses one set or multiple sets of credentials to access the external system. Each set of credentials corresponds to a login account on the external system.
Salesforce Connect Learning Map: Follow along the Salesforce Connect learning map to explore all the relevant trails, docs, and reference resources you need to integrate external data sources into your apps!
External Data Sources With Salesforce Connect: Salesforce Connect uses external data sources to access data that's stored outside your Salesforce org. You must configure an external data source and synchronize it to map its tables with external objects in Salesforce.
Define and Manage Platform Events: Use platform events to connect business processes in Salesforce and external sources through the exchange of real-time event data. Platform events are secure and scalable. Define fields to customize your platform event data.
Accessing Own through the Own API: Own provides API access through all pricing plans with the purpose of letting you manipulate and export some of your jobs and data.
Add a User: Users with Admin roles can add users and manage users and their roles in the Account Settings Users tab.
Audit Log: The audit log provides admins with a detailed record of recent events for all users.
Own Regions and IP Addresses for Allowlisting: When you limit network traffic to Salesforce, add these IP addresses to the list of Login IP Ranges. This will let Own connect to your environment.
Manage Business Units: Business Units provide a way to manage specific access permissions to environments. This means that users can belong to multiple business units, optionally with different roles in each. Think of business units as different departments to group the users by. For example, a user can be a Read-Only user in one Business Unit but have a Developer role in another business unit.
Business Unit FAQs: Find answers to frequently asked questions about Business Units, including issues related to user roles, service visibility, and plan limitations.
Using Bring Your Own Storage: Bring Your Own Storage (BYOS) is ideal for customers who want to own their backup data, in line with company security regulations and AWS storage commitments.
Configure IP Address Restrictions: Master Admins can configure what IP addresses are allowed to access the Own Data Platform. Changes to Permitted IP settings affect all the regions in the account.
Configure the AWS Bucket: When on-boarding, the Adding the services button is disabled, until a valid bucket is configured.
Configure Azure IdP for FedRAMP Single Sign-on: Instead of relying on local authentication for passwords and security policies, users may set their own authentication using a managed Identity Provider. Azure single sign-on is supported using SAML 2.0 authentication.
Configure Identity Providers (IdP) for SSO in Own Government Cloud: Customers can configure their own authentication using managed identity providers. The Own Government Cloud platform supports Azure IdP, Okta IdP, and Salesforce IdP. We recommend that Master Administrators follow the configuration instructions for their provider.
Configure IP Address Restrictions for FedRAMP: We recommend establishing trusted IP addresses or ranges to help ensure that only trusted sources are allowed to access the Own Government Cloud platform.
Enable Single Sign-on for FedRAMP: Within the Own Government Cloud platform, single sign-on (SSO) is the only authentication method available for user login. Own from Salesforce supports single sign-on using SAML 2.0. Instead of relying on local authentication for password and security policies, you can set your own authentication using your managed identity provider (IdP).
Getting Started with FedRAMP: Before getting started, it is important to understand what is available in FedRAMP due to regulation limitations. FedRAMP limitations apply to all available Own applications.
Guidance for Administrators on the Own Government Cloud Platform: Understand the types of privileged administrator roles that are available in the Own Government Cloud platform. Use best practices to assign appropriate admin roles to users. Learn how to disable, delete, or swap administrator accounts when necessary.
Migrating FedRAMP to the Own Data Platform: Own has launched a Data Platform to empower users to own their data. Accounts using single sign-on to access the current Own application must reconfigure their identity providers to access the Own Data Platform. Migrated users immediately benefit from the improved security experience provided by the platform.
Configure Okta IdP for FedRAMP Single Sign-on: Users can set their own authentication using a managed Identity Provider instead of relying on local authentication for passwords and security policies. Okta single sign-on is supported using SAML 2.0 authentication.
Platform Settings for FedRAMP: Set a session timeout to log out users after an interval of inactivity. Establish IP address restrictions to help ensure that only trusted sources can access the platform. See what URLs to allowlist so that the Own Government Platform can securely communicate with the Salesforce environment.
Own Regions and Allowlisting for FedRAMP: Allowlisting IP addresses and URLs is a critical configuration step. It helps ensure that the Own Government Cloud platform can securely communicate with the Salesforce org to perform automated backups, data seeding, and archiving.
Secure Configuration Guide for Own Government Cloud: This guide helps public sector customers meet the new Secure Configuration Guide (SCG) requirements introduced by the Federal Risk and Authorization Management Program (FedRAMP). By securely configuring their instance of the Own Government Cloud platform, public sector customers can help make sure they're protected against evolving threats.
Recommended Security Settings for FedRAMP: This guidance outlines recommended security settings that can be set by the top-level Master Administrator and other privileged users. These settings help ensure that customers configure their Own organization securely and in compliance with customer-defined or industry-specific requirements.
Set the Session Timeout for FedRAMP: The session timeout setting sets the interval of inactivity before a user is automatically signed out of the Own Data Platform.
GDPR and SaaS FAQs: Find answers to questions concerning OWN from Salesforce related to GDPR and SaaS.
Handling Data Privacy: Data Privacy is handled by masking the data. Own doesn’t change or delete records from backups. When you request records from a backup, either directly in the application or via API, the records are masked.
Salesforce Integration User License (API Only): The Authenticated User connects the application to the client's Salesforce org. Own doesn't currently support this type of license because the standard API configurations for the Salesforce API Integration User license have insufficient privileges to support usage as the Authenticated User for Own applications: Backup & Recover, Archive, and Seeding.
Upload an Asymmetric Key for Azure Blob Storage: Own is migrating to Azure Blob storage, a highly scalable and reliable object storage service. This requires customers with Bring Your Own Key (BYOK) to generate an asymmetric encryption key, as the existing Azure Disk storage uses symmetric keys.
Manage API Tokens: Use API Tokens, based on OAuth 2.0 authentication protocol, as a means to access Own from Salesforce APIs. Treat API tokens as securely as any other type of password. Make sure to store this token in a safe and secure location.
Set Up Multi-Factor Authentication (MFA): MFA works by adding an additional layer of security to your online account. It requires an additional sign-in credential or authentication step, beyond just your username and password to gain access. MFA allows you to protect access to your account using an app, including Okta Verify, or a FIDO2 Authenticator (for example, Google Authenticator, Salesforce Authenticator, Microsoft Authenticator).
Managing Multi-Region Accounts in Own from Salesforce: Provision and link multi-region Own accounts by using the same Master Admin email in each region. Invite users to linked regions with the same email for one credential set, and follow recovery guidance for separate account errors.
Roles & Permissions: The available permissions depend on the user's role. With the exceptions of Master Admin, Security Admin, and Account Level Audit-Log-Viewers, permissions are limited within the users' Business Units.
Using the System for Cross-Domain Identity (SCIM) with Own Data Platform: SCIM (System for Cross-domain Identity Management) is an open standard designed to automate and simplify user identity management across systems. A standardized schema ensures smooth operations between different Identity Providers (IdPs) and Own app.
Securing Your API Token: An API token is a refresh token that is used to generate an authentication token in order to sign in to the Own Data Platform via API, in order to perform various operations within the Own account.
Setting the Session Timeout: The session timeout setting sets the interval of inactivity before a user is automatically signed out of the Own Data Platform.
Configure Password Settings: Master Admins can configure and update password settings including the password expiration policy and password reuse policy. Admin users can see the configured settings while the settings aren't visible to nonadmin users.
Platform Settings: The platform settings for the Own Data Platform and related services can be managed through various features and tabs.
Sign Up and Sign In to Own from Salesforce Platform: Sign up for an Own from Salesforce Platform account. Sign in using Single Sign-On (SSO) or a password. Manage account security by resetting or changing your password and unlocking your account if it's blocked.
Enable Single Sign-On: Own from Salesforce supports single sign on using SAML 2.0. Instead of relying on local authentication for password and security policies, you can set your own authentication using your managed Identity Provider.
Create an Application for SSO in Azure: To use Azure as your identity provider while using single sign-on, configure the correct settings for your app integration.
Create an App Integration for SSO in Okta: To use Okta as your identity provider while using single-sign on, configure the correct settings for your app integration.
Create an SSO Application in Ping: To use Ping as your identity provider while using single sign-on, configure the correct settings for your app integration.
Single Sign On (SSO): The Own Data Platform supports Single Sign-On using SAML 2.0. You can set your own authentication using your managed Identity Provider instead of using local authentication for password and security policies.
Disable Single Sign-On (SSO): Disabling Single Sign-On (SSO) requires a shift to password authentication. Upon disabling SSO, you must configure password expiration settings, the number of previous passwords to deny, and whether to enable MFA.
Enable Asserted Encryption with SSO: In order to meet FAL2 requirements, your IdP may need to sign assertions it generates. Find the variables you need to enter in your IdP to enable encrypted assertion.
Migrate SSO Users to Own Data Platform: Own is launching a new Data Platform. If you access our applications with Single Sign On through your chosen Identity Provider, make sure your organization has made the necessary updates to continue benefiting from our improved platform security. For SSO users migrating to the Own Data Platform, it's important to configure your Identity Provider (IdP) by December 15th to verify access. After this date, access to the regional login URL will no longer be available.
Update SSO Credentials: When you update your identity provider issuer and/or certificate, the new credentials won’t be active until a user logs in with IdP.
Swap Master Admin Accounts: Sometimes the current Master Admin transfers the Master Admin role to another Administrator on the system.
User Roles: Roles are assigned to users per business unit to provide them permission to perform specific actions. Users can be assigned to one or more specific business units with a different role in each business unit.
User Roles FAQs: Find answers to frequently asked questions about visibility and access permissions related to user roles.
Users Management: Use Users Management feature to add and manage users, enable or disable Multi-Factor Authentication (MFA), and manage user roles and permissions. The Master Admin has specific capabilities, such as enabling, disabling, and resetting MFA for users.
Set Predefined Field Values for Quick Action Fields: When you create actions, use predefined field values to set a value for a field. Predefined values can help ensure consistency and make it faster and easier for users to create records.
View Records with Custom Tabs: To view the external objects that you synced with your Privacy Center retention store, you can create custom object tabs.
View Records with Related Lists: Use related lists to view the external objects that you synced with your Privacy Center retention store.
View Files and Attachments: View files and attachments in your Privacy Center retention store by adding a component to the associated record page.
Add Actions to Your Process: After you define a criteria node, define the actions that are executed when the criteria are met. Actions are executed in the order in which they appear in the Process Builder.
Send a Custom Notification from a Process: Send customized notifications when important events occur. Alert an account owner if a new support case is logged while trying to close a deal, or send a notification for a workflow built entirely with custom objects. Add recipients and content to your custom notification, then add it to your process.
Send an Email from a Process: Easily send an email from a process by using an email alert. Email alerts are configured outside of the Process Builder and contain the standard text, list of recipients, and template for an email.
Launch a Flow from a Process: Start an autolaunched flow from your process to automate complex business processes. Create flows to perform logic and have events trigger the flows via processes without writing code.
Invoke a Process from Another Process: Invoke a process from another process. With invocable processes, you have the option of reuse so that you don’t spend your time on repetitive work.
Use a Quick Action from a Process: Create a record, update a record, or log a call by using a quick action that you or another admin created for your organization.
Work with Quip from a Process: Create documents, chat rooms, and folders when important events occur. Attach a document to a record so your users have information in context. Update your spreadsheets with the latest Salesforce data. Send a message to a chat room or document. Add new slides to a deck, copy documents, add members to a document or chat, and more.
Copy a Document from a Process: To use a document as a template, create a copy. By default, copied documents are saved to the running user’s Private folder in Quip.
Export a Document to a PDF from a Process: To mark a document as complete or to keep a document view-only for record keeping, export it to a PDF. You can choose to attach the PDF to a document or to a Salesforce record.
Add a Live App to a Template from a Process: Keep your templates up to date with the latest Salesforce data. Add live Salesforce records and list views to your templates using Process Builder.
Copy Content with Live Paste from a Process: Copy content from a source document and paste it with Live Paste in a new document. After you update the source content, set the content to automatically update in all documents that reference it.
Send a Message from a Process: Send a message in a chat room or in a document. Messages sent in a document appear as inline comments or in the document body.
Specify When Your Actions Execute with a Schedule: In record-change processes and event processes, you can schedule actions to execute at a specific time. An action group that supports scheduled actions can have multiple schedules. For example, you can schedule some actions to execute one day from now and others to execute three days from now.
Update Records from a Process: Update one or more records that are related to the record that started the process by manually entering values or by using the values from related records.
Activate a Process: Salesforce doesn't start using a new or revised process to evaluate records until you activate it.
Nest Processes in the Process Builder: Invocable processes let you modularize sections of your processes and add more logic to them. An invocable process is a process that starts when another process invokes it. The process starts when in the process’s properties controls whether a process is invocable.
Avoid Unwanted Actions in Processes: When you add criteria to your process, you can choose to execute actions when specified criteria change.
Clone a Process: If you want to change an existing process, save a clone of that process. You can save the clone as either a new inactive process with its own version history, or as a new inactive version of the existing process.
Process Limits and Considerations: Before you start creating, managing, and activating processes, understand the limits and considerations.
Compatibility Considerations for Processes: Before you design a process, understand how processes interact with other Salesforce features, like custom objects and fields.
Considerations for Event Processes: These considerations are specific to processes that start when a platform event message is received.
Considerations for Processes That Update Records: Understand what happens when you change a record owner, update the same field multiple times, or update currency fields in a multiple currency org.
Considerations for Processes in Transactions: Each process runs in the context of a transaction. A transaction represents a set of operations that are executed as a single unit. When a process is triggered more than one time in a single transaction, Salesforce executes similar actions in one batch.
When Do Processes Evaluate Record Changes?: Processes start automatically and are invisible to the user. Before you design or activate a process, understand which changes trigger processes.
Create a Process: To create a process, define its properties and which records it evaluates, and then add criteria nodes and actions.
Add Process Criteria: Define the criteria that must be true before the process can execute the associated actions.
Process Formula Limitations: Formulas that are used as conditions in a criteria node have some limitations. If a process contains an invalid formula, you can't save or activate the process.
Delete a Process Version: If you no longer require a process version that you’ve defined, delete it.
Delete Unexecuted Scheduled Actions: If you no longer want to execute a process's scheduled actions, you can delete them from the list of paused flow interviews in Setup.
Printer Management Process Example: The example demonstrates how you can use Process Builder to subscribe to and evaluate a platform event.
Managing Documents Process Example: This example uses Process Builder to manage documents in Salesforce. The example moves a document to a shared folder in Quip whenever the record that the document is associated with is created or updated. This process ensures that the documents associated with a Salesforce record object are always available to users who have access to the shared folder.
Examples of Processes: See how Process Builder can make automating your business processes super easy.
Process Limits: When building processes, keep shared limits and Apex governor limits in mind. In addition, a process’s API name must be unique across all processes and flows in your Salesforce org.
Considerations for Scheduling Process Actions: Scheduled actions are supported only in record-change processes and event processes. The scheduled time depends on the type of schedule, whether the field changed, and whether the process was deactivated.
Process Schedule Limitations: Before you add a schedule to a process, understand the limits and what isn’t supported.
How Does Salesforce Process Scheduled Actions?: Understand the expected behavior for processing scheduled actions based on which type of schedule they’re associated with, whether the field changed, and whether the process was deactivated.
Transactions and Scheduled Actions: Immediate actions in processes are executed in the same transaction as the operation that triggered the process, such as when a user creates or edits a record. Scheduled actions are included in a separate transaction.
Process Management: Process Builder allows you to see and manage all your processes in one place.
Execute Actions for Multiple Criteria: Choose whether to stop or continue your process after specific criteria are met and associated actions execute.
Process Builder: Many of the tasks you assign, the emails you send, and other record updates are vital parts of your standard processes. Instead of doing this repetitive work manually, you can configure flows or processes to do it automatically. We strongly recommend using Flow Builder, but Process Builder can also help you automate your business processes and give you a graphical representation as you build it.
Configure the Process Trigger: Every process includes a trigger, which tells the process when to start. How you configure that trigger depends on what type of process you’re creating.
Process Status: Each process has a status that determines whether the process can be edited, activated, or deleted.
Troubleshoot Processes: Use the error messages that appear in the Process Builder and the emails you receive when a process fails to help solve problems that arise when you’re working with processes. When all else fails, look at the Apex debug logs for your processes.
Troubleshoot Processes with Apex Debug Logs: Use debug logs to find detailed information about your running processes after they finish running. For example, investigate why a process doesn’t to trigger when a record meets the process’s criteria, or explore the sequence of processes being executed.
Errors in the Process Builder: The API names for criteria nodes and actions are created in the background. When you create or update processes, you can see error messages that reference those names to help you identify specifically where the problem occurred.
Send Alerts When a Screen Flow Fails: To save time troubleshooting screen flows that fail, subscribe to the Flow Execution Error Event platform event. When a flow interview fails, Salesforce publishes a platform event message. In Process Builder, you can subscribe to the platform event and perform actions, such as posting to Chatter or sending custom notifications.
What Happens When a Process Fails?: When a user does something that triggers a process, such as create a record, and the process fails, the user gets an error message. The error message includes the process name, error ID, and sometimes technical information that the user can give to you, the Salesforce admin. You can use the error ID to locate the detailed error email that is sent when the process failed.
Process Usage-Based Entitlements: Like feature licenses, usage-based entitlements don’t limit what you can do in Salesforce; they add to your functionality. If your usage exceeds the allowance, Salesforce contacts you to discuss additions to your contract. In the meantime, your processes continue to run as usual.
Setting Values in the Process Builder: Throughout the Process Builder, you must set values, for example, to set conditions in a criteria node, to set the fields on a new case in a Create a Record action, or to specify an Apex method to reference.
Field Picker: Use the field picker to reference fields on the record that started the process or fields on related records.
Process Builder Value Types: When setting a value for a given field—whether on the record that started the process or a related record— the available value types are filtered based on the field that you’ve selected.
View the Public Group Access Summary: With the Public Group Access Summary, see the sharing rules, report and dashboard folders, and list views where this public group is used to grant access. You can also see the other public groups that it’s added to. The public group can be referenced in other features not listed in this summary.
Quick Pages (Beta): Use natural language to create and share tailored pages in Salesforce that gather all the information you need in one view. Chat with the agent to create and refine a Quick Page for any business need, such as for a presentation, meeting prep, or work prioritization. Share a page with specific users or public groups within your org, or with the entire org. Quick Pages are grounded in your Salesforce data and follow your org’s security model, so viewers of shared pages see only the data that they have access to.
Create and Share Quick Pages (Beta): Use natural language to create and refine a page. Share the page with the people or groups who need it, or with your entire org. Edit the page to update its appearance or the information that it conveys.
Set Up Quick Pages (Beta): Configure your org to enable Quick Pages, and assign permissions to grant access to standard users to create, edit, and share pages, or only to view pages.
Use Record Types: Here’s an example of how record types can work in your org. Let’s say you have two sales divisions, Hardware and Consulting, and only your Consulting division receives leads through seminars. You can choose to display the Seminar contact lead source for the Consulting division only.
Tips for Referencing Record Types in Formulas: Get tips for applying different workflow rules, validation rules, or lookup filters to different record types. Learn when to use record type names or IDs in formulas to apply logic based on a record’s classification. Plus, find guidance on limiting the use of the record type global variable to default value formulas, and deployment considerations for sandbox and production environments.
Create a Many-to-Many Object Relationship: You can use master-detail relationships to model many-to-many relationships between any two objects. A many-to-many relationship allows each record of one object to be linked to multiple records from another object and vice versa. For example, you create a custom object called Bug that relates to the standard case object such that a bug could be related to multiple cases and a case could also be related to multiple bugs. When modeling a many-to-many relationship, you use a junction object to connect the two objects you want to relate to each other.
Remote Access Application: Connected apps have replaced remote access apps. Use connected apps for apps that require integration with Salesforce to verify users and control security policies for external apps.
Proof-of-Possession for Asset Tokens: If you construct an actor token holding the public key of your asset and sign it with your asset’s private key, Salesforce binds that public key into your asset token. This pattern allows for what’s known as Proof-of-Possession or Holder of Key. The asset can prove that it holds the private key corresponding to the public key that Salesforce binds into the cnf claim during issuance. Proof-of-Possession helps provide greater assurance that the token is being presented by the actual asset it was issued to.
Using and Validating Asset Tokens: After Salesforce issues an asset token, the device presents its data or event to your backend service along with the asset token. Your backend service validates the asset token and determines whether the device is authorized for the requested operation. Common methods for securing communications between the device and your backend service are the bearer token sequence and the JWT bearer token exchange sequence. Use standard open-source libraries to validate asset token JWTs.
Secure Identity for the Internet of Things: Asset tokens are an open-standards-based JWT authentication token for verifying and securing requests from connected devices. They identify the device to a backend service that processes the stream of data and events from the device. They allow registration of device data with the Salesforce platform and linking it to Salesforce CRM data about the customer, account, or contact, helping you to act on behalf of the customer. You can even support custom business processes using asset token events. Asset tokens enable more proactive support and more predictive engagement with your customers, on an unprecedented scale.
Application Access Request: The external app you are using is requesting access to your Salesforce data. The external app has already been integrated into Salesforce by your admin.
Application Access Request Approved: The external app that you are using has requested access to your Salesforce data, and you approved this request. Close the browser window and go back to the app you were using.
Application Access Request Denied: The external application you are using has requested access to your Salesforce data and you denied this access. You should log out of Salesforce. You can go back to the originating application.
Replacement Tools for Workbench: Workbench (https://workbench.developerforce.com) is an open-source tool for interacting with your org. However, because Salesforce doesn’t maintain Workbench, we can’t address issues or bugs related to using it. We recommend that you use our alternative and integrated tools instead, such as Code Builder, Salesforce CLI, and VS Code Extensions.
Define Org-Level Help in Salesforce Classic: If you rename standard tabs, objects, fields, and other related user interface labels, you can also replace the built-in Salesforce Help with documentation that’s customized specifically for your users. To replace the built-in help, simply provide a URL to your custom help. This feature is available for Salesforce Classic only.
Configure the Guest User Profile: Before publishing your Experience Cloud site with public access enabled, configure the guest user profile so that your customers can view and interact with your site without logging in.
Actions in the Organization Sync Record Queue: This feature is now retired. In previous releases, Organization Sync let you set up a secondary, synced Salesforce org. Users could access a subset of Salesforce data in that org when the primary org was unavailable.
Managing Organization Sync: This feature is now retired. In previous releases, Organization Sync let you set up a secondary, synced Salesforce org. Users could access a subset of Salesforce data in that org when the primary org was unavailable.
Organization Sync: This feature is now retired. In previous releases, Organization Sync let you set up a secondary, synced Salesforce org. Users could access a subset of Salesforce data in that org when the primary org was unavailable.
Access External Data With Salesforce Connect: Salesforce Connect lets your users view, search, and modify data that’s stored outside your Salesforce org. Instead of copying the data into standard or custom objects, use external objects to access the data in real time via web service callouts.
Workflow Rule with an Email Alert Migration to a Flow Example: The majority of workflow rules are used to send email alerts or perform same-record field updates. While these types of workflow rules have a reputation for being fast, triggered flows are even faster. It’s time to migrate your workflow rules to Flow Builder.
Data Classification in Secure: After you create Sensitivity Levels and Compliance Categories on the Settings tab, the fields within the org can be assigned a classification on the Data Classification tab.
Security Center Extension Configuration: The Security Center Extension Config tab contains configuration options for the Security Center Extension. Users with the appropriate permissions can manage settings and configurations so that the extension operates according to the organization's specific security requirements and preferences.
Create Security Insights Alerts: Manage your company's security proactively with Security Insights alerts. Customize alerts to focus on specific security insights, such as administrative permissions or data vulnerability.
Create a Read-Only User for Security Insights in Secure: Retain a secure Salesforce environment and reduce the risk of unwanted changes to security settings by designating users as read-only. Give stakeholders access to security insights and permission to download lens-related data, without the ability to run jobs, configure risk ratings, or update scoring policies.
Managing Security beyond Health Check with Secure: Salesforce Health Check provides a basic security overview, but lacks in-depth analysis. Adding Secure offers a more comprehensive assessment including data identification, risk prioritization, and detailed analysis. Using both provides robust data protection.
Include and Exclude Insights from Scoring: You can exclude entire insights or specific entries from an org’s risk-weighted scoring. Excluding an entire insight will omit that insight from being scored within the specific lens. Excluding an individual insight entry will omit the specific entry within the list from being scored. Consider, for example the Data Protection and Clasification lens, which includes an insight called profiles with access to high-risk fields. You can exclude risk profiles that aren't assigned to any user since these profiles don't contribute to the organization’s risk.
Security Center Extension Tabs: Feature tabs provide a framework for maintaining data integrity and confidentiality within Salesforce. Understand which fields are displayed on the Security Center Extension tabs.
Getting Started with Security Center Extension: Security Center Extension is a useful Salesforce admin tool. It assists admins in classifying data, looking at and improving their security, and managing permissions and alerts. The Security Center Extension has features to compare security settings with best practices, learn about changes to the settings, and schedule regular analysis. It also has detailed views and customizable alerts.
Install the Security Center Extension: The Security Center Extension is a managed package. Use the standard process for installing a managed package.
Security Insights Lenses in Secure: The Security Insight lenses display a collection of insights, each of which identifies potential risks in the configuration. Customize the UI of the lenses according to your needs. Your customizations are saved for future sessions.
Perform a Guided Risk Assessment: The Guided Risk Assessment focuses on capturing business context for an org, which can then be combined with specific high risk setting observations without requiring extensive data classification, risk rating, and risk scoring configuration.
Scheduling Automated Snapshots: You can schedule a Platform Encryption Analysis, Data Classification Snapshot, Security Insights Refresh, History Retention Policy Snapshot, and Fill Rates Analysis. These can be configured to run on a Daily, Weekly, or Monthly basis. When scheduling, it is recommended to schedule the Platform Encryption Analysis to run separately from the Security Insights job, with a two to three hour buffer between them.
Security Insights Lens Information and Scoring in Secure: The detailed insight lenses display a set of scores. The scores are based on risk rating for each security insights finding and help in prioritizing what comes first when it comes to remediation activities.
Security Insights Alerts: Security Insights offers alerts that can be created, configured, and subscribed to.
Data Classification Categories and Levels in Secure: Secure policies include two classifications, Sensitivity Levels and Compliance Categories. Sensitivity levels indicate whether the sensitivity level is high-risk. Compliance Categorization can also be specified to better identify sensitive data. You can use the default sensitivity levels and compliance categories, and add custom entries.
Subscribe to Security Insights Alerts: Receive progress reports that compare the results of the latest security analysis with previous ones. Improve planning and resource allocation for security measures by tracking improvements or regressions in security settings over time.
Time Machine: The Time Machine allows you to view results from previous analysis jobs within Security Insights and the Platform Encryption Analyzer, along with previous snapshots that were scheduled and captured in Data Classification and the History Retention Policy Manager.
Security Insights in Secure: Security Insights is an automated tool that generates a risk-prioritized list of security gaps, and helps you decide where risk mitigation efforts should be focused. For example, security analysts can identify and address risky configurations and deviations from best practices, and then recommend setting enhancements that align settings with security policies.
Compare Users, Profiles, Permission Sets, and Permission Set Groups: Some lenses in the Who Sees What Explorer tab include a Compare option. Use the Compare option to compare object, field, and permission access between users, profiles, permission sets, and permission set groups. The "Objects & Fields" lens provides quick comparisons of Read and Edit access. In the "System Permissions" lens, compare permission assignments.
Who Sees What Explorer Lenses in Secure: The Who Sees What Explorer in Secure provides five lenses—Objects, Records, Users, System Permissions, and Profiles & Permission Sets—to help administrators manage and understand user access to objects, records, and system permissions. Each lens offers detailed insights and specific functionalities to ensure precise access control and compliance monitoring.
Who Sees What Explorer Tab in Secure: The Who Sees What Explorer tab in Secure provides five lenses to help administrators understand and manage user access to objects, records, and system permissions within the Salesforce Org. Each lens offers a unique perspective and detailed insights, enabling precise access control and compliance monitoring.
Update the Batch Configuration Custom Metadata Type: Batch Configuration Custom Metadata Type is included with Secure to handle issues that rise with certain Managed Package features within larger Salesforce orgs. Enabling the Custom Metadata Type with unique configurations enable, for example, specific jobs to finish without timeout errors, or load pages faster in some apps.
Design Your Own Data Model With Schema Builder: Schema Builder provides a dynamic environment for viewing and modifying all the objects and relationships in your app. This greatly simplifies the task of designing, implementing, and modifying your data model, or schema. Schema Builder is enabled by default.
Create Objects with Schema Builder: Custom objects are objects that you create to store information that's specific to your company or industry. You can create them via Setup or in the Schema Builder.
Secure: Secure by Own from Salesforce is a managed package that helps you get more out of Salesforce security and access features. Gain insights into your data’s security posture and classify data for informed security policy management. Understand which users can access which data and navigate data retention and field history settings. Secure includes features now found in Security Center Extension and Shield Extension managed packages.
Connect Multiple Salesforce Orgs in Secure: Secure enables you to connect multiple Salesforce orgs for reporting purposes in the Connections section on the Settings tab.
Secure Installation and Removal FAQs: If you encounter issues while installing Secure, the answers to frequently asked questions can sometimes help you.
Secure Settings FAQs: If you encounter issues related to Secure Settings, the answers to frequently-asked questions can sometimes help you.
Get Started with Secure: Secure provides a detailed analysis of your Salesforce security, going beyond the basic Salesforce Health Check. With Secure, administrators gain the ability to align security settings with industry best practices and organizational InfoSec policies, ensuring robust protection of sensitive data.
Install Secure: Classify your data, evaluate its protection status, and address security vulnerabilities by using a risk-based scoring system with Secure.
Secure Reporting Tab: Generate reports that help you focus on the most critical aspects of your security posture. The Reporting tab offers three types of reports that you can customize with date ranges and filters. Share reports directly within the platform or export them.
Security Center Features in Secure: Secure by Own from Salesforce helps you find and classify sensitive data, evaluate user access and data exposure, and undertake risk analyses. These features are now sold as part of the Security Center Extension managed package. They have the same functionality as those available to existing Secure customers.
Shield Features in Secure: Secure by Own from Salesforce includes features that help you get more out of Salesforce Shield products. These features are now sold as part of the Shield Extension managed package. They have the same features as those available to current Secure customers.
Secure Your Code: This section contains information about implementing security in your code.
Sharing Rules: Use sharing rules to extend sharing access to users in public groups, roles, or territories. Sharing rules give particular users greater access by making automatic exceptions to your org-wide sharing settings.
Create Apex Sharing Reasons: When creating Apex managed sharing, create Apex sharing reasons for individual custom objects to indicate why sharing was implemented.
Recalculate Apex Managed Sharing: Developers can write batch Apex classes that recalculate the Apex managed sharing for a specific custom object.
Security Center Extension: Security Center Extension by Own from Salesforce helps enhance data security and compliance. After installing the Security Center Extension managed package, use it to find sensitive data and manage data classification and user access settings. You can then decide how best to secure that data by using other Salesforce settings and features. The Who Sees What Explorer tab shows object and field-level access and permission assignments. On the Data Classification tab, find and classify sensitive fields such as personal information or financial data. The Security Insights tab helps you analyze your security posture and generates a risk-prioritized list of security gaps.
Controlling Access Using the Role Hierarchy: Determine whether users have access to records they don’t own, including records to which they don’t have sharing access, but someone below them in the hierarchy does.
Control Who Sees What: Salesforce data sharing lets you expose specific data sets to individuals and groups of users. Permission sets, permission set groups, and profiles provide object-level and field-level security by controlling access. Record-level sharing settings, user roles, and sharing rules control the individual records that users can view and edit.
Set Up Your Users’ Object, User, and Field Permissions: Salesforce provides a flexible, layered data sharing design so admins can control user access to data. Use profiles to configure default settings and layouts, then use permission sets and permission set groups to grant object, user, and field permissions. Salesforce also provides tools to automate, migrate, or report on your users’ permission assignments.
Additional Features that Control Data Access: Salesforce offers many optional features that allow you additional control over what data your users can access. As you decide which features to configure for your Salesforce org’s data access strategy, review these features and their applications.
External Organization-Wide Defaults Overview: External organization-wide defaults provide separate organization-wide defaults for internal and external authenticated users to help you better secure your data.
Restriction Rules: Restriction rules let you enhance your security by allowing certain users to access only specified records. They prevent users from accessing records that can contain sensitive data or information that isn’t essential to their work. Restriction rules filter the records that a user has access to so that they can access only the records that match the criteria you specify.
Create a Restriction Rule: Control the records that a specific user group is permitted to see. When a restriction rule is applied to a user, the data that the user has access to via org-wide defaults, sharing rules, and other sharing mechanisms is filtered by the record criteria that you specify.
Scoping Rules: Scoping rules let you control the records that your users see in list views, reports, and SOQL queries based on criteria that you select. You can set up scoping rules for different users in your Salesforce org so that they can focus on the records that matter to them. Users can switch the set of records they’re seeing as needed.
Create a Scoping Rule: Determine which records your users see by default. When a scoping rule is applied to a user, the data that the user sees in list views and reports is filtered by the criteria you set.
Create a Flow That Applies a Scoping Rule: You can create a scoping rule and then create a flow that users can run to update their user record. Users can filter records by scope to see only the records they need to focus on.
See Account Access from Manual Shares or Account Teams with Reports: See the account records that are shared manually or through account teams in your Salesforce org and which users or groups have access to them. Before building reports, create a custom report type on the Account Share object, which represents sharing entries on an account.
Sharing Considerations: Learn how sharing models give users access to records they don’t own.
Sharing Rule Categories: When you define a sharing rule, you can choose from the following categories in the owned by members of and Share with dropdown lists. Depending on the type of sharing rule and the features enabled for your organization, some categories may not appear.
Defer Sharing Calculations: Performing a large number of configuration changes can lead to very long sharing rule evaluations or timeouts. To avoid these issues, a Salesforce admin can suspend sharing calculations, specifically for sharing rules and group membership, then resume calculations during an organization's maintenance period.
Asynchronous Deletion of Obsolete Shares: Obsolete shares are removed asynchronously after groups are deleted or users are deactivated so that admins can perform other operations without waiting for shares to be deleted.
Defer Group Membership Calculations: If you’re making changes to groups or related features that affect many records, you can temporarily suspend automatic group membership calculations and resume them after you finish your updates. You must resume calculations and do a full sharing rule recalculation, or you can experience sharing inconsistencies in your records.
Keep Manual Shares When Transferring Records: By default, when ownership of a record is transferred, Salesforce deletes manual shares on the record, which can cause users to lose record access. Enable the “Keep manual shares when transferring records” setting to retain manual shares when a record’s owner changes.
Object-Specific Share Locks: When you create, edit, or delete a sharing rule, recalculation runs to update record access in your Salesforce org. This operation can take some time if you have many users and records. The object-specific share locks feature enables you to make changes to a sharing rule for other objects simultaneously, depending on the objects affected by the sharing rules, sharing rule type, and target groups or roles of the affected users.
View Sharing Overrides: When you select an object in the Sharing Settings page, the page includes a Sharing Overrides related list, which shows any profiles that ignore sharing settings for that object.
Organization-Wide Sharing Defaults: Define the default access that users have to records they don't own with organization-wide sharing settings. Organization-wide sharing settings can be set separately for custom objects and many standard objects. You can set different levels of access for internal and external users.
Monitor Public Group Members with Reports: See all users, roles, roles, territories, and other groups. Create a custom report type before building reports on public group members.
Recalculate Sharing Rules Manually: When you make changes to sharing settings, groups, roles, and territories, sharing rules are reevaluated to add or remove access as necessary. You can manually recalculate sharing rules if sharing rule updates have failed or aren’t working as expected.
Require Permission to View Record Names in Lookup Fields: To better protect your Salesforce org’s data, you can restrict who can view record names in lookup fields and system fields, such as Created By and Last Modified By. If you enable the Require permission to view record names in lookup fields setting, users must have Read access to these records or the View All Lookup Record Names permission to view this data.
Defer Sharing Rule Calculations: If you’re making a large number of changes that affect sharing rules, including changes to sharing rules, roles, territories, or public groups, you can temporarily suspend automatic sharing rule calculations and resume them after you finish your updates. You must resume calculations and do a full sharing rule recalculation, or you can experience sharing inconsistencies in your records.
Sharing Rule Types: You can base a sharing rule on record ownership or other criteria.
Create Sharing Rules: You can create sharing rules based on the record owner or other criteria, and sharing rules that grant record access to unauthenticated guest users. You can also create sharing rules based on group membership for the User object.
Edit Sharing Rules: You can edit the label, rule name, and sharing access level for all sharing rules. Depending on the rule type, you can also edit additional settings. If you must edit other fields in the sharing rule, like who is granted access, delete the rule and create a new one.
Create Guest User Sharing Rules: A guest user sharing rule is a special type of criteria-based sharing rule and the only way to grant record access to unauthenticated guest users. Guest user sharing rules can only grant Read Only access.
Considerations for Making Sharing Updates: Review these considerations before making sharing changes, such as updates to organization-wide defaults, sharing rules, account ownerships, or group memberships.
User Sharing and Visibility: User Sharing enables you to show or hide an internal or external user from another user in your organization.
Populate and Secure Data Sets with Seeding: Save your company time and ensure data consistency and reliability when you seed data into a sandbox or production org for development, testing, and deployment. Seeding by Own from Salesforce enhances data security and compliance by maintaining object relationships during seeding.
Seeding Data in Salesforce: Streamline development and testing by seeding data from one org to another with the Seeding app. You can customize data copying into sandbox and production orgs. Create and configure seeding templates that define which records to add, update, or delete. Use filters to control the amount and type of data seeded so that your team can reproduce customer use cases and production scenarios.
Seeding Template for Salesforce - Advanced Settings: Control your match processing for auto-cloned objects such as users, products, and price books within the Seeding application. Advanced settings can help prevent duplicate object records and make sure every record has a designated owner.
Activate Your Backup & Recover Platform: Prepare to manage and protect your Salesforce data when you activate the Backup & Recover platform during Seeding and Anonymize onboarding. Make sure to sign in or activate your Backup & Recover Platform before onboarding Seeding and Anonymize.
Create an Anonymization Template and Execute an Anonymize Job: Create and configure an Anonymization template for Salesforce by specifying objects and sensitive fields with replacement values. Use the Anonymization template to mask sandbox data in a standalone anonymize job, or reference the Anonymization template in a seeding template to anonymize the source data prior to it being seeded.
Create a Levels Seeding Template: Levels templates for Salesforce provide a more streamlined approach to managing complicated hierarchy structures compared to Nodes templates. By reducing complexity and automating relationship creation, Levels templates offer simpler seeding without requiring full knowledge of the data source structure. Create and configure a Levels template by adding root objects and selecting up to four hierarchy levels.
Create a Nodes Seeding Template: Craft Nodes templates for Salesforce to precisely populate data objects, tailoring data seeding to your organization's needs. Manually add root, child, and optional parent objects for targeted seeding, offering greater control but requiring deeper knowledge of the data hierarchy.
Define Your Business Use Case: Identify which Salesforce production orgs or sandboxes to use as data sources or destinations for seeding jobs. Determine the most suitable seeding templates, whether pre-defined templates (starter, CPQ, FSL, nCino) or custom Levels or Nodes templates. And determine which sandboxes need anonymization along with the object field types to be anonymized. Seed relevant data from production orgs or sandboxes into Developer, Developer Pro, Partial, and Full sandboxes, and even into production orgs.
Self-Service Onboarding for Seeding and Anonymize: The Seeding and Anonymize applications let you copy data between Salesforce orgs and mask sensitive information. These applications support software development, testing, and training efforts.
Salesforce Authenticated User Permission Requirements for Seeding: In a Salesforce data environment, the Seeding application uses an authenticated user to access production and sandbox orgs. Authenticated users require specific permissions to perform tasks such as building templates that define subsets of related data to extract from a source org. And then using those templates to seed sandboxes with identical data structures.
Seeding for Salesforce Best Practices: Perform successful data seeding jobs when you follow best practices to make sure object relationships and metadata are configured correctly.
Create a Seeding Template for Salesforce: Create an initial version of a seeding template for performing data seeding. By default, template creation is based on the blank template. This means that the created template doesn’t have any predefined nodes (objects) or predefined levels. When you create the template you define the template type: Nodes or Levels.
Disable Auto-Clone Object Matching from Your Salesforce Template: Disable auto-clone object matching to speed up your seeding jobs and avoid seed failures caused by large records. When you disable auto-clone matching, you reduce processing time, especially when the destination already contains the necessary records.
Editing a Levels Template for Salesforce: When opening an existing Levels seeding template, it opens in view-only mode. You can edit a seeding template if another user isn't editing the template. Master admins can edit locked templates.
Editing a Nodes Template for Salesforce: When opening an existing Nodes seeding template, it opens in view-only mode. You can edit a seeding template if another user isn't editing the template. Master admins can edit locked templates.
Common Errors and Warnings - Seeding and Anonymize for Salesforce: Check out common errors and warnings you might encounter while using Seeding and Anonymize in Salesforce. For each issue, we offer a clear explanation of the cause and actionable steps you can take to resolve it.
Execute a Seeding Job for Salesforce: After your seeding template is built, you can use it in a seeding job to copy (seed) data into a Salesforce sandbox or into a Salesforce production org. You can do this directly from the Template Builder tab. If the Seed... button isn't available in the Template Builder tab, contact your administrator to grant you the required permission.
Seeding for Salesforce FAQs: If you encounter issues related to Seeding for Salesforce, the answers to frequently-asked questions can sometimes help you.
Seeding Support for Attachment, Document, and ContentDocument Objects: The Seeding application for Salesforce seeds dummy files. During a seeding job, the original files are replaced with a dummy file that correlates to the original file type, matching it by file name. Replacement with a dummy file is done to prevent users from seeing the actual data, thereby making the replacement file comply with Personally Identifiable Information (PII) protection.
Filter Salesforce Object Records for Seeding: Limit the records used for seeding to control which data is copied. Filtering object records helps make seeding more efficient and relevant for its specific purpose, such as testing. Strategic filtering prevents the inclusion of unnecessary or problematic data, such as redundant child objects or unconverted leads, which maintains data integrity.
Seeding to a Full Sandbox: Incrementally seed a Full Salesforce Sandbox that already contains data from Salesforce.
Get Service and Backup IDs for Salesforce Seeding Jobs: Retrieve data from any service backup, regardless of service or Salesforce org status, by obtaining the Service ID and Backup ID. Seed data from a specific point in time, using any backup, which is useful when the live service is unavailable or unsuitable for seeding.
Get Started with Seeding for Salesforce: Seeding populates data sets from one Salesforce org into another, which lets users develop, test, and train using accurate data. Extract data from a source org and use it to seed any sandbox with an identical data structure. Seeding also helps maintain object relationships, select specific records, and troubleshoot permissions or data issues.
Recent Seeds Information and Seeding Job Reports (Salesforce): Seeding application processing generates information about each executed, seeding job Recent Seeds Information, Salesforce Automations Report, Seeding Report. These reports help you in understanding the seeding job's status and outcome.
Use Advanced Settings to Manage Seeding Templates in Salesforce: Fine-tune your seeding templates using advanced settings to optimize the seeding process. Prevent duplicate object records with auto-cloned object matching. Adjust the default batch size to avoid timeout errors during seeding.
Manage the Salesforce Seeding Object Batch Size: When using your template to seed a very large object, or an object that triggers many automations, the insertion might fail due to a timeout with your cloud service provider. To successfully seed such an object, lower the number of object records per processing batch for the insertion of the object. The process to change an object's batch size is the same for both Nodes and Levels templates.
Navigating the Templates Tab: The Templates tab under the Seeding tab presents a listing of previously created, available templates with template-related information. You can clone and delete templates provided they aren’t being edited by another user.
Pair Salesforce Objects by Field Value with Field Matching: Use Field Matching to manually match source and destination objects by a field value instead of an ID. When you select a unique value, the Seeding application maps the source and target records to prevent duplicate values.
Node Context Menu for a Salesforce Nodes Template: Each node in a Nodes Template has an available options context menu, regardless of where that node (object) is located in the template hierarchy (Parent, Root, or Child).
Seeding Recurring Activities: When you seed recurring activities in Salesforce, you can automatically schedule and manage activities that occur repeatedly. By automating the creation of events or tasks that occur at specific times, you can make your work processes more efficient, cut down on manual work, and keep your activity management consistent.
Schedule Seeding in Salesforce Overview: Schedule seeding jobs to automate multiple seeding tasks, which increases efficiency by reducing the need for manual intervention. Ensure necessary destinations are fully seeded with the required data in advance of upcoming sprints and development projects to maintain consistency. Choose one-time or recurring seeding jobs with error handling and alerts.
Schedule, Edit, and Delete Salesforce Seeding Jobs: Schedule recurring and onetime seeding jobs in advance when you use Schedule Seeding. Enhance seeding efficiency by automating recurring tasks and manage all scheduled jobs from a central tab.
Seeding and Anonymizing Data: The Seeding application copies selected Salesforce objects from a production org or sandbox to a sandbox, supporting software development, QA, and training. The Anonymize application replaces data in Salesforce sandbox object fields with alternate values to privatize original data and verify compliance with privacy laws and regulations.
Seed Attachment, Document, and ContentDocument Objects: Seed dummy content in Salesforce to prevent users from seeing actual data and comply with PII protection requirements. When using Nodes templates to seed the ContentDocument object, you can choose to seed dummy content or real content. The Attachment, Document, and ContentDocument objects represent uploaded files.
Seeding Data in ServiceNow: Seeding for ServiceNow allows you to populate data sets from a production, sub-prod, or personal developer instance. Protect personally identifiable and sensitive information when you seed anonymized data using custom templates. Build templates that define a subset of related data to extract from a source instance, and use those templates to quickly and repeatedly seed any existing sub-prod with an identical data structure. Save time by automating recurring and one-time seeding jobs. Make sure that specific destinations are fully seeded with required data, in advance of upcoming sprints and development projects.
Getting Started with Accelerate for ServiceNow: Accelerate for ServiceNow allows you to populate data sets from a production/sub-prod instance into a sub-prod instance with matching metadata.
Getting Started with Anonymize for ServiceNow: Manage anonymization templates and apply them to ServiceNow data using Salesforce's Anonymize application. Use the application to anonymize ServiceNow data in seeding jobs to make sure that sensitive information is protected.
The Anonymize Tabs for ServiceNow: When you open the Anonymize app (by clicking the Anonymize tab, which is at the top of the Own UI), there are two tabs. The Templates tab which is displayed automatically upon access of the Anonymize application and the Activities tab.
Build the Seeding Template for ServiceNow: Select the tables you want to seed to make sure you are seeding the exact data required by your use case. Once your seeding template is in Edit mode, you can start building your node hierarchy of tables that you want to seed in the Template Builder tab.
Create a Seeding Template for ServiceNow: Use the Create New Template window to create an initial version of a seeding template for performing data seeding. By default, template creation is based on the blank template (Create From field = Blank template), which means that the created template does not contain any predefined nodes (tables).
Editing a Nodes Template for ServiceNow: When opening an existing seeding template, it opens in view-only mode. You can edit a seeding template if another user isn't editing the template. Master admins can edit locked templates.
Filter the Data for Seeding in ServiceNow: Control the number and order of records and the type of records that are seeded for a selected template table with the Filter option.
Filter ServiceNow Records for Seeding: Limit the records used for seeding to control which data is copied. Filtering object records helps make seeding more efficient and relevant for its specific purpose, such as testing. Strategic filtering prevents the inclusion of unnecessary or problematic data, such as redundant child objects or unconverted leads, which maintains data integrity.
Recent Seeds Information and Seeding Job Reports (ServiceNow): Seeding application processing generates information about each executed, seeding job Recent Seeds Information, Seeding Report. These reports help you in understanding the seeding job's status and outcome.
Managing Seeding Templates in ServiceNow: The Templates tab under the Seeding tab presents a listing of previously created, available templates with template-related information. You can clone and delete templates provided they aren’t being edited by another user.
Node Context Menu for a ServiceNow Nodes Template: Each node in a Nodes Template has an available options context menu, regardless of where that node (table) is located in the template hierarchy (Parent, Root, or Child).
Run a Seeding Job for ServiceNow: You can run the seeding job directly from the Template Builder of the template. If the Seed button isn't available in the Template Builder tab, contact your administrator to grant you the required permission.
Schedule Seeding in ServiceNow: Schedule seeding jobs to automate multiple seeding tasks, which increases efficiency by reducing the need for manual intervention. Ensure necessary destinations are fully seeded with the required data in advance of upcoming sprints and development projects to maintain consistency. Choose one-time or recurring seeding jobs with error handling and alerts.
Schedule, Edit, and Delete Scheduled Seeding Jobs In ServiceNow: Schedule recurring and onetime seeding jobs in advance when you use Schedule Seeding. Enhance seeding efficiency by automating recurring tasks and manage all scheduled jobs from a central tab.
Seeding and Anonymizing ServiceNow Data: The Seeding application copies selected ServiceNow tables from a production org or sandbox to a sandbox, supporting software development, QA, and training. The Anonymize application replaces data in sandbox table fields with alternate values to privatize original data and verify compliance with privacy laws and regulations.
Configure an Anonymization Template for ServiceNow: After you create an anonymization template for ServiceNow, the new template automatically displays in the My Templates page. The template is empty of tables to anonymize, and is in Edit mode, meaning that its content can be modified. Configure the new template with tables and configure the associated columns that you want the template to anonymize.
Create an Anonymization Template for ServiceNow: When you create an anonymization template for ServiceNow, the new template automatically displays in the My Templates page. The template is empty and in Edit mode, meaning that its content can be modified.
Delete Tables from an Anonymization Template for ServiceNow: Remove tables from anonymization templates in ServiceNow to refine your data anonymization strategy. When you delete a table, it's removed from the template, and its data won't be anonymized.
Anonymize As Part of a Seeding Job in ServiceNow: Anonymize as part of a seeding job in ServiceNow enables you to anonymize the seeding source's data. Source data such as personally identifiable information (PII), sensitive information, and classified information is anonymized before being copied to (seeded in) the destination.
Work with Anonymization Templates for ServiceNow: Anonymization templates for ServiceNow can be managed through various actions such as creating, configuring, deleting, and exporting. Tables that are included in both the seeding and anonymization templates can be anonymized as part of the seeding process.
Generating and Seeding Synthetic Data: The Seeding application offers a combined generate-seed functionality, eliminating the need for a seeding source. By utilizing both a Generate template and an anonymization template, a seeding job can automatically create specified synthetic data and then populate a sandbox with it. This process significantly streamlines development by providing relevant, meaningful test data for necessary objects directly in your sandbox. Consequently, you avoid the time-consuming tasks of manual data creation or copying data from production or other sandboxes.
Generate Synthetic Data and Seed to a Sandbox Environment: Create and configure an anonymization template, or edit an existing anonymization template. This is the template that will be used to generate the required, synthetic data.
Set Masking Rules: Set masking rules for standard and custom objects in your sandbox org.
Set Up Actions with Chatter Enabled: Global and object-specific actions enhance the Chatter experience for your users in Salesforce Classic and in the Salesforce app.
Set Up Actions Without Chatter Enabled: You can set up object-specific and global actions for the Salesforce mobile app or third-party apps, even if your org doesn’t have Chatter enabled.
Setup Home Page: The Home page in Setup is the jumping off point for customizing your org, finding important setup tools and information, and building and managing applications.
Quick Access Menu: The quick access menu offers handy shortcuts to customization features.
Recent Items List (Beta): The Recent Items list in Salesforce Classic shows recent metadata items that you’ve viewed, edited, or created and their related objects.
Configure System Overview Messages: Add system overview usage messages to the Salesforce Home page to remind you when your org approaches its limits. You can expand, collapse, and dismiss the system overview messages that appear on the Home page. By default, the system overview home page messages are enabled.
Implicit Sharing: Implicit sharing is a built-in mechanism in the Salesforce platform that automatically grants users access to parent records if they can access related child records and vice versa. There’s also built-in sharing behavior for external site and portal users.
Organization-Wide Default Access Settings: For most objects, you can assign default access to Controlled by Parent, Private, Public Read Only, or Public Read/Write. Other access levels, like Public Full Access and View Only, are available for only specific objects.
Shield Extension: Shield Extension managed package by Own from Salesforce includes tools that help you get the most out of Shield Platform Encryption, Field Audit Trail, and Field History Tracking. The Platform Encryption Analyzer streamlines field-level encryption planning and implementation. Use the Field History Explorer to view history changes for tracked fields. With History Retention Policy Manager, monitor and update field history tracking and data retention configurations.
Add Lightning Components to Secure: Integrate security features and functionalities into Salesforce record pages by adding Lightning components. Improve the security posture of your Salesforce instance by using components that make security-related data easily accessible and manageable right from the record pages.
Add Visualforce Pages to Secure and Page Layouts: Enhance the functionality and security of your Salesforce environment by adding Visualforce pages. Create custom user interfaces tailored to your business that improve user experience and operational efficiency.
Analyze Platform Encryption Fields: Determine which fields can be encrypted without affecting other configurations in an org. Prioritize which fields need encryption based on their sensitivity and compliance requirements.
Shield Extension Configuration: The Shield Extension Config tab contains configuration options for the Shield Extension. Users with the appropriate permissions can modify various settings such as encryption fields and analysis scheduling.
Dynamic SOQL and Secure Platform Encryption: Dynamic SOQL lets you create SOQL strings at run time within Apex, so you can build more flexible applications. This flexibility is useful in environments where queries are constructed dynamically based on user input or other run time conditions.
Turn On Field History Tracking: Field History Tracking helps ensure compliance, maintain data integrity, and enhance security by providing a detailed audit trail of changes to critical fields.
Encrypt Fields with Secure: Encrypt sensitive fields using the Platform Encryption Analyzer so you can protect your data. Encrypt fields directly from the analysis results, and then confirm the encryption options. You can also exclude fields from encryption, include previously excluded fields, and download a compliance report of the last analysis as a PDF file.
Shield Extension Tabs: Feature tabs provide a framework for maintaining data integrity and confidentiality within Salesforce. Understand which fields are displayed on the Shield Extension tabs.
Get Started with Shield Extension: Shield Extension provides comprehensive tools to analyze Salesforce field encryption options, review data retention policies, and explore field history for enhanced data security.
History Retention Policy Manager Tab: Maintain compliance with data retention policies, manage field history tracking, and ensure sensitive data is properly monitored from the History Retention policy Manager tab.
Install Shield Extension: Analyze and encrypt Salesforce fields to enhance data security and compliance. Shield Extension helps you manage and monitor data history and retention policies for comprehensive auditing and control.
Change History Retention Policies: History retention policies specify how long data is retained before being archived or deleted. There are ranges for each policy that you can change to fit your company's needs
Platform Encryption Analyzer Tab: Before encrypting fields in an org, find out which ones are compatible with Salesforce Shield Platform Encryption. Encryption helps protect sensitive data by converting it into a format that is unreadable without the appropriate decryption key.
Set Up Site.com Users: Before users can access Site.com, you must allocate a Site.com feature license to each user and assign a user role at the site level. The features available when editing a site in Site.com Studio vary depending on these settings.
Export Assets: Designers and site administrators can export all site assets separately from the .site file. You can export assets together or individually.
Import and Manage Assets: Contributors, publishers, and site administrators can import a variety of assets, such as images, HTML pages, and PDFs, to use in a website. You can import assets and files individually, or use a zipped file. When importing entire websites or large numbers of assets, it’s easier to create a zipped file of the content with the desired folder structure. When importing the zipped file for a website, Site.com recreates your website and places everything in the same folder structure.
Setting Custom Authorization: When you select Custom authorization, you get a great deal of flexibility in controlling access to your site. Not only can you control who has access to top level resources, like folders and pages, but you can also set access at the individual resource level.
Remove Site.com Authorization: You can remove authorization for a resource by either deleting it from the authorization table under Site Configuration, or by deselecting Requires Authorization from the Actions menu.
Site.com Authorization Overview: As part of your site design, you might want to control what content is public and private to your site visitors. New sites are initially set so that all site resources, such as folders and pages, are public. You can change the default setting from the Authorization view found under Site Configuration.
Creating Branding Properties: With branding , you can quickly create style properties that can be reused by editors of your site.
Use the Branding Editor: The Branding Editor provides a centralized place to customize and then preview the changes that you make to the branding properties in your site.
Set Up Branding Properties: After you create branding properties, the next step is to reference them as expressions in your Cascading Style Sheets (CSS) or Site.com page elements such as content blocks or custom code elements.
Adding Breadcrumb Navigation to Pages: Add a Breadcrumb page element to your page to help users navigate through your site and show the page’s location in the site hierarchy.
Create Categories and Terms: Categories let you create groups of terms that you can use to classify the items in your site's content lists.
Enable Clickjack Protection in Site.com: Clickjacking is a type of attack that tricks users to click something, such as a button or link, because they perceive they are clicking something safe. Instead, the button or link performs malicious actions on your site, leading to data intrusion, unauthorized emails, changed credentials, or other site-specific results. Hidden iframes can be placed maliciously on site pages and entice users to click a button or link that appears below the hidden iframe. With clickjack protection, you can configure whether your browser allows external domains to frame your Site.com site pages.
Add Custom Code to Pages: Custom code lets you customize your site using markup, such as HTML and JavaScript.
Create Branded Pages Overview: When you create a Community site, Salesforce automatically creates a Site.com site and associates it with your community.
Display Current Community User Information: Site.com designers creating authenticated pages for a community site can display the current user's information by accessing CurrentUser namespace expressions.
Create a Site.com Community: Each community has one associated Site.com site that lets you add custom, branded pages to your community. By default, Site.com pages are publicly available and don’t require login, but you can also create private pages that only community members can access.
Determine the URL of a Site.com Page: Determine a Site.com page’s URL to let your users access it directly, make it the home page for your community, and more.
Use Site.com to Customize Your Community: Communities users can use Site.com to build custom, branded pages for a community. There are many approaches to building custom pages for your community, but these actions are some of the typical stages involved.
Content List Field Properties: When adding or editing fields in a content list, use the options in the Properties pane to control how the selected field functions.
Content List Field Types: These field types are available to you when you create or edit a content list. You can add any combination of fields to a content list.
Adding and Editing Content List Fields: As a site administrator or designer, you can add fields to a content list and edit field properties to suit your needs.
Content Lists and Categories Overview: Content lists let you create and store content items to use in your site, such as press releases, blog posts, and news articles. Categories let you create groups of terms to classify the items in your content lists.
Content List XML Format: To import records into a content list in Site.com Studio, you must create an XML file that consists of these elements.
Importing Records into Content Lists: Import records from existing press releases, articles, or blogs into your site’s content lists. For example, if you have a blog that’s hosted elsewhere, you can export the blog’s posts and then import the contents to use in your site.
Sample Content List XML File: This XML code makes up a sample XML file for importing records into a content list. In this case, the content list has two text fields called Title and Author, and a number field called Rank.
Add Content Blocks to Pages: Content blocks contain the text of your website pages, and can also house images, videos, and hyperlinks. Designers and site administrators can add content blocks to pages when in Design Mode.
Add Anchors to Pages in Design Mode: An anchor is an invisible marker that identifies a particular location on a page. If you’re a designer or site administrator, you can add an anchor to the page and then create a hyperlink that jumps to that specific location, which can be useful if a page is particularly long. For example, if your page has several sections, you could add links to each section at the top of the page to aid navigation.
Edit Content Blocks in Design Mode: Designers and site administrators can edit content blocks on the page. Content blocks contain the text for site pages, and can also house images, videos, and hyperlinks.
Attach Hyperlinks to Text and Images in Design Mode: When viewing a page in Design Mode, designers and site administrators can create hyperlinks to external Web pages or websites, pages and assets in the site, email messages, and anchors on the page.
Preview How Pages Appear on Mobile Devices: With live mode, site administrators, designers, and contributors can preview how pages and templates appear on devices such as mobile phones and tablets.
Edit Content Blocks as a Contributor: Content blocks contain the text of your website pages, and can also house images and hyperlinks. As a contributor, you can edit the text in editable content blocks using an inline editor. Because you're editing the text inline, you always know exactly how the finished page looks when it's live.
Add Images to Text as a Contributor: As a contributor, you can quickly add images to any editable text areas on the page using an inline editor.
Understand the Inline Editing Toolbar: As a contributor, you can use the inline editor to edit any editable text areas on the page. Editable areas display a gray border when you hover over the text.
Understand the Content Editing Toolbar: Designers and site administrators can edit content blocks when in Design mode. Content blocks contain the site page's text, along with images, videos, and hyperlinks.
Add Video to Content Blocks in Design Mode: Designers and site administrators can add YouTube®, Google®, Adobe® Flash®, Windows Media®, and Apple QuickTime® videos to content blocks when viewing a page in Design Mode.
Setting Up Custom Properties: You can use custom properties in your website by using expression language syntax within a style sheet, code block, widget, or the HTML page editor.
Storing Assets to Use with Salesforce Objects: Because websites built with Site.com are publicly available, site visitors don't have the security privileges required to view images and documents stored in your Salesforce objects, which are available to authenticated users only.
Improve Performance Using Caching: When working with data-bound page elements, such as data repeaters, data tables, and data functions, you can improve the performance and page rendering of your website using caching. Caching controls how often a page containing a data connection requests data from Salesforce.
Displaying Data or Content Using Custom Code: In addition to data elements and content blocks, you can also use custom code as an alternative way to display data in a data repeater or in a page data connection. It's particularly useful for displaying field data that's inline with text.
Displaying Data Using Content Blocks: In addition to data elements and custom code, you can also use content blocks as an alternative way to display data in a data repeater or in a page data connection. It's particularly useful for displaying field data that's inline with text.
Setting the Default Value of Input Fields: You can set the default value of an input field that you add to a form or page. This automatically populates the input field with the value you specify when the page loads.
Adding a Form to the Page: Use forms to collect data from your site visitors and submit the data to standard or custom Salesforce objects. Create web-to-lead forms, capture customer details, or gather feedback on your products or services.
Input Field Properties: When adding or editing input fields on a form or page, use the options in the Field Properties section of the Properties pane to control how the selected input field functions.
Input Field Types: When adding input fields to a form or page, the following field types are available. However, if the object connected to a form doesn't contain a particular field type, you can't add that input field type to the form.
Add Input Fields to Forms or Pages: Add additional input fields to an existing form. Each input field binds to a field in the object the form is connected to. Add input fields directly to a page, panel, data repeater, or data table to build your own custom features using
Styling Forms: Forms are styled using CSS themes that you can customize to match the design of your website.
Setting a Form's Submit Behavior: When your site visitors submit a form successfully, you can either redirect them to another page or display a message indicating that they were successful.
Using Data Functions: A data function lets you connect to a standard or custom Salesforce object, perform calculations on the returned results, and display the calculation on the page. For example, for a particular field in an object, you can use a data function to calculate the total value or the average amount of all returned records.
About Displaying Dynamic Data Using Expressions: Site.com uses expression language to display data dynamically. Expressions serve as placeholders for data that is replaced with information when the page loads. When working with data-bound page elements or custom widget properties, you can use expressions to customize how data is displayed on the page.
Access Data in Related Objects Overview: Standard and custom objects have relationships that define how records in one object relate to records in another. For example, the Accounts object has a one-to-many relationship with the Contacts object—that is, each account can have one or more contacts associated with it. This relationship is also known as a parent-to-child or a master-detail relationship.
Data Filters: When you add a data repeater, a data table, or a data function to a page, you don't have to limit the records it retrieves. However, if you're working with a Salesforce object that has thousands of records, you can limit the returned results using filter criteria.
Site.com Data Services Overview: Site.com data services combine many features that let you connect to standard and custom Salesforce objects. Retrieve data from your organization's objects and dynamically display it on your site pages, or alternatively, gather and submit data from your customers. And when you update data in your Salesforce object, the changes are reflected automatically on the live site—no site updates required!
Page Data Connections Overview: Page data connections make it easy for site administrators and designers to create a detail page for a single record when working with Salesforce objects.
Repairing Data Connections: If you or another user modifies the object that an existing data repeater, data table, data function, or form is connected to, the data connection might break. For example, this can happen if a connected object or field is renamed or deleted, or if its permissions are changed.
Dynamically Retrieve Data with Data Repeaters: Use a data repeater to connect to a standard or custom Salesforce object and retrieve a dataset based on the filter criteria that you specify.
Display Data or Content Using Data Elements: You can use a data element to display the data retrieved by a page data connection or a data repeater. The data element binds to a field in the object and acts as a placeholder that's replaced with the field's data when the page loads.
Data Filter Examples: When working with data repeaters, data tables, and data functions, you can filter the data you retrieve in many ways. In this topic, we explore two options— fixed values and URL query strings—to illustrate some common filtering techniques.
Dynamically Retrieve Data with Data Tables: Use a data table to connect to a standard or custom Salesforce object, retrieve a dataset based on the filter criteria that you specify, and display one or more record as rows in the table.
Edit Columns in a Data Table: A data table's columns bind to the fields of the object it's connected to. Each column cell acts as a placeholder that is replaced with the field's data when the page loads.
The Default, Error, and No Data Views: When working with data repeaters, data tables, data functions, and forms, you can customize what your site visitors see if an error occurs when connecting to the data source.
Add Domains Using CNAME Records in Site.com: To publish a site to the Internet, you must first set its domain information. Add a domain name using a CNAME record if you're creating a domain name, or if you're adding a domain name that's currently not in use.
Manage Domains in Site.com: Before you can publish your site to the Internet, you must set the site's domain information.
Add Domains Using TXT Records in Site.com: To publish a site to the Internet, you must first set its domain information. Add a domain name using a TXT record if you're reusing a domain name that's currently in use. For example, if you're migrating from an existing site to a new Site.com site, you can transition seamlessly to the new site when you're ready to go live. This method is suitable only for existing sites that use DNS A records.
Understanding the Contributors's Overview Tab: As a contributor, when you open a site in Site.com Studio, it opens on the Overview tab. Here you can access and edit the site's pages and content, and import images and files.
Create an Event: Use events to add interactive and animated effects to the pages and page elements of your website.
Events Overview: Events enable you to add interactive and animated effects to the pages and page elements of your website.
Add Pagination to Data Repeaters and Data Tables: Events let you add interactive and animated effects to the pages and page elements of your website. When using data repeaters and data tables, you can add pagination events so users can easily page through the displayed data. Pagination events are particularly useful when working with large amounts of data.
About Site.com Features: >Site.com Studio features vary depending on feature license, user role, and permissions.
Creating and Managing Folders: As a site administrator or designer, you can create folders to manage your pages, style sheets, templates, and assets.
Site.com Tab Overview: If you can't see the Site.com tab, go to the Site.com app. It's available in the Lightning Platform app menu in the Salesforce header. Then click the Site.com tab to view the list of your Site.com sites.
Adding Custom HTML Attributes: You can add custom HTML attributes to pages and page elements, which are rendered on the HTML tag of the page element. For example, this is useful when working with third-party frameworks that render page elements differently based on certain attributes.
Changing a Page's Doctype Property: The Document Type Definition (DTD) or doctype of a page defines which version of HTML it's using. This information is used by some browsers to trigger a standard rendering mode. By default, each page's doctype is set to HTML5, which is the latest version, but you can change it to XHTML 1.0.
Changing a Page Element's HTML Tag: By default, panels, data repeaters, data elements, custom code, and content blocks are each defined as a div, but you can change this to any other HTML tag using the HTML Tag property. This gives you greater flexibility and control over how the page element is displayed on the page.
HTML5 Semantic Page-Layout Tags: HTML5 defines several semantic page-layout tags that describe the content they contain. These tags make it easier for search engines and screen readers to read and organize your content.
Add Images Directly to the Page: As a site administrator, you can add images directly to your site pages and page templates or you can add images to content blocks.
Editing, Disabling, and Deleting IP Restrictions in Site.com: After you create an IP restriction for a Site.com site, you can edit the address range, briefly disable the IP restriction (say, to allow temporary access to a page), or delete the restriction entirely.
Site.comIP Restrictions Overview: Every computer has a unique IP address that it uses to identify itself. Using IP restrictions, you can define a range of permitted IP addresses for the pages, folders, and assets in your site to control visitors' access.
Add IP Restrictions in Site.com: Control site visitors' access to the pages, page templates, folders, and assets in your site by setting the range of permitted IP addresses.
Adding Languages: Add the languages you want your site to support.
Create a Multilingual Site: Creating a multilingual site is a multistep process. It involves defining the languages you want your site to support, adding translated content for each language, and letting your site visitors choose their preferred language.
Setting the Default Language: The default language is the language in which your site initially displays. By default, it's set to English (US), and it serves as the starting point when you add new languages.
Deleting Languages: When you delete a language, the translated content is not actually deleted—it's just no longer available to your or your team. As soon as you add the language back to the site, you can access the translated content again.
Edit Language Content on the Page: The Site.com Studio language selector lets you switch between languages as you edit content on each page. Contributors, designers, and site administrators can each add language-specific content to a page using the language selector.
Exporting Language Content: Export one or more site languages as an .xml file that you can send to your translation service.
Importing Translated Content: You can import a translated .xml file back into your site after your translation service has completed the translations.
Multilingual Sites Overview: Site.com Studio lets you to create different language versions of your site. And because all languages are maintained within the site, you don't need to create and manage a separate site for each language.
About Editing Language Content: The default language is the language in which your site initially displays. By default, it's set to English (US), and it serves as the starting point when you add new languages. So for example, if you build your site and then add French as a site language, the French version initially contains English (US) content until you replace it with French-specific content.
Language-Aware Properties: Several properties in the Properties pane are language aware, meaning they can store different values for each language.
Setting Language Options: After you add site languages in the Languages view, you can define separate settings for each one.
Add a Navigation Menu: By default, when you create a menu, it's generated from the pages and site map links in the Site Map folder in the Site Pages view. However, you can also create a menu that's generated from the pages in the Landing Pages folder or from the child or sibling pages of a site page.
About the Site Map and Page Hierarchy: The Site Pages view on the Overview tab contains the pages and site map links of your website. The Site Map folder reflects the hierarchy or tree structure of your site by housing site pages and links that are included in the site map. When you create pages or site map links, they're automatically added to this folder. The Landing Pages folder houses standalone pages that are excluded from the site map, making it ideal for temporary pages, such as promotional or competition pages.
Style Navigation Menus: Navigation menus are styled using CSS themes that you can customize to match the design of your website. When you add a navigation menu to a page, it uses a default theme to control its appearance. Choose from other existing themes in the Theme Name dropdown list in the Properties pane.
Site.com Page Elements: Page elements are the building blocks of your site pages and page templates. Combined, they provide the page's structure and content.
Add Site.com Page Elements: Page elements are the building blocks of your site pages and page templates. Panel elements add structure to your pages. You can think of both pages and panels as “containers” for the page elements that you add to them.
Edit and Work with Site.com Page Elements: The Page Structure pane displays the hierarchy of all elements on the page and is a very useful way of selecting, moving, and reordering elements, particularly for more complicated page designs.
Site.com: Site.com is a web content management system (CMS) that makes it easy to build dynamic, data-driven web pages quickly, edit content in real time, and manage your websites.
Understand the Site Administrator and Designer's Overview Tab: As a site administrator or designer, when you open a site in Site.com Studio, it opens on the Overview tab. Here you can access and manage the site's components and configure the site's properties.
About Editable Page Elements: When you mark a page element as Editable on a page template, that page element becomes editable in any child pages or templates derived from the parent template.
Create Site.com Pages: As a site administrator or designer, when you create a site page, you can choose to base it on a layout or page template.
Site.com Page Templates Overview: Before you begin building the pages of your website, take some time to plan the pages you need, and in particular, which pages have a similar layout. When you've decided on the layout, the quickest method is to use a page template to build the basic layout.
Create Site.com Page Templates: A page template lets you define the layout and functionality of site pages in one location. By adding common page elements to the template and then basing site pages on it, you can achieve a consistent look and feel throughout your site. And because a template-based page inherits the template's elements, you can make site-wide changes from one location.
Create Editable Template Areas: As the template creator, you specify which elements users can edit in pages based on the template.
Identify Which Template a Site.com Page Uses: When you edit a template-based page, you can't modify its non-editable page elements. You also can't reposition, resize, or delete editable page elements, or alter the events, properties, or style associated with them. To update these elements or properties, you must edit them in the template the page is based on.
Rename, Duplicate, and Convert Pages: When working with pages and templates, you can perform common tasks, such as renaming, deleting, or duplicating pages.
Lay Out Site.com Pages Using Panels: A panel is a useful layout tool that defines the logical divisions of your page and lets you group page elements together for easy movement and positioning. Think of it as a container for other page elements, including other panels, or as a div that wraps around the content placed within it. Panels are ideal for adding editable areas to page templates.
Position Panels Using CSS: A panel is a useful layout tool that defines the logical divisions of your page. Using CSS, you can position panels and improve the layout of the page.
About Site.com User Roles: Each Site.com user must have a user role assigned at the site level, which controls what each user can do in a site. Users can have only one role per site, but their roles can vary between sites. For example, a person can be a site administrator on one site and a contributor on another.
Preview Site.com Sites: Contributors, designers, and site administrators can preview site pages to see how they look when rendered in a browser window. It's always a good idea to make sure your changes are displayed correctly, as this preview is how the pages appear on the live site.
Site Branding Overview: Branding provides a flexible way for you to define different aspects of your website's brand. Once branding properties are defined, your editors can easily customize everything in one centralized place, the Branding Editor. When your website editors customize the properties, they get a preview of their branding changes immediately.
Custom Site Properties Overview: With custom site properties, you can define and store frequently occurring content on your site. For example, you can store your address and phone number as a custom property so that it can be reused by anyone who is editing your site. You can apply stored properties to pages, headers and footers, and widgets quickly by using expression language syntax.
Custom Property Types: Property types are available when designers or site administrators create site branding properties, site custom properties, widget branding properties, and widget custom properties.
Publish Site Changes: When you publish a site in Site.com, you make its pages and assets live on the Internet so site visitors can access them.
Publish and Manage Live Sites: When you publish a site in Site.com, you make its pages and assets live on the Internet so site visitors can access them.
Create URL Redirects in Site.com: If you move or reorganize pages in your site, search engines can have trouble finding the new page locations. To avoid this issue, set up URL redirects to inform users and search engines that site content has moved.
Add Links to a Site Map: Pages aren't the only things you can assign to your site map. Add internal or external URLs to your site map to customize your navigation menus and breadcrumbs, and achieve greater flexibility and control.
Create Style Sheet Items and Groups: When adding style items to style sheets, you can define CSS classes and IDs, or you can redefine the formatting of HTML tags such as body or h1. When you change the CSS style of an HTML tag, anything formatted with that tag is immediately updated.
Create and Use CSS Style Sheets: A default style sheet called “Site Style Sheet” is included with every site you create. However, if you're familiar with CSS and need multiple style sheets, you can create ones to use in your site.
Use CSS Reset: Every browser has set presentation defaults, but unfortunately they aren't standardized across all browser types. This means that when you use CSS to style your site, it doesn’t render as expected when you view it in different browsers.
Cascading Style Sheets Overview: Cascading Style Sheets (CSS) provide a flexible way to add style to the pages of your website. This collection of formatting rules governs the appearance of your pages, and lets you define the fonts, colors, layout, and other presentation features.
Style Pane Properties: The Style pane is a visual CSS editor that lets you modify style properties, such as the background color, font size, and border style, as you work with pages and page elements.
Use the Style Pane: The Style pane is a visual CSS editor that lets you modify style properties, such as the background color, font size, and border style, as you work with pages and page elements. If you're using CSS classes or IDs to style your pages, you can modify or create style items directly from the Style pane, rather than opening the style sheet.
Site.com Version Overview: Each time you publish your site, it's tracked as a version. You can restore your site back to one of the previously published versions. You can't select individual components when restoring; you must restore the complete site.
Restore to a Previous Site Version: The Change History list in Site.com Studio tracks all published versions of your site. You can select any previously published version and restore it. You can only restore an entire site, not parts of a site.
Use the Metadata API to Deploy a Site: As a user, you can migrate a site from sandbox to production. You can use the Metadata API to create a deployable package for Site.com sites and Site.com Communities sites.
Export a Site.com Site: You can export your site from Site.com to your hard drive. The site is exported in a packaged format with a .site extension, which you can import into another Salesforce organization. The maximum site size you can import is 2 GB.
Import External Websites into Site.com: With Site.com Studio, you can import your existing website and recreate it automatically as a Site.com site, which prevents you from having to recode existing HTML pages.
Import a Site.com Site: You can import an exported Site.com site into your organization. When you import a site, you’re given the site administrator role in the site. You can import a site file that was exported in Summer ’19 or later and has a maximum site size of 2 GB.
Configure Site Properties: Set properties for the site, such as the home page, site name, and error page, and create an anonymous preview URL that allows other users to review the site before it goes live. The URL is always valid (unless you disable it) and shows the latest work in progress. It's only available to the people you send it to, and can't be found by search engines.
Copy and Overwrite a Site: Export a copy of your site, and then use the overwrite feature to replace your current production Site.com or Site.com community site with the exported file.
Create Widgets: Widgets let you create custom, reusable page elements by combining existing Site.com page elements, custom code, and CSS.
Edit and Delete Widgets: Access the site's widgets in the Widgets view under All Site Content (on the Overview tab).
Widgets Overview: Widgets let you save time by building custom page elements that you and your team can reuse throughout the site.
Custom Properties for Page Templates or Widgets Overview: When you create a page template or a widget, you can add custom properties to it and specify the value and type of each property to achieve greater flexibility over how templates and widgets are reused.
Plan and Implement a Site.com Website: There are many approaches to building a website. The process that best suits your needs depends on many factors, such as the size of your team and the tasks you're responsible for. If you're a site administrator or designer, you’re involved in every stage, including adding and maintaining the site's content. Alternatively, you can have contributors who add, edit, and maintain this content. And if you're a contributor, you can be responsible for editing and updating all of the site's content, or you can work with other contributors, designers, and site administrators to bring the site to completion. There are various stages involved in creating a site with Site.com.
Report on Salesforce Sites: To track your site activity and usage, take advantage of the Sites Usage Reporting managed package. To help you avoid reaching monthly and daily limits for individual sites and for your org, this package includes site usage reports. You can use those reports to you analyze your monthly page views, daily bandwidth, and daily service request time.
Track Your Salesforce Sites with Google Analytics: Salesforce Sites provides out-of-the-box integration with Google Analytics. To track the usage of your sites and site pages, use Google Analytics. You can track the number of visits, the number of page views, the average time spent on the site, and more.
Configure Site Caching: Caching your Salesforce Site pages, attachments, and static resources can improve page load times and site performance. It can also help you avoid reaching bandwidth and service request time limits.
Configure Salesforce Sites: After you create your site, configure public access and login settings, then activate the site. Optionally, you can also create a syndication feed for your site, and assign error pages for standard errors.
Salesforce Sites Considerations: Before you create and use Salesforce Sites, review considerations around App Exchange packaging, access and authentication, and potential URL conflicts between sites.
Enable Salesforce Sites: To use Salesforce Sites with or without a custom domain, you must first enable Salesforce Sites and register your Salesforce Sites domain. Your company's Salesforce Sites domain is used for all the sites that you create.
Assign Salesforce Site Error Pages: Salesforce sites use Visualforce pages for site and error pages. Sample error pages use the SiteSamples static resource for their style sheet and images.
Salesforce Sites Usage and Billing: Salesforce Sites usage is governed by monthly and daily allocations. Understanding these allocations is important to the success of your sites.
Manage Salesforce Sites Login and Registration Settings: Let users register for and log in to your portal from your public Salesforce Site. For example, users browsing through an ideas site can register and login directly from that site. Then, as authenticated users, those users can vote, add comments, and participate in the ideas community. When users successfully log in, they leave the public site and enter the associated portal seamlessly.
Manage Salesforce Sites: Review the high-level steps to create and manage a Salesforce Site.
Salesforce Sites: Salesforce Sites enables you to create public websites and applications that are directly integrated with your Salesforce organization—without requiring users to log in with a username and password. You can publicly expose any information stored in your organization through a branded URL of your choice. And you can make the site's pages match the look and feel of your company’s brand.
Salesforce Sites URL Redirects: If you move or reorganize pages on your Salesforce Site, search engines can have trouble finding the new page locations. To avoid this issue, set up site URL redirects to inform users and search engines that site content has moved.
Salesforce Sites Security: Review how the Sites and Domains settings related to secure connections affect what your users see when accessing your org.
Set Up Salesforce Sites: Enable Salesforce Sites and create public websites and applications that are directly integrated with your Salesforce org—without requiring users to log in with a username and password.
Manage Salesforce Site Visualforce Pages: Salesforce Sites use Visualforce pages for all site and error pages. To expose a Visualforce page on your site, enable that page for your site.
Manage Salesforce Sites Standard Pages: Control the standard pages users see for your site. Salesforce Sites uses Visualforce pages for all site and error pages. Lightning Platform also provides some standard pages that you can use. Before you can use a page for your site, enable the page for the site. If a page isn’t listed under Site Standard Pages, Salesforce displays an authorization required error.
View 24-Hour Salesforce Sites Usage History: You can avoid exceeding your site usage limits. Monitor the bandwidth and request time usage for each of your sites by viewing the usage data tracked on the 24-Hour Usage History related list.
Use Workflow for Salesforce Sites: With workflow for sites, you can create workflow rules that trigger email alerts when certain site-related criteria are met. For example, create a rule that sends your site administrator an email alert when bandwidth usage reaches 80% of the daily bandwidth limit or when a site's status changes from the active state.
Slack Legacy Actions: Legacy Slack actions are based on an outdated method of managing Slack channels, members, and messages.
Mobile Smart Actions: Mobile smart actions are a set of preconfigured quick actions. They’re available for account, case, contact, lead, and opportunity pages and on the global publisher layout in the Salesforce mobile app. You can use them to set up quick actions for mobile users with little effort.
Map Salesforce External Object Fields to Snowflake Data Types: External object fields can be mapped to Snowflake data table columns with scalar types such as strings and numbers. External object fields can’t be mapped to columns containing complex or semi-structured data types such as a variant, object, or array.
Manage Qualifiers for Salesforce Connect Adapter SQL for Snowflake: Tables and databases in Snowflake contain the metadata definitions for the underlying source data schema. To be able to make queries to Snowflake, use qualifiers to specify the key columns that identify records in the Snowflake data source.
Client-Driven and Server-Driven Paging in the Salesforce Connect SQL Adapter for Snowflake: It’s common for Salesforce Connect queries of external data to have a large result set that’s broken into smaller batches or pages. You decide whether to have the paging behavior controlled by the external system (server-driven) or by the SQL adapter for Salesforce Connect (client-driven).
Set Up Salesforce Connect SQL Adapter for Snowflake: Provide users easy access to data stored in Snowflake so that they can build custom applications that combine the power of the Salesforce and Snowflake platforms.
Standard Action Overrides: For standard actions, such as Delete, Edit, List, New, Tab, and View, you can provide a custom user interface for the action, called an action override. Use action overrides when your business model requires a more customized user experience than the Salesforce standard page provides.
Standard Profiles: Every Salesforce org includes standard profiles that you can assign to users. Edits to standard profiles are limited to certain settings.
Authorize a Deployment Connection: Authorize inbound changes so that another Salesforce org can send change sets to the org you are logged into.
Create an Outbound Change Set: An outbound change set is a change you send from the Salesforce org you are logged into to another org.
Test Your Changes: Testing is key to the success of your application, particularly if you deploy your application to customers. If you validate that your application works as expected with no unexpected behavior, your customers are going to trust you more.
Tips for Working with Activity Fields in Formulas: Get tips for creating accurate activity formulas by distinguishing between tasks and events. Plus, find guidance on handling activity-specific fields and correctly referencing polymorphic relationships like Who and What.
Tips for Working with Date and Date/Time Formulas: Use these tips to avoid unexpected results in Date and Date/Time calculations. Learn about data type compatibility, calculating durations and intervals, handling fractional day values, and staying within valid year ranges.
Tips for Using Hyperlinks in Formulas: Get tips on using formula fields that contain a HYPERLINK function. Learn how to control link target behavior and predict how relative and external links open. Plus, find guidance on supported URL protocols in Lightning Experience.
Tips for Using Merge Fields in Formulas: Get tips for working with merge fields in your formulas. Learn how to reference cross-object merge fields, work with person and business accounts, and more. Plus, find guidance on using a special merge field to reference the unique identifier for your Salesforce org in a formula.
Tips for Working with Numbers in Formulas: Get tips for using number fields in your formulas. Learn how to work with percent fields using decimal values and how to reference auto-number fields as text. Plus, find guidance on mixing numbers with percentages and currencies, and understanding output limits and rounding behavior.
Tips for Working with Text in Formulas: Get tips for working with text in formulas. Find guidance on using quotation marks to insert or concatenate text, escaping special characters with backslashes, and more.
Tips for Building Formulas: Extend your Salesforce data with powerful formula logic. Access a collection of tips for using specific data types in your formulas, including dates, numbers, text, picklists, and record types.
Work with Translation Files: Translate metadata labels or data translation text, or review existing translations, with XML Localization Interchange File Format (.xlf) or Salesforce Translation Format (.stf) files.
Custom Branding for Trialforce: If you use Trialforce, you can optionally set up a branded login site and emails. By applying your company’s look and feel to a login site and emails, customers are immersed in your brand from signup to log in. Apply custom branding only for non-CRM solutions. Don’t apply it to solutions that extend Salesforce CRM and require standard objects, such as Leads, Opportunities, and Cases.
Create a Branded Login Page: Customers typically log in to your app using the traditional login.salesforce.com site. A branded login page enables you to customize this domain and parts of this login page so you can provide a branded experience for your customers.
Trialforce Branded Email Sets: Trialforce Email Branding allows you to modify system-generated emails so that they appear to come from your company rather than from Salesforce. Trialforce Email Branding only applies to users who sign up for your application through Trialforce.
Choose a Trialforce Login Site Domain: Choose a subdomain for customers to log in to your application. Usually, the subdomain is the name of your company.
Trialforce Branded Login Site: Use the Trialforce Branded Login Site page to create, publish, and edit a login page that has your company's look and feel.
Sign-Ups Using the API: Use API calls to the SignupRequest object to create sign-ups for prospective customers.
Which Trial Method Is Right for My AppExchange Solution?: The first step to offering trials of your AppExchange solution is to pick a delivery method. You can provide trials on your AppExchange listing using test drives or Trialforce orgs, or you can provide trials on your website using SignupRequest API. Learn about the differences between trial methods, and decide which options work best for your business.
Troubleshoot Deployment Failures: Review these common issues and learn how to fix them. If you need help, contact your Salesforce admin.
Troubleshoot DevOps Testing Issues: Here are some tips on troubleshooting common issues encountered while using DevOps Testing. If needed, get help from your test manager or Salesforce system administrator to resolve these issues.
Troubleshoot Missing Picklist Values: If you add a new picklist value but it doesn't appear when users view or edit records, there are several configuration issues to consider. Review the most common causes and solutions for this type of problem. This topic covers inactive values, record type or business process assignments, field dependencies, and field-level security.
Add or Edit Picklist Values: Add new values or rename existing values in a custom picklist from the fields area of an object. If the picklist uses a global picklist value set, you can change its values only by editing the global value set. Your changes affect all picklists that inherit their values from that global value set.
Find Examples of Advanced Formulas: Review sample formulas for sales, service, financial, employee-services, and integration scenarios. Examples cover commissions and discounts, cross-object references, date and time calculations, image links, data completeness, and more. Adapt the formulas to your fields and business requirements.
Sample Account Media Service Formulas: Create formula links to web and news services, such as Bloomberg, Google, or Yahoo, based on account names or financial ticker symbols.
Sample Account Management Formulas: Rate an account, assign sales regions based on billing state, and track the age of active contracts.
Sample Case Management Formulas: Create autodial links, categorize cases by age, measure data completeness, and suggest agent prompts or offers based on purchase and support information.
Sample Commission Calculations Formulas: Calculate commissions, assign rates by deal size, identify commissions that meet a threshold, and return the highest asset commission.
Sample Contact Management Formulas: Display account details on contact pages, create profile and website links, assign contact identifiers and priorities, and format addresses and phone numbers.
Sample Expense Tracking Formulas: Create identifiers from trip and expense information and calculate mileage reimbursement at a set rate per mile.
Sample Financial Calculations Formulas: Calculate compound interest, consultant costs, gross margin, and contract payments. Other examples supply missing payment due dates and identify overdue unpaid payments.
Sample Image Link Formulas: Visualize case priority, case age, project status, ratings, and scores with images such as flags, colored indicators, star ratings, and proportional bars.
Sample Integration Link Formulas: Create links that connect records to external systems for API integrations, carrier shipment tracking (FedEx, UPS, or DHL), and Skype auto-dialing. Review session-context restrictions and picklist-driven links.
Sample Lead Management Formulas: Track how long leads have been open, measure lead data completeness, convert lead numbers for calculations, and distribute leads or cases across queues.
Sample Opportunity Management Formulas: Calculate opportunity revenue, costs, pricing, commissions, shipping, and contract value. Other examples categorize opportunities, measure data completeness, format revenue, and link to stage-specific sales documents.
Sample Pricing Formulas: Calculate a total amount from unit price and quantity, and derive a per-user price from total license revenue.
User Fields: The fields that comprise the Personal Information and other personal settings pages describe a user.
Public and Personal Groups: A group consists of a set of users. A group can contain individual users, other groups, or the users in a particular role or territory. It can also contain the users in a particular role or territory plus all the users below that role or territory in the hierarchy.
Public Group Considerations: For organizations with a large number of users, consider these tips when creating public groups to optimize performance.
Role Fields: The fields that comprise a role entry have specific purposes. Refer to this table for descriptions of each field and how it functions in a role.
View a User’s Access Summary: To make managing permissions and troubleshooting access easier, in the User Access Summary, you can see a consolidated view of a user’s key details and assigned permissions and tabs. You can also manage the user’s assigned permission sets, permission set groups, public groups, and queues.
Guidelines for Adding Users: Understand important options for adding users. Learn what to communicate to users about passwords and logging in.
Add Multiple Users: You can quickly add up to 10 users at a time to your organization. Your Salesforce edition determines the maximum number of users that you can add.
Create Contactless Users: Create users without contact information to reduce the overhead of managing customers and partners. You can add contacts later if you decide that you want them, like when you upgrade to a more full-featured community license. You can add contactless users to new or existing Experience Cloud sites.
Downgrade Experience Cloud Site Users with Community Licenses to Contactless Users: You can convert Experience Cloud site users with community licenses to contactless users. By converting site users, you can expand your site without adding to the cost. For example, you can downgrade inactive or unqualified users and then upgrade them to full-featured site users later on. You can downgrade users from Setup and through the API.
Enable Contactless Users: Enable the contactless user feature for your org to reduce the overhead of managing customers and partners by creating users without contact information. Without contacts, you don’t have to worry about keeping user and contact records in sync. For example, if you maintain a user directory for identity purposes, no contact information is required.
Manage Contactless Users: By default, when Salesforce creates a user record for a customer or partner, it adds the user’s contact information. But if your implementation doesn’t require contact information for customers or partners, consider going contactless to reduce the overhead of managing these types of users. Without contacts, you don’t have to worry about keeping user and contact records in sync. For example, if you maintain a user directory for identity purposes, no contact information is required.
Upgrade a Contactless User to a Community License: Upgrade contactless users with an External Identity license to a community license to give them more access to your Experience Cloud sites. To upgrade a contactless user, you must first assign the user a contact.
Create and Edit Profile List Views: If enhanced profile list views are enabled for your organization, you can create profile list views to view a set of profiles with the fields that you choose. For example, you can create a list view of all profiles with Modify All Data enabled.
Enable User Self-Deactivation: Let external Experience Cloud site and Chatter users deactivate their own accounts. The results are identical to an administrator-initiated deactivation.
Restrict User Email Domains: You can define an allowlist to restrict the email domains allowed in a user’s Email field.
Enable User Access Policies: User access policies allow you to automate and migrate your users’ assignments to access mechanisms, including managed package licenses, permission sets, and permission set licenses.
Enable the Email Domain Allowlist: Enable the Email Domain Allowlist Setup page, where you can restrict the email domains allowed in a user’s Email field.
Available Feature Licenses: Assign one or more of these additional feature licenses to users so that they can access features not included in their user license.
Freeze or Unfreeze User Accounts: In some cases, you can’t immediately deactivate an account, such as when a user is selected in a custom hierarchy field. To prevent users from logging in to your organization while you perform the steps to deactivate them, you can freeze user accounts.
Group Member Types: Many types of groups are available for various internal and external users.
View Group Lists: View and edit information about a group and its members.
Edit Multiple Profiles with Profile List Views: If enhanced profile list views are enabled for your organization, you can change permissions in up to 200 profiles directly from the list view, without accessing individual profile pages.
When to Use an Internal or External License: The Salesforce platform supports multiple use cases and stakeholders, such as employees, partners, brokers, and end customers. Salesforce has built purpose-driven applications and licenses to account for the differences in features, user experiences, sharing requirements, data security, and the needs of various roles. Learn about the various use cases and available licenses to make informed license purchasing decisions.
Billing Considerations for Platform Login and Dev Credit: Usage of certain Platform Login and Dev Credit features impacts credit consumption. To monitor your usage in these Platform Login and Dev Credit usage categories, access your org’s Digital Wallet. For more information on how usage is billed, refer to your contract or contact your account executive.
Enable the Licensing Events Feature: Control when licensing events occur by specifying peak business hours and heavy traffic periods to optimize licensing event timing.
Standard User Licenses: Standard user licenses provide internal users access to Salesforce. These licenses include the Salesforce and Platform user licenses. Salesforce user licenses are for users who need full access to Salesforce CRM objects and AppExchange apps. Platform user licenses are for users who need access to custom apps but don’t need full access to standard CRM objects.
Chatter User Licenses: All standard Salesforce licenses allow free Chatter access for everyone in your organization. Salesforce also offers Chatter-specific licenses: Chatter External, Chatter Free, and Chatter Only (also known as Chatter Plus). The Chatter Only license is available for purchase only by existing Chatter Plus customers. For new customers, the Lightning Platform Starter license is a step up from Chatter Only, giving your users access to a more robust set of features.
Experience Cloud User Licenses: The following licenses are used for external users: Customer Community, Customer Community Plus, Partner Community, External Apps, External Identity, and Channel Account.
Features Available with Lightning Platform Starter, Lightning Platform Plus, and Salesforce Platform Login Licenses: Lightning Platform Starter and Lightning Platform Plus licenses contain the Salesforce Platform user license. The Salesforce Platform License and Salesforce Platform Login licenses have access to the Salesforce Platform permission set. The Salesforce Platform permission set gives access to user permissions with AI capabilities. You can also enable users access to the Lightning Console app. This table shows which features are available to users with the Lightning Platform Starter, Lightning Platform Plus, and Salesforce Platform Login licenses.
Database.com User Licenses: User licenses designed for users who need to administer Database.com and who need Database.com access to data stored in Database.com.
External Identity License Details: Salesforce Customer Identity is available when you purchase the External Identity license. You can purchase the External Identity license in blocks of active users. These users are typically consumers of your business, such as customers, purchasers, patients, partners, and dealers.
Update a User's License: You can move a user to a new license from the user’s profile. Before moving a user to another license, set up a profile for the new license type you’re moving the user to.
User License Type Options: Salesforce offers many types of user licenses to support different business needs. The appropriate license for a user depends on the functionality they need and whether they're an internal employee or external user. To make informed licensing decisions and find the right fit for your users, review the user license type options that are available.
Channel Account Licenses: The Channel Account license is available for Experience Cloud sites and has the same permission and feature access as the Partner Community license. Unlike login or member-based licenses, Channel Account licenses are priced per partner account. Partners then open up access to users.
Authenticated Website User Licenses: Platform portal users have the Authenticated Website license, which is designed to be used with Salesforce Sites. It gives named sites users unlimited logins to your Platform Portal to access customer support information.
Legacy Portal Licenses: The following licenses are used in portals: Gold Partner, Customer Portal Manager Standard, and Customer Portal Manager Custom. These licenses are no longer sold because Partner Portals and Customer Portals are no longer available for orgs that aren’t currently using them. Instead, use Experience Cloud sites.
Unmetered Platform Developer and Admin AI User Permission Set License: The Unmetered Platform Developer and Admin AI User permission set license provides access to unmetered Agentforce Vibes and certain AI-powered developer and admin tools. Unmetered usage doesn’t consume Flex credits.
Assign the Unified Employee License: To assign the Unified Employee license to employee (internal) users, complete each step provided here. For employee users who access employee agents in Slack, complete the extra Slack configuration steps. For employee users who access HR Service or IT Services, follow the Service Cloud configuration steps linked at the end of this topic.
Salesforce Platform Login License Details: The Salesforce Platform Login license is for users who need only occasional access to custom apps and to the same features and functionality as the Salesforce Platform license.
Unified Employee License Details: The Unified Employee license gives employee (internal) users access to Experience Cloud sites and employee agents in Slack and other Salesforce products. This license doesn’t provide employee users access to Lightning Experience in your Salesforce org. To grant your users access to Lightning Experience, assign them the Salesforce Platform or Salesforce user license.
View Your Org’s User Licenses: You can view your active licenses through either the Company Information page in Setup, or the Digital Wallet License Utilization tab.
Licenses Overview: To enable specific Salesforce functionality for your users, you must choose one user license for each user. To enable more functionality, you can assign permission set licenses and feature licenses to your users or purchase usage-based entitlements for your organization.
View Your Org’s User Licenses in Digital Wallet: The Digital Wallet License Utilization tab directly maps user and permission set licenses to the specific products that you purchased. It also provides real-time license information to help you monitor usage and maximize the value of your investment.
View Your Org’s User Licenses in Setup: From the Company Info page in Setup, view the licenses that your company has purchased. Understand which licenses are assigned to users and how many are remaining. This page provides a simple, point-in-time list of licenses and entitlements.
Licensing Events Overview: Provisioning new licenses and similar licensing events can delay your org’s ability to process other requests. The Licensing Events feature puts you in control of when licensing events occur. You can specify your busiest hours and dates as blockout periods so that licensing events occur outside these time frames. Additionally, if a licensing request comes in during a blockout period, Salesforce notifies you and you can override the blockout.
Look Up Licensing Event History in Setup Audit Trail: When a licensing event is triggered for your org, a corresponding entry is added to the Setup Audit Trail page. With Licensing Events enabled, standard entitlement delivery continues as usual, but an additional row is recorded for any license application—whether manual or occurring outside designated blockout periods.
Override Blockout Hours or Dates: If a licensing request comes in during a blockout period, Salesforce notifies you and you can override the blockout. For example, if you designate blockout hours from 9:00 AM to 5:00 PM, Salesforce downloads events during this time but doesn’t apply them until the blockout period ends. If you want to apply an event at 2:00 PM, you can override the blockout period.
Set Blockout Hours and Blockout Dates: After you enable the feature, you can specify blockout hours and blockout dates. You can set hours, dates, or both. You can change these settings or opt out at any time.
Manage Users and Data Access: One of the most important administrative tasks is setting up and keeping your users up to date with the permissions and access that they require to perform their everyday tasks. Salesforce provides a variety of features and tools so that you can customize your data access setup for internal and external users.
Manage Personal User Information Visibility for External Users: Protect your external users' data by concealing personal information fields from other external users. To meet your business's security needs, modify which user fields are classified as personal information and hidden from view on Experience Cloud sites.
Set Up Record Access for Your Users: As part of your data management setup, configure the access that your users have to records that they don’t own through organization-wide defaults, the role hierarchy, sharing rules, manual sharing, and other features. Sharing settings respect the object permissions that you configure for your users using permission sets.
User Management Administration: As a Salesforce administrator, you manage users in your org. Besides creating and assigning users, user management includes working with permissions and licenses, delegating users, and more.
Manage Users: In Salesforce, each user is uniquely identified with a username, password, and profile. You can have internal users, such as employees, who log in to Salesforce. You can also have external users who log in to Experience Cloud sites and guest users who don’t have login credentials.
User Management Settings: Manage org-wide user settings to improve user experience and increase org security.
Permission Dependencies and Alignment: Some object and user (app and system) permissions are dependent on each other to make sure that assigned users have the correct access to related data and tasks. When needed, Salesforce automatically enables dependent permissions in profiles and permission sets to grant assigned users required object and feature access.
Enable Enhanced Permission Set Component Views: When you have large numbers of Apex class assignments for permission sets, enable a paginated result set, standard filtering, and sorting to work more efficiently.
Permission Set Licenses: Permission set licenses entitle users to access additional features not included in their assigned user license. Users can be assigned any number of permission set licenses.
Remove a Permission Set License from a User: First remove or modify the relevant assigned permission sets that require the license, and then remove the assigned permission set license. This unassignment happens automatically in most scenarios, but you can also remove permission set licenses manually if needed.
Configure Enhanced Personal Information Management Using Compliance Categorization: Enhanced Personal Information Management conceals personal information fields from authenticated external users on Experience Cloud sites. If your org enabled this feature before Spring '22, add PII as the Compliance Categorization value on user fields to control which fields are hidden.
Personal User Information Considerations: Keep these considerations in mind as you configure personal user information settings for external users by using Enhanced Personal Information Management.
Configure Enhanced Personal Information Management Using Field Sets: Enhanced Personal Information Management conceals personal information fields from authenticated external users on Experience Cloud sites. If your org enabled this feature in Spring '22 or later, use the PersonalInfo_EPIM field set to control which user fields are hidden.
Configure Independent Guest Field Masking: Use field sets to control which user fields guest users can see separately from other external users, such as portal users. With Independent Guest Field Masking, guest users can't see the fields listed in the Guest_PersonalInfo_EPIM field set.
Personal User Information Policies and Timelines: To protect your external users’ data, Salesforce introduced security settings that let you control personal user information visibility. Use this topic as a starting point to understand all the security improvements and updates, including timelines for enforcement and how to prepare for the changes.
Enable the Enhanced Profile User Interface: The enhanced profile user interface provides a streamlined experience for managing profiles. You can easily navigate, search, and modify settings for a profile. Your Salesforce org can use one profile user interface at a time.
Create or Clone Profiles: Create custom profiles using the API, or clone existing profiles and customize them to fit your business’s needs.
Enable Custom Permissions in Profiles: Custom permissions give you a way to provide access to custom processes or apps. After you’ve created a custom permission and associated it with a process or app, you can enable the permission in profiles.
Enable Enhanced Profile List Views: Enhanced lists give you the ability to quickly view, customize, and edit list data to speed up your daily productivity.
App and System Settings in the Enhanced Profile User Interface: In the enhanced profile user interface, administrators can easily navigate, search, and modify settings for a single profile. Permissions and settings are organized into pages under app and system categories, which reflect the rights users need to administer and use app and system resources.
Search in the Enhanced Profile User Interface: To locate an object, tab, permission, or setting name on a profile page, type at least three consecutive letters in the Find Settings... box. As you type, suggestions for results that match your search terms appear in a list. Click an item in the list to go to its settings page.
Field Permissions: Field permissions, or field-level security, lets you specify whether users can view or edit each field for an object.
Object Permissions: Object permissions specify the base-level access users have to create, read, edit, and delete records for each object.
View and Edit Password Policies in Profiles: To ensure that the appropriate level of password security is used for your organization, specify password requirements with Password Policies settings for users assigned to a profile. Profile Password Policies settings override the organization-wide Password Policies for that profile’s users. If you don’t set Password Policies on a profile, the organization-wide Password Policies apply. New profile Password Policies take effect for existing profile users when they reset their passwords.
Password Policy Fields in Profiles: Specify password requirements with Password Policies settings. Understand how each field impacts a profile’s password requirements.
Edit Session Settings in Profiles: You can control session settings on a user profile basis. If you don’t configure the profile session settings, the org’s session settings apply to users of the profile. When set, the profile settings override the org-wide settings.
Configure Default Settings in Profiles: Configure assigned apps, record types, page layouts, and other default settings in profiles so that assigned users can see the data and apps required to complete their work.
“View All” and “Modify All” Permissions Overview: The “View All” and “Modify All” permissions ignore sharing rules and settings, allowing administrators to grant access to records associated with a given object across the organization. “View All Records” and “Modify All Records” can be better alternatives to the “View All Data” and “Modify All Data” permissions.
Restrict Permissions Cloning in Profiles: Use the Restricted Profile Cloning option to ensure that only permissions accessible to your org are enabled when you clone profiles. If you don't enable this setting, all permissions currently enabled in the source profile are also enabled for the cloned profile, even if your org can't currently access them.
Let Users Scramble Their User Data: When users no longer want their personal data recognized in Salesforce, you can permanently scramble the data with the System.UserManagement.obfuscateUser Apex method. However, when you invoke the method for a user, the data becomes anonymous, and you can never recover it. As an extra precaution, you can’t use the method until you enable Scramble Specific Users’ Data for your org.
Administrators and Separation of Duties: Separating duties limits the power of any one person or entity so that you can help prevent a single point of failure. For example, you can have two or more administrators who have responsibilities for administering different portions of your org. If you have only one administrator, consider assigning a backup person to the role. You can give the backup person the same access that your primary administrator has.
Feature Licenses Overview: A feature license entitles a user to access an additional feature that isn’t included with his or her user license, such as Marketing or WDC. Users can be assigned any number of feature licenses.
User Licenses: Every user requires a user license to access Salesforce. Depending on your product, edition, and add-ons, there are various types of user licenses available. See how user licenses work to ensure you’re allocating them appropriately and effectively.
Usage-Based Entitlements: A usage-based entitlement is a limited resource that your organization can use on a periodic basis. For example, the allowed number of monthly logins to a Partner Community is a usage-based entitlement.
Unlock Users: Users can be locked out of their org when they enter incorrect login credentials too many times. Unlock users to restore their access.
Usage-Based Entitlement Fields: The Usage-Based Entitlements related list displays these fields. The fields aren’t editable, and they’re only visible if your Salesforce org is entitled to a resource.
Generate Emails From Records: A merge field is a field you can put in an email template, mail merge template, custom link, or formula to incorporate values from a record. For example, you can place a merge field in an email template so that the greeting includes the recipient's name rather than a generic “Hello!”.
View Which Users Have Access to Your Records in Salesforce Classic: Identify users who have been granted access through sharing. The list includes their access level and an explanation and shows every user who has access that’s greater than the org-wide default settings.
Viewing Which Users Have Access to Your Records in Lightning Experience: When viewing a record, you can view a list of users who have been granted access to the record through sharing. The list includes their access level and an explanation and shows every user who has access that’s greater than the org-wide default settings.
Web Console (Beta): Web Console is a modern, browser-based Integrated Development Environment (IDE) embedded natively within Salesforce. It facilitates an in-context workflow for debugging, editing, and validating technical assets, removing the requirement for external tool integration or context-switching.
Modify Process Automation Settings: Enable or disable features related to flows, processes, workflow rules, and classic approval processes.
Classic Approval Processes: It’s likely that you’re familiar with process automation in the form of workflow rules. Approval processes take automation one step further, letting you specify a sequence of steps that are required to approve a record.
About Claudeforce: Claudeforce is the Salesforce and Anthropic strategic partnership and collaboration between the two companies. Salesforce in Claude (Beta) is a packaged plugin for Claude customers. Use it to connect to your org through a secure Salesforce MCP (Model Context Protocol) connection.
Work With APIs: Salesforce provides programmatic access to your org’s information using simple, powerful, and secure application programming interfaces.
Translation Workbench: Use Translation Workbench to maintain translated values for metadata and data labels in your Salesforce org. Specify languages for translation and assign translators for each language. Manage translated values for any Salesforce supported language. Translators can maintain translations directly through the workbench, or you can export translation files for bulk translation imports.
Export Metadata Translation Files: To easily translate your metadata, create files for your translators that contain your Salesforce org’s translatable metadata. Examples of translatable metadata include custom field labels, report type names, and picklist values.
Export Data Translation Files: If data translation is enabled in your Salesforce org, you can create files for your translators that contain your org’s data translations. Examples of translatable data include B2B Commerce Product names and data stored in custom fields.
Flow Identifiers in Translation Files: In a translation file exported from Translation Workbench, a unique key or trans-unit ID attribute identifies a flow metadata label.
Import Translated Files: Import and update the translations for your Salesforce org’s metadata, such as custom fields, report types, and picklist values. Or import and update data translations, such as Product names. Typically, you export translation files from Salesforce, then send them to outside translators or a translation agency for bulk translation activities. You then import the translated files.
Metadata Translation: When you enable multiple languages in your Salesforce org, Salesforce translates some labels for you, based on the language type. For labels without a default translation, you can localize your apps and custom functionality for any Salesforce supported language through metadata translation.
Manage Your Translations: If your Salesforce org has multiple languages enabled, manage translations so that your global users can use Salesforce in their language.
Bilingual Translation Files: Use the Bilingual file to review translations, edit existing translations, and add translations for labels or data that haven't been translated. One Bilingual file is generated for each translation language.
Translation File IDs and Keys: Each translatable item has a unique identifier in the translation file. In .xlf files, it’s the id within a trans-unit tag. In .stf files, it’s the key. The structure of these identifiers differs for metadata and data translation files.
Outdated and Untranslated Translation Files: Use the Outdated and untranslated file to translate labels or data that need translation. The file includes labels or data changed since the last translation and labels that haven't been translated. One Outdated and untranslated file is generated for each language. When multiple files are generated, they're exported to a .zip file containing a file for each translation language.
Source Translation Files: Use the Source file to translate an organization's labels or data for the first time. The Source file contains labels for all of a Salesforce org's translatable metadata or data in the org's default language.
Cross-Object Field Updates: For all custom objects and some standard objects, you can create actions where a change to a detail record updates a field on the related main record. Cross-object field updates work for custom-to-custom master-detail relationships, custom-to-standard master-detail relationships, and a few standard-to-standard master-detail relationships.
Field Updates That Reevaluate Workflow Rules: If Re-evaluate Workflow Rules After Field Change is enabled for a field update action, and a field update results in a change to the value of the field, Salesforce reevaluates all workflow rules on the object.
Workflow Limits: Salesforce limits the number of total and active rules in your org, the number of time triggers and actions per rule. It also processes a limited number of daily emails and hourly time triggers.
Daily Allocations for Email Alerts: The daily allocation for emails sent through email alerts is 1,000 per standard user license per org—except for free Developer Edition and trial orgs, where the daily workflow email allocation is 15. The overall org allocation is 2,000,000. This allocation applies to emails sent through email alerts in workflow rules, approval processes, flows, processes, or REST API. Single emails sent to external email addresses are also limited, and how those limits are enforced depends on when your org was created.
Field Update Actions: Field update actions let you automatically update a field value. You can associate field updates with workflow rules, approval processes, or entitlement processes.
Outbound Message Actions: An outbound message sends information to a designated endpoint, like an external service. You configure outbound messages from Setup. You must configure the external endpoint and create a listener for the messages using SOAP API. You can associate outbound messages with flows, workflow rules, approval processes, or entitlement processes.
Outbound Message Notifications: You can request that up to 5 users receive a notification listing all outbound messages that have failed for at least 24 hours. A fresh notification is sent every 24 hours until you cancel the request. Failed messages are deleted from the failed outbound messages related list after 7 days. Before they’re removed, you can delete them yourself or request that they be retried again.
Monitor Pending Workflow Actions: When a workflow rule that has time-dependent actions is triggered, use the workflow queue to view pending actions and cancel them if necessary.
Workflow Considerations: Learn the intricacies of workflow rules and workflow actions before you begin working with them.
Set the Criteria for Your Workflow Rule: Get started with creating a workflow rule by selecting the object the rule relates to and configuring its criteria.
Create a Workflow Rule: Automate your organization’s standard process by creating a workflow rule.
Add a Time-Dependent Action to Your Workflow Rule: Time-dependent actions are executed at a specific time, such as 10 days before a record’s close date. When that specific time passes, the workflow rule reevaluates the record to make sure that it still meets the rule criteria. If the record does, the workflow rule executes those actions.
Workflow for the User Object (Beta): You can create workflow rules and actions for the User object. You can, for example, send welcome emails to new employees or sync user data with a third-party service using outbound message actions.
Provide Actions, Buttons, and Links: Buttons and links let users interact with Salesforce data and with external websites and services, such as search engines and online maps. Salesforce includes several standard buttons and links. You can also create custom ones. Actions let users do tasks, such as create records in the Chatter publisher and in the Salesforce app.
Work with Code: This section contains information about the tools and techniques you can use when making changes to your organization by using code.
Global Publisher Layouts: Global publisher layouts determine the global actions that appear in the various Salesforce interfaces. In Salesforce Classic and Lightning Experience, these layouts customize the actions on global pages (like the Home page) and on the Chatter page. Lightning Experience also uses these layouts to populate the Global Actions menu. And in the Salesforce mobile app, these layouts drive the actions that appear in the action bar on the Feed and People pages. Global publisher layouts can include global actions only.
Write Code: Write code using the Apex programming language to add business logic or use the Visualforce markup language to create the user interface. Integrate your application using APIs and authenticate your external applications.
Cross-Org Adapter for Salesforce Connect: Collaborate more effectively and improve processes by connecting the data across your Salesforce orgs. With the cross-org adapter, Salesforce Connect uses Lightning Platform REST API calls to access records in other Salesforce orgs. Nevertheless, setup is quick and easy with point-and-click tools.
API Usage Considerations for Salesforce Connect—Cross-Org Adapter: With the cross-org adapter, Salesforce Connect uses Lightning Platform REST API calls to access records in other Salesforce orgs. Depending on how the external object is accessed, each call counts toward the API usage limits of only the provider org or of both provider and subscriber orgs.
