It seems like you're asking about flows with examples, but could you clarify what kind of flows you're referring to? For example:
- Process Flows: Steps in a business process, like onboarding an employee.
- Data Flows: Movement of data through a system, like ETL (Extract, Transform, Load) processes.
- User Flows: The journey a user takes through a website or app, like signing up or making a purchase.
- Programming Flows: Logical sequences in code, such as loops, conditions, or state machines.
- Workflow Automations: Tools like Zapier, Power Automate, or others used to automate tasks.
Salesforce Flows are powerful tools for automating business processes within Salesforce. They allow admins to configure actions, collect data, and interact with the system without needing extensive coding knowledge.
Here are examples of Salesforce Flow types with real-world scenarios:
1. Record-Triggered Flow
Scenario: Automatically update a related record when an Opportunity is closed.
- Use Case: Update the Account’s "Last Closed Date" field when an Opportunity is marked as "Closed Won."
- Flow Steps:
- Trigger: When a record is created or updated on the Opportunity object.
- Conditions: Opportunity Stage = "Closed Won."
- Action: Update the related Account record with the Opportunity’s
Close Date
.
2. Screen Flow
Scenario: Guide customer service reps through a case escalation process.
- Use Case: Prompt users to input additional information for a high-priority case.
- Flow Steps:
- Start: Create a button on the Case page to launch the flow.
- Screen: Ask for details like the escalation reason and expected resolution date.
- Action: Update the Case record with input values and notify the Manager via email.
3. Scheduled-Triggered Flow
Scenario: Send a reminder email for overdue tasks.
- Use Case: Notify users of open Tasks that are due today or earlier.
- Flow Steps:
- Trigger: Run daily at 8:00 AM.
- Get Records: Query open Tasks with a due date before today.
- Action: Send an email notification to the assigned user with Task details.
4. Autolaunched Flow (Invocable)
Scenario: Integrate with external systems to validate customer data.
- Use Case: Validate an email address by sending it to an external API.
- Flow Steps:
- Input Variables: Accept an email address.
- Action: Use an HTTP callout to an external API for validation.
- Output Variables: Return the validation status (valid or invalid).
- Usage: Invoke the flow from Apex or another flow.
5. Loop in Flow
Scenario: Assign open leads equally among users in a sales team.
- Use Case: Distribute leads using a round-robin method.
- Flow Steps:
- Trigger: A record is created or updated on the Lead object.
- Get Records: Retrieve all open Leads.
- Loop: Iterate through the list of leads.
- Assignment: Assign each Lead to the next available sales user in the round-robin list.
- Update Records: Save the updated owner for each Lead.
6. Subflow
Scenario: Use a common subflow for contact verification across multiple flows.
- Use Case: Validate Contact fields (email and phone) and handle errors.
- Flow Steps:
- Create a reusable subflow to check for valid email and phone numbers.
- Integrate the subflow into other flows, like creating a new Lead or updating Account information.
7. Decision Element in Flow
Scenario: Route cases to the appropriate team based on priority and type.
- Use Case: Automatically assign cases to different teams.
- Flow Steps:
- Trigger: A record is created on the Case object.
- Decision: Evaluate conditions:
- High Priority & Technical Issue → Assign to Tech Support.
- High Priority & Billing Issue → Assign to Finance.
- Else → Assign to General Support.
- Action: Update the case owner field with the corresponding team queue.
8. Email Alert in Flow
Scenario: Notify the sales team when a large Opportunity is created.
- Use Case: Send an email to the sales manager if an Opportunity's Amount exceeds $100,000.
- Flow Steps:
- Trigger: A record is created or updated on the Opportunity object.
- Condition: Amount > 100,000.
- Action: Use the "Send Email" action to notify the manager.
9. Platform Event in Flow
Scenario: Trigger notifications to external systems for large orders.
- Use Case: Notify an inventory management system about large sales orders.
- Flow Steps:
- Trigger: A record is created on the Order object.
- Condition: Order Total > 50,000.
- Action: Publish a Platform Event with the order details.
No comments:
Post a Comment