Certified Platform App Builder Business Logic and Process Automation

Business Logic and Process Automation Detailed Explanation

Business logic and process automation in Salesforce enable you to streamline repetitive tasks, enforce business rules, and enhance data integrity. Salesforce offers various tools for automating processes, from simple point-and-click tools to advanced coding options.

Core Automation Tool 1: Process Builder

What is Process Builder?

• Process Builder is a visual, point-and-click automation tool in Salesforce.
• It helps automate simple to moderately complex processes without writing code.

Features:

1. Multi-Condition Branching:

   • You can define different actions to take based on specific conditions.
   • Example: If an Opportunity is marked as "Closed-Won," notify the Sales Manager; if "Closed-Lost," notify the Account Executive.

2. Actions Supported:

   • Create Records: Automatically create related records.
   • Update Fields: Update fields on the current or related records.
   • Trigger Approval Processes: Start an approval process.
   • Send Notifications: Send emails or use chatter to notify users.

Example Use Case:

• When a new account is created, automatically create a related task to follow up with the account owner within 7 days.

Core Automation Tool 2: Flow Builder

What is Flow Builder?

• Flow Builder is a powerful tool that enables more complex automations than Process Builder.
• It provides a drag-and-drop interface to create flows, which are sequences of actions, logic, and user interactions.

Capabilities:

1. Screen Interactions:

   • Allows user input through custom screens.
   • Example: A flow can collect customer feedback after a case is closed.

2. Database Operations:

   • Query data, update records, and delete records dynamically.
   • Example: Automatically update related Contact records when an Account’s name changes.

3. Advanced Logic:

   • Supports loops, decisions, and variables to handle dynamic scenarios.

Example Use Cases:

• Generate Quotes Automatically:
  • Based on a product selection, create a PDF quote and email it to the customer.
• Bulk-Update Records:
  • Update all open cases for a specific customer when their Account is flagged as "VIP."

Core Automation Tool 3: Workflow Rules

What are Workflow Rules?

• Workflow Rules is one of Salesforce’s legacy automation tools, designed for simple processes.
• It automates tasks based on specific criteria being met.

Actions Supported:

1. Send Emails:
   • Example: Send a welcome email when a new lead is created.
2. Update Field Values:
   • Example: Automatically set the “Priority” field to “High” when a case is flagged as urgent.

Important Note:

• Workflow Rules are being phased out in favor of Process Builder and Flow Builder. It’s better to use these newer tools for any new automation.

Core Automation Tool 4: Validation Rules

What are Validation Rules?

• Validation Rules enforce data quality by ensuring user inputs meet specific criteria before a record is saved.

Features:

• Use formulas to define rules that must be met.
• Display error messages if the criteria aren’t satisfied.

Example Formula:

LEN(Phone) = 10

• Ensures that the "Phone" field contains exactly 10 digits.

Example Use Case:

• Prevent saving a record if the "Discount" field is greater than 50% unless the "Approval Status" is set to “Approved.”

Core Automation Tool 5: Approval Processes

What is an Approval Process?

• Approval Processes automate multi-step approval workflows, ensuring that important records are reviewed by the right people before being finalized.

Features:

1. Define Approval Steps:
   • Specify the sequence of approvers. For example, a manager reviews first, followed by a director.
2. Automate Notifications:
   • Notify approvers when their input is required.

Example Use Case:

• When a discount over 20% is applied to an Opportunity, require approval from the Sales Manager.

Core Automation Tool 6: Triggers (Apex Triggers)

What are Triggers?

• Triggers are pieces of code written in Salesforce’s Apex programming language.
• They enable you to perform complex operations that cannot be achieved using point-and-click tools.

Features:

1. Complex Cross-Object Logic:
   • Example: Automatically update a parent record based on changes in its child records.
2. Advanced Calculations:
   • Perform calculations or handle data across unrelated objects.

Example Use Case:

• When a new product is added to an Opportunity, calculate and update the total discount percentage dynamically.

Note for Beginners:

• Triggers require programming knowledge and are typically used as a last resort when declarative tools (like Flow Builder) cannot fulfill requirements.

Comparison of Automation Tools

Tool	Best For	Skill Level Required	Examples
Process Builder	Simple to moderately complex automations	Beginner to Intermediate	Auto-create tasks, send notifications, update records.
Flow Builder	Complex automations with user interactions	Intermediate	Generate quotes, bulk updates, advanced logic.
Workflow Rules	Basic automations (being phased out)	Beginner	Send emails, update fields.
Validation Rules	Ensuring data quality	Beginner	Prevent invalid data entry, enforce business rules.
Approval Processes	Multi-step approvals	Beginner to Intermediate	Require manager approval for discounts over 20%.
Triggers	Highly complex operations and calculations	Advanced (Apex knowledge)	Cross-object logic, advanced data processing.

Beginner’s Practical Steps

1. Start with Process Builder:
   • Create a process to automate task creation or email notifications.
2. Experiment with Flow Builder:
   • Build a simple flow to update related records or collect user inputs via screens.
3. Try Validation Rules:
   • Set up a validation rule to enforce business rules on key fields.
4. Understand Triggers:
   • Learn the basics of Apex coding (optional for beginners).

Business Logic and Process Automation (Additional Content)

Business Logic and Process Automation in Salesforce allow organizations to streamline operations, enforce business rules, and improve data accuracy.

1. Process Builder

Process Builder is a point-and-click automation tool that enables users to define logic for automating record updates, sending notifications, and invoking approval processes. However, it is being phased out in favor of Flow Builder.

