#Experience Cloud32 debatiendo

@Patricia Cameron you don't need a separate CDN product for the Experience Cloud site. Salesforce CDN is already a setting on the site. Turn that on for the public pages and the static files.

It will not carry 1.5 million logged-in members. Authenticated pages are built for that user, so the CDN mostly serves guests, images, and files. The org still renders the member session.

Headcount on the member list is not the load. Concurrent sessions and page views are. I would not turn 1.5 million names into a license guess.

TeamSite and LiveSite stay outside that CDN. If the content is still served from there, cache it on that side. Salesforce CDN only fronts the Experience Cloud domain.

If most of the portal is login-only, the win is fewer queries per page, not another cache SKU. I don't know of an add-on that changes how authenticated pages are cached. A new build can use LWR, which handles the public pages better than Aura, but it does not cache a logged-in member page as if it were static.

Hi @Kushagra Rajput,

Your direction is right. Here is a simple way to build it.

1. Set up AWS SES first

• Verify your sender email or domain in SES.
• If your SES account is in sandbox mode, you can only send to verified emails, so request production access.
• Create an email template in SES. SendBulkEmail needs a template, even for a simple message.

2. Authentication from Salesforce

Use a

3. The API call

Send a POST request to /v2/email/outbound-bulk-emails (SES v2). One call accepts

4. Use Batch Apex

• Implement Database.Batchable<SObject> and Database.AllowsCallouts. Without AllowsCallouts, the callout fails.
• Run it with a scope of 50, so each execute makes one SES call.

apex

public class BulkEmailBatch implements Database.Batchable<SObject>, Database.AllowsCallouts {
    public Database.QueryLocator start(Database.BatchableContext bc) {
        return Database.getQueryLocator('SELECT Email FROM Contact WHERE Email != null');
    }
    public void execute(Database.BatchableContext bc, List<Contact> scope) {
        List<Object> entries = new List<Object>();
        for (Contact c : scope) {
            entries.add(new Map<String, Object>{
                'Destination' => new Map<String, Object>{ 'ToAddresses' => new List<String>{ c.Email } }
            });
        }
        Map<String, Object> body = new Map<String, Object>{
            'FromEmailAddress' => 'sender@yourdomain.com',
            'DefaultContent' => new Map<String, Object>{
                'Template' => new Map<String, Object>{ 'TemplateName' => 'YourTemplate', 'TemplateData' => '{}' }
            },
            'BulkEmailEntries' => entries
        };
        HttpRequest req = new HttpRequest();
        req.setEndpoint('callout:AWS_SES/v2/email/outbound-bulk-emails');
        req.setMethod('POST');
        req.setHeader('Content-Type', 'application/json');
        req.setBody(JSON.serialize(body));
        HttpResponse res = new Http().send(req);
        // check res.getStatusCode() and log failures
    }
    public void finish(Database.BatchableContext bc) {}
}

Run it with Database.executeBatch(new BulkEmailBatch(), 50);

5. Things to remember

• Check the response for each entry (the API returns a status per email), and log failures.
• Respect your SES sending rate limit.
• Handle bounces and unsubscribes (SES configuration sets with SNS can help).

Hope this helps. Share where you get stuck and I can help further.

@Rahul Kumar

try checking these threads -  

Hi @Vishal Verma

--->>>

how will the Trigger know which other policies the message should link to. But it hints to a solution.

Maybe if the conversation is still open with Support, then also ask them if it is possible to control this from the Salesforce Outlook Add-In which you are currently using. Is there a way to specify more policies (or other entities) to upload the email to? 

Could you please Guide me on this ?

Control User Visibility in Your Experience Cloud Site (p. 240-241 in Experience Cloud documentation) link 

 Change your org’s settings to control your Experience Cloud site’s user visibility for authenticated members and guest users.

 1. From Setup, enter Sharing Settings in the Quick Find box, then select Sharing Settings.

2. Click Edit in the Organization-Wide Defaults area.

 3. Enable Portal User Visibility or Site User Visibility based on your org’s needs. 4. Click Save.  

Note: To view record names in lookup fields and system fields, such as Created By and Last Modified By, select the Require permission to view record Names in lookup fields checkbox. Then enable the View All Lookup Record Name permission in custom profiles or permission sets for users who must see record names in all lookup and system fields, regardless of sharing settings. You can manage user visibility and guest user visibility on a site-by-site basis. 1. From Setup, enter Digital Experiences in the Quick Find box, then select Digital Experiences > All Sites. 2. Click Workspaces for the site you’d like to access. 3. Click Administration > Preferences. 240 Set Up and Manage Experience Cloud Sites Control Which Users Experience Cloud Site Users Can See 4. Select the See other members of this site or Let guest users see other members of this site checkboxes based on your site’s needs. 5. Click Save.

 Note: To see user profile photos for other users in your site, select the See other members of this site or Let guest users see other members of this site checkboxes. User profile photos display in feeds by default.