3

Using the Metadata API, you can get CaseSettings. If On-Demand Service is enabled you can use the following. You can query EmailServicesFunction object to see if there is an entry for EmailToCase. If there is then it is enabled. SELECT Id, FunctionName from EmailServicesFunction where FunctionName = 'EmailToCase' You can also query EmailServicesAddress ...


2

The error message Error Occurred: Probably Limit Exceeded or 0 recipients is explained in this help document I'm assuming you have some sort of email alert going out as an action on your process builder. This email alert is trying to send an email, but there's no recipients or the recipient is a user who is inactive.


2

According to Bounce back loop from 'Email-to-Case' creates more than 1000 Cases: Salesforce has set measures to detect an email loop from an external email system. This is set in place to prevent a continual loop that could cause a large amount of erroneous inbound messages into a Salesforce.com organization. The 'Email to Case' looping algorithm looks at ...


1

As far as I can see there is a new default for any org created after Winter'21 (which is the release being deployed by Salesforce). Long story short: I think you cannot change it, if your org is already at Winter'21 release. Check the Email-to-Case documentation for more info: Insert Thread ID in the Email Subject NOTE Any org created after the Winter '21 ...


1

During the insert the record type assignment is missing and the default record type may not have the picklist value that you are trying to insert with, so add the record type assignment- Case newCase = new Case(); ... newCase.RecordTypeId = '{get value from describe call}'; newCase.Close_Code__c = 'test'; insert newCase;


1

The settings are applied before the transaction starts; you can't modify those settings during a trigger. To fix it easily, create a custom field as you described, set it in the before-insert trigger, and then you can create a single rule entry like: Skip Assignment equals True And the Owner would be set to: Keep Owner


1

I'm not sure where, or if, this is documented, but I do know that this is normal behavior. The Contact and Account will not be resolved until the after-insert phase of the trigger process. In fact, the OwnerId field will be "wrong" in the after-insert trigger phase as well, because assignment rules don't run until later. You could use a Process Builder/...


1

To reproduce the error (V47), you need at least 200,000 Contacts with Contact.Email populated and encryption sync'd (I used 225,000 with 10,000 having Contact.Email=null) 2 Contacts with same email address Email-to-case enabled Send email from email address represented on 2 Contacts RESULTS: Contact.Email encrypted Contacts w/ same Email Email-to-...


1

I think the only admin tool that will allow you to accomplish this is a product called Lightning Flow, and there are a few Trailheads that can help you get your feet wet with this product. https://trailhead.salesforce.com/en/content/learn/modules/business_process_automation However, you may want to shy away from what you are asking about or at least think ...


1

I'm not aware of a way to do this with the standard "send email" on case as you have no access to that email before it actually sends out. I've done this type of thing before, but I had a custom lightning component that users used to send emails from cases on which gave me complete control of the email before I sent it out in the code. This obviously adds ...


Only top voted, non community-wiki answers of a minimum length are eligible