This API is solving some important problems for us and I'd like to ask whether there are any further updates on a possible move to GA? The last update I saw came from @James Ferguson in May this year saying that Salesforce is working on changes to make this API more sustainable.
Thanks!
Hi Neeraja,
If the map button isn’t showing, it might be a browser issue or file mismatch. Try re-uploading the CSV or using another browser. Also, if you’re exploring record mapping visually,
Mango Map might be worth checking out—it works inside Salesforce.In our org, we have set up a specific "do not reply" email for each of our business units. Grants has a do not reply email, Explorers have a do not reply email, etc. We already have "Send Case Notifications from System Address" in Support Settings turned on for awhile now.
So the question is: If we do NOT create a default no reply org-wide email and kept everything as is (we already have assigned no-reply emails for each of our sites) -- will this release impact us // break anything? Or can we continue with the current setup and ignore creating a default no-reply org wide email address?
The no-reply emails that we have set up has the "Purpose" as User Selection vs. default-no reply, so I am not sure if that matters.
Reading the article "email notifications for inbound emails for existing Cases, case comment, case escalation, and case assignment send from your selected default No-Reply address"
What is considered an inbound email? Like if an agent from our Org answers a case, then customer would get an email about that update? and that's when the org-wide email would kick in?
What templates are going to be used if we do not specify any custom templates for Case Assignment , Case Escalation etc? We do have a. Default No-Reply Address but no specific email templates defined yet.
Thank you
Can the folder structure be kept when importing on a different org? #SalesforceLive
Hi all,
I have, in our sandbox, enabled the Release Update called "Disable Ref ID and Transition to New Email Threading Behavior".
I'm very concerned about this coming change since we have a lot of processes running that is using the Thread Id's. For example when we need a mail to be attached to a specific case (e.g. a Bounce message from Salesforce), we just add the Thread ID of the original case and send it into Salesforce and it's correctly connected to the case we want it to be connected to.
We also use the Thread Id's in a link in our autoreplies templates.
I have also tested the Release Update with just replying to a mail from a case and also that does not work. I have an ongoing Support case towards Salesforce Support but I just want to check if anyone here experience the same issues with this Release Update?
Link to the release note:
https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_email_to_case.htm
Br
Madelene Wärja
I have worked on the new feature Email Threading. its working fine.
for that, the email id, which is used in Email to Case is same as from email address in Email Alert and org wide email Address
When will the recording be available to share with others who could not attend today?
@Judson Bruno in the meantime, you can watch the Service and Field Service webcasts here:
Service Cloud https://www.salesforce.com/video/43284053/
Field Service https://www.salesforce.com/video/43284048/
Will the 0 recipients email error in Flow ever mirror the behavior from Workflow? In Workflow, if an email alert has no recipients (i.e., a contact lookup isn't filled in), it just doesn't send; in Flow, we get a fault. #SalesforceLive
This was helpful, in my Task notification flow the original owners are no longer active. I set the entry criteria for the record owner to a formula/text that they must be active to initiate the record trigger flow email notification. This now allows the task to be marked as complete without bumping into the error and only sends out a notification to the original owner if they are still active.
Regardez la vidéo Aperçu administrateur pour avoir un aperçu de la release et des
bonnes pratiques, provenant directement des experts Salesforce.
Après avoir regardé l'Aperçu administrateur, publiez toutes vos questions dans
la communauté, en utilisant le hashtag #SalesforceLive. Des experts en release
Salesforce et d'autres clients comme vous vous répondront.
Regarder la vidéo ici: https://sfdc.co/rrlfr
... et le support de présentation de la release est en français !
Assista ao vÃdeo de Visualização do administrador para ficar sabendo dos destaques da versão e das melhores práticas diretamente dos especialistas da Salesforce.
Depois de assistir à Visualização do administrador, publique na comunidade todas as perguntas que você tiver usando a hashtag #SalesforceLive. Você receberá respostas de especialistas em lançamentos da Salesforce e de outros clientes como você.
Assista ao vÃdeo aqui: https://sfdc.co/RRLPT
Machen Sie sich bereit für den Spring '24 Release!
Sehen Sie sich das Vorschauvideo für Administratoren an und lassen Sie sich die Release-Highlights und Best Practices von Salesforce Experten zeigen.
Nachdem Sie sich das Vorschauvideo für Administratoren angesehen haben, können Sie unter dem Hashtag #SalesforceLive Fragen an die Community richten. Sie erhalten Antworten von Salesforce Release-Experten und anderen Kunden.
Video hier ansehen: https://sfdc.co/RRLDE
