Automate Business Processes with Salesforce

Introduction

Welcome to Day 6 of my Salesforce Administrator learning journey! Today was all about automation – teaching Salesforce to do repetitive tasks automatically so users can focus on more important work.

I learned how to use Workflow Rules and Process Builder to automate business processes without writing a single line of code. This is one of the most powerful features of Salesforce and a critical skill for any Salesforce Administrator.

What I Built Today

I created automated processes for a housing association's repair management system:

1. Auto-Assign Emergency Repairs (Workflow Rule)

Problem: Emergency repairs were being manually assigned, causing delays.

Solution: Created a Workflow Rule that automatically assigns emergency repairs to the "Emergency Repairs Team" queue as soon as they're logged.

How it works:

Trigger: When a repair request is created
Condition: Priority = "Emergency"
Action: Update Owner field to "Emergency Repairs Team" queue

Impact: Emergency repairs are now assigned instantly, reducing response time.

2. Send Email Alerts for High-Priority Repairs (Workflow Rule)

Problem: Managers weren't being notified of urgent repairs in real-time.

Solution: Created a Workflow Rule that sends an email alert to the repairs manager when an emergency repair is logged.

How it works:

Trigger: When a repair request is created
Condition: Priority = "Emergency"
Action: Send email using custom template with repair details

Impact: Managers are immediately notified and can take action faster.

3. Create Follow-Up Tasks for Overdue Repairs (Workflow Rule)

Problem: Overdue repairs were being forgotten.

Solution: Created a Workflow Rule that automatically creates a high-priority task for the repair owner when a repair becomes overdue.

How it works:

Trigger: When a repair request is created or edited
Condition: Status = "Overdue"
Action: Create task with due date = tomorrow

Impact: Ensures overdue repairs are followed up promptly.

4. Update Tenancy Status When Move-In Date Passes (Process Builder)

Problem: Tenancy records were staying in "Pending" status even after tenants moved in.

Solution: Created a Process Builder flow that automatically updates tenancy status to "Active" when the move-in date is reached.

How it works:

Trigger: When a tenancy record is created or edited
Condition: Move-In Date ≤ Today AND Status = "Pending"
Action: Update Status to "Active"

Impact: Tenancy records are always up-to-date without manual intervention.

5. Update Property Status When Tenancy Ends (Process Builder)

Problem: When a tenancy ended, the property status wasn't being updated, causing confusion about availability.

Solution: Created a Process Builder flow that automatically updates the related property's status to "Available" when a tenancy ends.

How it works:

Trigger: When a tenancy record is edited
Condition: Status changes to "Ended"
Action: Update related Property record's status to "Available"

Impact: Property availability is always accurate, improving operational efficiency.

Key Learning: This demonstrates Process Builder's ability to update related records, which Workflow Rules cannot do.

6. Post to Chatter for High-Priority Repairs (Process Builder)

Problem: The repairs team wasn't being notified in real-time about urgent repairs.

Solution: Created a Process Builder flow that posts to the "Repairs Team" Chatter group when a high-priority repair is logged.

How it works:

Trigger: When a repair request is created
Condition: Priority = "High" OR "Emergency"
Action: Post to Chatter with repair details

Impact: Team collaboration is improved with instant notifications.

Workflow Rules vs. Process Builder: When to Use Each

One of the key lessons today was understanding when to use Workflow Rules vs. Process Builder.

Use Workflow Rules when:

✅ You need simple, single-object automation
✅ You're updating fields on the same record
✅ You're sending email alerts or creating tasks
✅ The logic is straightforward (one condition, one action)

Use Process Builder when:

✅ You need to update related records (parent or child)
✅ You need multiple criteria branches (if-then-else logic)
✅ You need to create new records
✅ You want to post to Chatter
✅ You need to call Apex code

Example:

Workflow Rule: "When Priority = Emergency, send email" ✅
Process Builder: "When Tenancy ends, update the related Property record" ✅

Order of Execution: Why It Matters

Today I learned about Salesforce's Order of Execution – the sequence in which Salesforce processes automation when a record is saved.

Simplified Order:

Validation Rules (fire first)
Workflow Rules (field updates only)
Process Builder
Workflow Rules (email alerts and tasks)

