#TrailblazerCommunity토론 중인 항목 189개

As a Technical Architect in Salesforce Services, I get a front-row seat to what's actually possible with agents, before most of it becomes mainstream. 

The biggest shift I'm seeing:

Instead of just surfacing information, they're taking action: updating records, triaging requests, and kicking off processes. That frees people to focus on judgment calls and relationships instead of repetitive steps. 

Working across customer projects, a few patterns keep showing up:

• Start with a narrow, high-value use case. The wins come from agents that do one job well, not ones that try to do everything.
• Data quality is the foundation. An agent is only as good as the data and context behind it, so grounding it in trusted data matters as much as the prompt.
• Guardrails build trust. Clear boundaries and human handoffs help teams adopt agents with confidence.

The most exciting part is how quickly customers go from "what if?" to "it's live." What used to take months of custom build now comes together in weeks. 

I'd love to hear from others:

Good afternoon everyone, how are you? 

I have a question regarding the following scenario: I have a client who is about to implement MC Next and wants to proceed with development in a sandbox. 

In this case, do we need to complete the full MC Next + Data Cloud setup in production first, and then repeat it in the sandbox? Or, once the setup is done in production, will it correctly mirror to the SANDBOX environment? 

Because the scenario I encountered was: the client provided the sandbox environment for us to work in, but while setting up MC Next after activating Data Cloud, I ran into some blockers to proceed with the setup. This raised the question of whether it is necessary to do everything in production first before doing it in the sandbox. 

Thank you ! 

Good afternoon everyone, how are you? 

We have some questions regarding the Repeater Block and its pre-configuration. We saw in a documentation that it was necessary to force a relationship between our Products DMO and the Individual to be able to associate it with the Data Graph, and then personalize our abandoned cart emails. 

The question we have is:  

Is this step of forcing a relationship really necessary? Or do we need a separate Data Graph for each function? Will each Data Graph work as an activation (comparing it to the use of Data Cloud activation to MCE) ? 

Thank you.

Hi Trailblazers, 

Salesforce has introduced Headless Experience Layer (HXL), an interesting addition for building interactive Agentforce experiences.

Instead of showing only text responses, Agentforce can now display interactive cards, tables, and other UI components. 

Key Advantages:

1. Build Once, Use Anywhere: Create one widget and reuse it across supported platforms like Agentforce, ChatGPT, Claude, and Slack.
2. Interactive Responses: Display customer details, records, and other information in a user-friendly format.
3. Less Development Work: No need to rebuild the same UI for every supported platform.
4. Custom Lightning Types: Connect Agentforce action outputs to interactive widgets.
5. Agent Script Integration: Configure action outputs to display widgets in Agentforce.
6. Security: Use Salesforce permissions and sharing rules to control data access.

Example:

Instead of Agentforce displaying customer details as plain text, we can show the information in a structured card. 

My View:

HXL could be very useful for developers building Agentforce solutions across multiple platforms. It's currently in beta, so testing and platform compatibility are important. 

Question:

Do you think HXL will reduce the need for building separate custom UI components for AI-powered Salesforce applications? 

Useful Resources:

• Salesforce HXL Blog
• HXL Documentation
• HXL Playground

#Agentforce #Salesforce Developer #TrailblazerCommunity #Trailhead Challenges #Salesforce

Hey Trailblazers 👋 

Sharing a new update to Salesforce Metadata Navigator: manage queue and group membership directly from the extension. 

You can now:

🔎 Search for queues and groups 

➕ Add members 

➖ Remove members

All in a few clicks, from one place. 

Whether you’re onboarding someone or updating membership after a team change, the goal is simple: reduce repetitive Setup navigation and make everyday admin tasks easier. 

Watch the demo below 👇 

Try the extension: 

If you manage queues and groups regularly, what would make this workflow more useful for you?

#Salesforce Developer #Salesforceadmins #TrailblazerCommunity