I’m looking for an experienced Salesforce Flow developer to build a record-triggered approval flow for discounting. This is not a standard approval process. The company uses a Task-based approval structure that must be automated using Flow. The most important architectural requirement is that: Discounts are not fields. Discounts are separate Opportunity Product Line Items with a negative UnitPrice. The flow must evaluate each negative line item individually. ⸻ How Discounts Work (Key Technical Requirement) In this environment, a discount is represented as its own OpportunityLineItem: • Normal product (positive price) • Discount line item (negative price) • Normal product • Discount line item (negative price) So the flow must trigger on OpportunityLineItem, and only run when: • UnitPrice < 0 (identifies a discount line item), or • A discount % field exists and is > 0 (optional, depending on your implementation) I will provide any field API names as needed. ⸻ Discount Tier Logic (Must Be Implemented Exactly) For each discount line item, create approval Tasks based on the discount tier. Tier 1 – Discount ≤ 10% Create 1 Task: • Sales Manager Tier 2 – Discount > 10% and ≤ 30% Create 2 Tasks: • Sales Manager • CRO Tier 3 – Discount > 30% Create 3 Tasks: • Sales Manager • CRO • CEO User IDs / emails will be placeholders. I will update them later. ⸻ Discount Percentage Calculation Because discount line items are negative-priced products, discount % may be calculated using: ABS(DiscountLineItem.TotalPrice) / SUM(All Positive Line Items) If you prefer, I can supply a pre-calculated percentage field. ⸻ Approval Task Requirements Each created Task must include: • Subject (placeholder text) • Description (placeholder text) • Assigned To = placeholder User ID • Related To = Parent Opportunity • Status = Not Started • Priority = Normal ⸻ Deduplication Logic (Very Important) The deduplication rules must be implemented exactly as follows: 1. Prevent creating duplicate tasks if: • The same approver already has an open/pending approval task • For the same discount line item • In the same tier 2. Allow new tasks if the discount tier increases. Examples: • 12% → 35% (must create the new CRO/CEO tasks) • 8% → 15% (must create CRO task) 3. Do not create new tasks if the discount changes but stays in the same tier. 4. Do not remove or close old tasks. Only add the required new ones. ⸻ Flow Technical Requirements • Record-triggered flow on OpportunityLineItem • Runs on create + update • Decision elements for tier logic • Variables for approver IDs, discount percent, etc. • Get Records only where needed • Error handling / fault paths • Logic must be scalable for changes in tiers/approvers • Must work entirely inside a Developer Sandbox with fake data ⸻ Deliverables 1. Completed record-triggered flow 2. Full documentation explaining: • Flow structure • Where to update approver IDs • How to modify discount tiers 3. Exported metadata (Flow XML / package) 4. A short test demonstration (screenshots or quick video) using fake data