Why this matters:

If a validation rule fails, no automation runs
Workflow field updates happen BEFORE Process Builder
Multiple automations on the same object can cause infinite loops

Best Practice: Use only ONE automation tool per object to avoid conflicts.

Testing My Automation

Testing is critical to ensure automation works as expected. Here's how I tested each automation:

Test 1: Emergency Repair Auto-Assignment

Created a repair request with Priority = "Emergency"
Result: ✅ Owner automatically changed to "Emergency Repairs Team"
Result: ✅ Email alert received in inbox

Test 2: Overdue Repair Task Creation

Created a repair request with Status = "Overdue"
Result: ✅ Task created with subject "Follow up on overdue repair request"
Result: ✅ Task due date = tomorrow

Test 3: Tenancy Status Update

Created a tenancy with Move-In Date = yesterday and Status = "Pending"
Result: ✅ Status automatically changed to "Active"

Test 4: Property Status Update

Changed a tenancy status to "Ended"
Result: ✅ Related property status changed to "Available"

Test 5: Chatter Post

Created a repair request with Priority = "High"
Result: ✅ Chatter post appeared on the record

All tests passed! ✅

Challenges I Faced

Challenge 1: Email Template Merge Fields

Problem: My email template wasn't displaying the property name correctly.

Solution: I learned that merge fields use the format {!Object.Field}. For lookup fields, you need to use {!Object.Lookup_Field__r.Name} to display the related record's name.

Example:

❌ {!HOA_Repair_Request__c.Property__c} (displays ID)
✅ {!HOA_Repair_Request__c.Property__r.Name} (displays property name)

Challenge 2: Process Builder Not Firing

Problem: My Process Builder flow wasn't updating the property status.

Solution: I forgot to activate the process! Process Builder flows must be activated before they run. Also, I learned to check the "Only when a record is updated to meet the criteria" option to prevent the process from firing on every edit.

Challenge 3: Understanding "Immediate" vs. "Scheduled" Actions

Problem: I was confused about when to use immediate vs. scheduled actions.

Solution:

Immediate Actions: Run as soon as the criteria are met (e.g., send email immediately)
Scheduled Actions: Run at a specific time in the future (e.g., send reminder email 3 days before due date)

For today's use cases, I used immediate actions.

Key Takeaways

✅ Automation saves time – What used to take manual effort now happens automatically
✅ Choose the right tool – Workflow Rules for simple tasks, Process Builder for complex processes
✅ Always test – Create test records to verify automation works as expected
✅ Document your automation – Future admins (and future you!) will thank you
✅ Understand order of execution – Prevents conflicts and unexpected behavior
✅ Process Builder can update related records – This is a game-changer for complex processes

Real-World Application

These automation skills directly apply to the Salesforce Administrator role at Incommunities:

Auto-assigning cases based on priority or category
Sending email alerts to managers for urgent issues
Creating tasks for follow-ups
Updating related records (e.g., updating property status when tenancy changes)
Posting to Chatter for team collaboration

Automation is one of the most valuable skills a Salesforce Admin can have because it directly improves efficiency and user satisfaction.

What's Next?

Tomorrow (Day 7), I'll be learning Flow Builder – the modern, more powerful successor to Workflow Rules and Process Builder. Flow Builder can do everything Process Builder can do, plus:

User interaction (screens and forms)
Complex logic (loops, decisions)
Delete records
Integration with external systems

I'm excited to level up my automation skills!

Resources

Thanks for following along! If you're also learning Salesforce, I'd love to hear about your automation experiences. Drop a comment below! 👇

#Salesforce #SalesforceAdmin #Automation #LearningInPublic #Day6

🤖 Day 6: Automating Business Processes in Salesforce

Introduction

What I Built Today

1. Auto-Assign Emergency Repairs (Workflow Rule)

2. Send Email Alerts for High-Priority Repairs (Workflow Rule)

3. Create Follow-Up Tasks for Overdue Repairs (Workflow Rule)

4. Update Tenancy Status When Move-In Date Passes (Process Builder)

5. Update Property Status When Tenancy Ends (Process Builder)

6. Post to Chatter for High-Priority Repairs (Process Builder)