New answers tagged

0

Workflow rules are triggered only after Insert/Update DMl OPerations. Hence you cannot send out emails using workflow rules without saving the record first. You can create a VF Page/Lightning Page to send out emails using Apex without saving the record first. send emails through Apex


0

If you have a limited number of special characters to replace... Assuming the field is called Phone__c SUBSTITUTE( SUBSTITUTE( SUBSTITUTE( SUBSTITUTE(Phone__c,'-',NULL), '_',NULL), '(',NULL), ')',NULL) Removes hypen, underscore, left and right parens. Extend to other common characters like period/dot, plus sign, blanks, etc. If I enter (650)555-1212 I ...


1

I recommend removing the LastModifiedDate and LastModifiedById conditions within your Workflow rule criteria. Also, the LastModifiedById should be compared with an ID field i.e. a Salesforce Id of the User record for the MY SFDC USER ID user, instead of comparing it with the name of the user. Remove these from your rule criteria and the workflow should ...


2

Figured out the issue. I didn't test by sending and replying to the Proxy email designated in the email-to-case setting. It also requires the setting of including the thread ID in the subject or body also located in the Email-to-case setting.


1

Since all I wanted to generate was a unique value in a workflow field update, I used text(now()) to generate one. Served the purpose.


0

If you're attempting to use the merge fields in an email template/email alert outside of the approval process, I don't believe it is expected to populate as noted below. https://help.salesforce.com/articleView?id=approvals_considerations_mergefields.htm&type=0 You might be better off considering a report on Approval History (filter those submitted and ...


Top 50 recent answers are included