Scheduled Actions in Process Builder

Process Builder supports time-dependent actions, meaning you can schedule actions to occur at a specific time after a record change.

• Example: Follow-Up Email for Leads
  • When a new Lead is created, Process Builder can be configured to send a follow-up email 2 days later if no activity has been logged.
  • This helps automate customer engagement without requiring manual intervention.

Process Builder is Being Replaced by Flow

Salesforce has announced that Process Builder will be retired, and organizations are encouraged to use Flow Builder instead.

• Why? Flow Builder provides greater flexibility, supports more complex automation, and offers better performance and maintainability.
• Best Practice: Avoid creating new automations using Process Builder and instead convert existing ones into Flow Builder where possible.

2. Flow Builder

Flow Builder is the future of automation in Salesforce, offering more power and flexibility than Process Builder or Workflow Rules.

Types of Flows

Flow Builder provides several types of automation flows, each suited for different use cases:

1. Screen Flow

• Requires user interaction (e.g., filling out a form).
• Example: A customer support agent uses a Screen Flow to guide them through logging a new Case.

2. Record-Triggered Flow

• Triggered automatically when a record is created, updated, or deleted.
• Example: When an Opportunity is Closed-Won, the system automatically creates a follow-up Task.

3. Schedule-Triggered Flow

• Executes at a scheduled time (e.g., daily, weekly, or monthly).
• Example: A flow runs every month to identify inactive customers and send them re-engagement emails.

4. Autolaunched Flow

• Called by other automation tools, such as Process Builder, Apex, or another Flow.
• Example: A Flow calculates commission for sales reps and is triggered when a new sale is recorded.

Flow is Replacing Process Builder and Workflow Rules

• Flow Builder can replace nearly all use cases of Process Builder and Workflow Rules.
• Future-Proofing: Since Process Builder and Workflow Rules are being retired, organizations should prioritize learning Flow.

3. Workflow Rules

Workflow Rules were one of Salesforce’s earliest automation tools, but they are now considered legacy.

Workflow Rules vs. Flow

Feature	Workflow Rules	Flow Builder
Supported Actions	Email alerts, field updates, outbound messages, task creation	All Workflow Rule actions + record creation, deletion, loops, and complex logic
Supports Multi-Step Logic?	No	Yes
Scheduled Actions?	Yes	Yes
Being Phased Out?	Yes	No

Best Practice

• Do not create new automations using Workflow Rules.
• Convert existing Workflow Rules into Flows to ensure long-term support.

4. Validation Rules

Validation Rules help prevent incorrect data entry by enforcing business rules at the field level.

Best Practices for Validation Rules

1. Use Validation Rules to Prevent Bad Data

• Instead of fixing data after the fact, use Validation Rules to stop invalid data from being saved in the first place.
• Example: Ensure an Opportunity has a Contact Role before closing the deal.

2. Combine Picklists with Validation Rules

• Validation rules can enforce dependent logic based on picklist values.

• Example:

  ISPICKVAL(Status, "Closed") && ISBLANK(Resolution_Notes__c)
  

  • Ensures that the "Resolution Notes" field is required when a Case is marked as Closed.

When to Use Validation Rules vs. Flow

• Validation Rules: Used to prevent bad data entry.
• Flow: Used to automate processes after data is saved.

5. Approval Processes

Approval Processes automate record approvals, ensuring that critical records are reviewed before being finalized.

Approval Actions

1. Lock the Record

• Prevents users from editing the record while it is waiting for approval.
• Example: A discount request cannot be modified while pending manager approval.

2. Update Fields

• When a record is approved or rejected, its status can be updated automatically.
• Example: When a job application is approved, change the "Application Status" to "Accepted".

3. Auto-Reassign Approvals

• If an approver does not respond within 3 days, the request can be automatically reassigned to a higher-level manager.

Approval Process vs. Flow

• Flow Builder now supports approval processes using Flow.
• Recommendation: New approval workflows should be built using Flow instead of traditional Approval Processes.

6. Apex Triggers

Apex Triggers allow custom logic execution when a record is created, updated, or deleted. While powerful, Salesforce recommends using Flow whenever possible due to its maintainability.

Trigger Events

1. Before Insert / Before Update

• Runs before data is saved to the database.
• Use Case: Populate a default value for a field before a record is created.

2. After Insert / After Update

• Runs after a record is saved.
• Use Case: If a new Order is created, automatically create a related Invoice record.

3. Before Delete / After Delete

• Runs when a record is deleted.
• Use Case: Prevent a record from being deleted if it has related child records.

Trigger vs. Flow

Feature	Apex Triggers	Flow Builder
Requires Coding?	Yes	No
Handles Complex Logic?	Yes	Yes (but limited)
Preferred by Salesforce?	No (Use Flow first)	Yes

Best Practice

• Use Flow first whenever possible.
• Only use Apex Triggers if Flow cannot handle the logic.

Conclusion

The additional concepts covered here enhance our understanding of Business Logic and Process Automation:

1. Process Builder is being phased out, and Flows should be used instead.
2. Flow Builder is now the primary automation tool, with different Flow types for different use cases.
3. Workflow Rules are becoming obsolete, and all new automation should be built in Flow.
4. Validation Rules should be used to prevent bad data entry rather than fixing data afterward.
5. Approval Processes are transitioning to Flow, and manual approval flows should be re-evaluated.
6. Apex Triggers should only be used when Flow cannot meet the requirements.