🏢 COMPANY BACKGROUND: You’ve just been hired as a Junior Admin for SwiftMoves Ltd, a UK-based logistics company helping small businesses move packages and equipment across the country. The business is growing fast, and users are struggling to enter data correctly and quickly. You’ve been asked to create simple Screen Flows to guide users through data entry — no more messy record creation! This is your first Flow project, and you’ll build 3 beginner-level Screen Flows, one each for Leads, Accounts, and Opportunities. 🔧 YOUR TASK: Create 3 Screen Flows, each on a different object. These should all: - Use Screen Elements for guided input - Save the data to the relevant object - Include basic input validation (e.g., required fields) - Be beginner-friendly and clean 🧩 FLOW 1 – Lead Capture Flow Business Use Case:The Sales team wants a quick way to log new leads during phone calls. Requirements: - Create a Screen Flow on the Lead object - Fields to include: - First Name - Last Name - Company - Email - Lead Source (Dropdown picklist) - After the user enters details, save the record and show a confirmation screen - Make Email a required field 🧩 FLOW 2 – New Business Account Creation Business Use Case:Admins are creating business accounts manually. They want a flow that captures only key fields. Requirements: - Create a Screen Flow on the Account object - Fields to include: - Account Name - Industry (Dropdown) - Type (Customer, Partner, Prospect) - Website (Optional) - After submission, show a screen that says: “Account [Name] has been created!” - Account Name and Type should be required 🧩 FLOW 3 – Opportunity Quick Entry Business Use Case:Sales reps want a simplified form to create an Opportunity from anywhere — they don’t want to see the full layout. Requirements: - Create a Screen Flow on the Opportunity object - Fields to include: - Opportunity Name - Close Date - Stage (Dropdown) - Amount - Related Account (Lookup)

Hey team! 👋 We were meant to kick off Automation in Salesforce during tonight’s session, but there will be no live class this evening. Instead, you’ll use the session time to study this essential Trailhead module on automation. This will prepare you with everything you need to know about: ✅ Workflow Rules (legacy) ✅ Process Builder (legacy) ✅ Flow Builder (the future) ✅ Choosing the right automation tool ✅ Best practices for automation in Salesforce This is a core part of your Admin journey — so don’t skip it. Go through the full trail, take notes, and be ready. We’ll go deeper in the next live session, but this gives you a solid foundation. 🔗 Study the Automation Trail here: https://trailhead.salesforce.com/en/content/learn/trails/automate_business_processes Let’s get you fluent in automation so we can build powerful flows next class 🚀 #Automation #TrailheadSession #PathwayToSalesforce #SelfStudy #AdminSkills

How can you remove a field from required field please?

📍 Company: SecureHire Ltd A recruitment agency based in Manchester that connects tech professionals to contract and permanent jobs across the UK. 🧠 PROJECT BACKGROUND: SecureHire has recently migrated from spreadsheets to Salesforce. The company is growing fast, and leadership has asked YOU, their new Salesforce Admin, to build a secure, scalable data model that matches how the business actually works. Right now, everything is being dumped into the Account and Opportunity objects, and data is being viewed and edited by the wrong people. Leadership’s biggest concern? - Recruiters are seeing salary info they shouldn’t - Sales reps are editing candidates they don’t manage - Managers want reports by industry, recruiter, and region - Finance wants visibility into payments only - Data structure is messy, reporting is unreliable, and data access is out of control 🔧 YOUR TASK (As the Admin): You are required to design and implement a proper Data Model and apply security controls to protect sensitive data and clean up the chaos. 📊DATA MODEL – OBJECTS TO CREATE: 🔹Custom Object 1: Candidate__c Stores individual candidate information Fields to Create: - Full Name (Text) - Email (Email) - Phone (Phone) - Current Role (Text) - Expected Salary (Currency) - Availability Date (Date) - Assigned Recruiter (Lookup to User) - Region (Picklist – North, South, Midlands, Scotland, Remote) 🔹Custom Object 2: Job_Position__c Represents open job roles from client companies Fields to Create: - Job Title (Text) - Department (Picklist) - Salary Range (Currency) - Employment Type (Picklist – Contract, Permanent) - Hiring Manager (Lookup to Contact) - Status (Picklist – Open, Interviewing, Closed) - Linked Account (Lookup to Account) 🔹Custom Object 3: Placement__c Represents a match between a candidate and a job Fields to Create: - Candidate (Lookup to Candidate__c) - Job Position (Lookup to Job_Position__c) - Start Date (Date) - End Date (Date) - Placement Status (Picklist – Interviewing, Offered, Accepted, Rejected) - Recruiter (Lookup to User)

Creating Chatter groups