Excellent example for improving performance when using WhatsApp, especially for those with many agents using this tool. Enable subtitles in your language and 1080p quality:
https://www.youtube.com/watch?v=kHTemjVWEG0&list=PLYStC_2TZBSU
I would like to configure password policies for MuleSoft local users, including options to enforce minimum character length, minimum number of uppercase letters, lowercase letters, and special characters. Our Auditors have requested evidence of the password configuration screen to validate it meets company's password policy. so I propose MuleSoft to enhance Anypoint Access Management to cover the custom/user specific password policy settings.
Salesforce users: If you could fix ONE thing in Salesforce tomorrow, what would it be?
Reporting? Automation? Data management? Integrations? Something else?
Drop your biggest Salesforce pain point below. Curious to see what the community is struggling with most.
Since Salesforce recommended to update our integration users from "System Admin" users to the Salesforce Integration user, I have been trying unsuccessfully to get our integration user to trigger Auto-Response emails via Auto-Response Rules when cases are created from Form-to-Case. While this result can be achieved via flow, I did not want to have to manage Case Auto-Response Rules in 2 places ( Flow and Auto-response Rules)
Salesforce Support's final email said that this may be an oversight in the current design of the Salesforce Integration User license and a current product limitation.
I would love to see the permission to trigger the Case Auto-Response rule extend to the Salesforce Integration license so we can use out of the box functionality and not have to build custom processes. Unfortunately I will have to keep using a regular Salesforce License user as my integration user until that is resolved.
If anyone has found a better workaround, I would love to know!
Hey Charlotte,
Web-to-Lead/Web-to-Case auto-response rules not firing when records are created via the REST API (which is likely how your Form-to-Case integration inserts records). This is actually a REST API limitation, not specifically tied to the Salesforce Integration license itself, the SOAP API has an EmailHeader option to explicitly trigger auto-response, but REST API doesn't expose an equivalent.
Two documented workarounds:
Option 1: A Workflow Rule that fires on Case creation and sends the email directly, no code needed, simplest option, but as you noted, means managing logic in two places.
Option 2: A single Apex trigger using Database.DMLOptions to explicitly re-trigger the existing Auto-Response Rules:
```apex
trigger AfterCaseInsert on Case (after insert) {
if (trigger.isAfter && trigger.isInsert) {
List<Case> newlyInsertedCases = [SELECT Id From Case WHERE Id IN :trigger.new];
Database.DMLOptions autoResponseOptions = new Database.DMLOptions();
autoResponseOptions.EmailHeader.triggerAutoResponseEmail = true;
for (Case c : newlyInsertedCases) {
Database.update(c, autoResponseOptions);
}
}
}
```
This re-updates each new Case with a DML option that explicitly triggers your existing Auto-Response Rules, so you keep managing rules in one place (Setup > Auto-Response Rules) instead of duplicating logic in Flow. This runs regardless of which user/license created the record, since it's the DML option itself that flags the update to trigger auto-response, not something dependent on the inserting user's license type.
Worth testing in a sandbox first, and for high case volume, this should be refactored to Queueable/future to avoid governor limit issues on bulk inserts.
Reference:
https://help.salesforce.com/s/articleView?id=000386731&language=en_US&type=1Our GSOC (Global Security Operations Center) is now monitoring Salesforce logs.
For some logs the volume is huge, so we add filters in our SIEM's collect server to filter on the "PolicyID" of Event Monitoring / Transaction Security Policies.
However for the "API Event" big object the PolicyID is always empty leaving us no possibility to filter on that.
Anyone has already encountered the same issue? how did you proceed? would there be a way to filter this directly from the Salesforce API?
Thank you very much beforehand.
Hey guys, thank you very much for both of your answers!!
@Himanshu Shekharactually we already implemented Transaction Security Policy via the TSP accelerator package. However, when we connected our SIEM to Salesforce, our Professional Services told us that the only way to retrieve the Transaction Security Policies events was to take all the Salesforce event logs and then to filter on the PolicyID.
But if I understood properly your answer... you are mentioning a way to take directly into our SIEM Splunk only the TSP alerts. Do you have a link to the resource explaining how we can implement this process?
Thank you very much beforehand
Am I the only one to think this new thing is not ready?
I had a bad experience. First, I had no other choice then use my personnal phone to make it worked. Then, it worked for sometime and block. It was not my phone As I was able to log on other sandbox with the exact same set up with a keypass using my Phone. I had to open a ticket and wait few days before they can unblock me. Fortunately, it was for one of my Sandboxs. But I Can't imagine having the same issue in Production. I fully understand the need, but... it has to work.
I have several users whose preferred browser is Mozilla Firefox, and we've had trouble setting it up. It keeps defaulting to asking for a physical key or using facial recognition, which is useless on a PC. The reverification for exporting reports after a certain time is also a pain.
A platform-native data dictionary
that integrates with Salesforce’s metadata and permissions system as an out-of-the-box feature, rather than a third-party or AI tool which could be more vulnerable to attack. This would provide:
This would reduce manual effort, minimize risk, and improve transparency for admins, data stewards, and auditors.
Allowing users to tag records and find shared tags could replace rigid picklists with a flexible way to categorise Cases. Reporting on these tags across objects would make the data far more useful, especially as Salesforce pushes for AI-ready data. Built on Chatter, this feature may never evolve further—but it’s exactly the kind of lightweight, adaptable system Salesforce should revisit.
We have several reports that users reuse all the time, making edits to the filters to fit their needs. We don't want them saving their edits to the report, but they're finding that after re-authenticating, the report runs with the original filters rather than the edited one. Is there a way around this?
It is a pain, We see the same behavior. We have also noticied that if you create a report and try to export it before even saving it and you have to preform step up auhentication then the report exports blank. I get 2 copies on that initial blank export, then after the step up authentication I export again and it exports normally.
Is there a way in Salesforce Sales Engagement cadences to require reps to update or personalize an email before it can be sent?
We are looking to prevent users from sending cadence emails without first making an update to the email body or subject line. Ideally, we'd like the email step to require some level of personalization before the email can be sent.
Is there a native setting, validation, customization, or best practice that would:
If this is not available out of the box, are there any recommended workarounds or custom solutions?
@Melissa PageSince you cannot hard-stop them natively, the most common fallback in Salesforce architecture is tracking compliance:
A) Managerial Dashboards & Accountability (The Administrative Control - Easy-Peasy.)
Create a custom formula field or Flow on the Task/Email object that checks if the outgoing email body matches the default template text word-for-word.
Build a Sales Engagement Exception Dashboard for sales managers that highlights instances where reps sent emails containing default placeholder text (e.g., leaving [First Name] unmerged or unchanged).
OR
B) Separate Cadence Design (The Process Workaround)
C) Leverage Apex Triggers / Flows via Custom Development