#Salesforce Admin425 utenti parlano di questo argomento

Hi everyone,

I'm working on the Trailhead module Protect Your Data → Create Sharing Rules and am stuck on the validation step.

The challenge instructions say to create the Applicant sharing rule as follows:

• Label: Share Applicants Between Recruiters
• Rule Type: Based on record owner
• Applicant owned by members of: Role: Recruiter
• Share with: Role: Recruiter
• Access Level: Read Only

When I run Check Challenge, I get the error:

I then changed the access level to Read/Write and saved the rule. However, when I checked the challenge again, I received:

I've already:

• Saved and recreated the rule
• Clicked Recalculate in Sharing Settings
• Verified the role is Recruiter
• Confirmed the rule label is Share Applicants Between Recruiters

Has anyone recently completed this module and encountered the same issue? 

Any guidance would be greatly appreciated. Thanks! 

#Trailhead Challenges

Context

We recently experienced an Email-to-Case outage where a mailbox forwarding configuration was updated for a Sandbox request, but the forwarding rule was actually tied to the active Production Email-to-Case process. This unintentionally disrupted Production email routing and prevented incoming emails from being automatically converted into Salesforce Cases until the routing configuration was restored.

As part of our ongoing Email-to-Case enhancement and Hyperforce migration efforts, we would like to understand what contingency options are available to ensure business continuity if email routing or forwarding configurations fail in the future.

Ask

Looking for recommendations and best practices from the community on:

• What backup or failover mechanisms can be implemented for Email-to-Case?
• How can we ensure inbound emails continue to flow into Salesforce if mailbox forwarding fails or is misconfigured?
• Are there monitoring, alerting, or health-check approaches that can proactively identify Email-to-Case routing issues before business users are impacted?
• Has anyone implemented secondary routing addresses, backup mailboxes, middleware, or other resilient architectures for Email-to-Case?
• Any lessons learned or best practices for Hyperforce migrations and Email-to-Case resilience?

We would appreciate insights from teams that have implemented a robust Email-to-Case recovery or failover strategy to minimize service disruption. 

#Salesforce Admin  #Systems Administrator  #Salesforce Developer  #Salesforce_developer  #Email-to-case  #Trailhead    #Sales Cloud  #Service Cloud 

Hi everyone,

I’d like to understand whether Zoom Phone, RingCentral, and Agentforce (including Prompt Builder) can be integrated with or used within Salesforce Experience Cloud.

Specifically, I’m looking for information on the following:

1. Zoom Phone: Can Zoom Phone be integrated with Experience Cloud for making and receiving calls? Are features such as click-to-call, call logging, and CTI supported for community users?
2. RingCentral: Does RingCentral support integration with Experience Cloud? If so, what calling and telephony features are available to external or community users?
3. Agentforce and Prompt Builder: Can Agentforce agents be deployed within an Experience Cloud site? Can prompts created using Prompt Builder be used by community users, and what are the available options and limitations?
4. Licensing requirements: What Salesforce licenses, Experience Cloud licenses, Agentforce licenses, or third-party subscriptions are required to enable these features?
5. Configuration and limitations: Are there any additional setup requirements, supported integration approaches, permissions, or known limitations to consider?

If anyone has implemented these solutions, I’d appreciate details about the recommended approach, licensing costs or requirements, and any practical experience or documentation you can share.

Thanks in advance!