Automation
Email Administration
` `
- Create org-wide email addresses
` `
- Setup BCC email for compliance reasons
` `
- Enable email to SFDC that automatically logs email seat from 3rd party email accounts as actives on lead & contact records
` `
- Stop end users from downloading harmful attachments
` `
- Setup default footers for both individual and mass emails
Email Templates:
` `
- Maintain brand consistency
` `
- Save time with several out-of-box email templates
Email Templates can be set up for:
` `
- Web-to-lead
` `
- Web-to-case
` `
- Email-to-case
` `
- Assignment rules
` `
- Escalation rules
` `
- Auto-response rules
` `
- Workflow
` `
- Process
Email Template:
` `
- Text
` `
- HTML
` `
- Custom
` `
- Visualforce
Email Template Folders: My Setting | Email| Email Templates Setup | Communication Templates | Email Templates
Creating an Email Template in 4 steps
` `
-
Choose template type
` `
- Text
` `
- HTML (with letterhead)
` `
- Custom (no letterhead)
` `
- Visualforce
` `
` `
-
Enter Template Information
` `
- Folder Description
` `
- Name
` `
- Specify letterhead
` `
- Choose layout
` `
` `
-
Enter Content
` `
- Return address
` `
- Text
` `
- Merge fields
` `
-
Create text-only version
` `
- If this is blank, the text from the HTML version will be copied over automatically
Process Builder:
` `
- Create processes that execute actions when certain conditions are met
` `
- Add multiple groups of criteria & associate actions with each criterion
` `
- Create immediate & scheduled actions
` `
- Continue a process after a branch by choosing the “Evaluate the text criteria” option instead of “STOP”
` `
- Use versioning to easily track & maintain processes
Workflow tool allows you to automate business process using a visual interface
By default, a criteria node is set up STOP after executing actions
To use the “Evaluate the new criteria option”:
` `
- The Criteria node should include only immediate actions and no scheduled actions
` `
- The next criteria node must be defined
“Evaluate the next criteria” is helpful in process management because multiple actions for an object can be performed in a single process
Use cases for processes:
` `
- Send an email reminder to the account team if a high value opportunity is still open 10 days before the specified close date
` `
- Update all the mailing addresses on all child contacts when a billing address is changed on an account
` `
- Create records and notifications based on stages of an opportunity and schedule follow up tasks that execute based on changes to records
` `
- Create an order record with data in the opportunity stage changes to closed & won
Actions supported in processes
Process builder supports all the same actions as workflow rules:
` `
- Apex: add customized functionality
` `
- Create a record: create a new record
` `
- Email Alert: send an email using an email alert
` `
- Flows: trigger an auto launched flow to automate complex business processes
` `
- Post to Chatter: post the feed of a user, a Chatter group, or the record that started the process
` `
- Quick Actions: use this action to use an object-specific or global action to create a record, update a record, or log a call
` `
- Submit for Approvals: submit a record for approval without requiring you to submit manually
` `
- Update Records: update fields on records or any related records
Considerations for Processes
General:
` `
- Process do not support outbound messages, but the Call Apex action can be used to provide similar functionality
` `
- Actions are executed in the order in which they appear in the process
` `
- Criteria can be reordered in process with drag & drop
` `
- Name and Descriptions can be reused while creating a new process
Scheduled Actions:
` `
- Multiple scheduled action groups are supported for each criteria node
` `
- Scheduled actions cannot be used in processes that evaluate every time a record is created or edited
` `
- Scheduled actions cannot be used when using the “Evaluated Next Criteria” option
` `
- The Paused & Waiting Interviews list displays all pending scheduled actions
` `
- If salesforce executes the scheduled actions of an inactive user who started the process, the process admin receives a fault email with celestials about what happened & how to fix it.
A workflow rule:
` `
- Automates workflows based on an organizations requirements
` `
-
Triggers workflow actions based on criteria:
` `
-
Evaluation criteria Ă Rule Criteria Ă Actions Ă Time Triggers Ă Action (Tasks, Email Alerts, Field Updates, Outbound Messages)
` `
- Evaluation and rule criteria to trigger an action: Rules created after saving records do not trigger for those records retroactively
` `
-
Workflow Actions:
` `
-
Workflow Tasks:
` `
- Can be assigned to a user, role, record owner, record creator, opportunity team role, or account team role
` `
- Are associated with workflow rules for the same type of record
` `
- Shouldn’t be assigned to roles with multiple users
` `
- Can be assigned to multiple users by creating multiple tasks as outcomes of the rule
` `
- Are tracked in activity history and can be reported on
` `
-
Email Alerts:
` `
- Automatically send an email to one or more recipients
` `
- Send a template email to user, role, record owner, record creator, opportunity team role, or account team role
` `
- Can be sent to any email addresses populated in a custom or standard filed on the record
` `
- Auto-generated emails are not automatically added to the activities related list
` `
-
Field updates:
` `
- Automatically change the value of a field
` `
- Can be created for standard or custom objects
` `
- Can be immediate or time-dependent
` `
- Depending on the type of field, can make the value blank or calculate a value based on a formula
` `
- Can retrigger workflow rules
` `
` `
-
Workflow outbound messages
` `
- Send specific information to a designated endpoint
` `
- Send the data in form of an API/SOAP message
` `
- Can be created for Standard or Custom objects
` `
-
Time-based Workflow Criteria
` `
-
Workflow actions can trigger immediately once a record is saved, or they can be time delayed
` `
- Setup | Time-based workflow
-
Automating Leads:

500 new leads per day
Automating Cases (5000 new cases per day)

Preparing for web-to-lead or web-to-case
Create Custom Fields –> Create queues –> Create Email Templates
` `
- Create org-wide Email Addresses
` `
- Create Assignment rules Ă Create auto-response rules
` `
- Create web form
Creating and mapping custom fields: setup | Customize | Leads |Fields | Map Lead fields
Map custom fields to other custom fields of the same data type
Exception:
Lead: Field
Account, Contact, Opportunity Field
Picklist
Text
Text, Text Area
Long Text
Auto #
Text, Text Area
Creating queues: setup | Manage Users | Queues
Creating Assignment Rules:
` `
- Setup | Customize | Leads | Assignment Rules
` `
- Setup | Customize | Cases | Assignment Rules
Creating Auto-Response Rules
` `
- Create Auto-response rules to respond to the web submission of lead or cases
` `
- Only 1 auto-response rule can be active at a time

Enabling web-to-lead and creating the web form permissions have to be “Modify all data”:
Setup | Customize | Self-service | web-to-case
Testing the Form:
` `
- Save the form in HTML (form should already be generated)
` `
- Test
Order of Execution
` `
- Validation Rules
` `
- Assignment Rules
` `
- Auto-Response Rule
` `
- Workflow Rules
` `
- Processes
` `
- Escalation Rules
When using assignment rules to change case ownership, escalation rules are evaluated before assignment rules.
Web-to-case Feature has more template options than web-to-lead