Flow-Based Discount Approval Process Resume Project Example
A Flow-driven discount approval process that routes quote exceptions by margin tier, integrates with CPQ quote lines, notifies approvers in Slack, and extends standard approvals with Apex when thresholds exceed policy.
Free to start · No credit card required
JORDAN KIM
Salesforce Developer
Project
Discount approvals
Policy-aware- Automated discount approvals by margin tier with Flow.
- Integrated CPQ quote lines into approval criteria.
- Extended routing with Apex for multi-region policies.
Why this project is valuable
Revenue workflow signal
Discount approvals connect Salesforce automation to finance policy—a common enterprise need.
Good ATS coverage
Supports Flow, Approval Processes, CPQ, Apex, and business workflow keywords.
Cross-team relevance
Sales, finance, and ops all touch quote exception handling.
Good interview depth
Discuss approval criteria, CPQ field sets, Flow invocations, and escalation paths.
Project overview
A Flow-based discount approval process shows Salesforce developers can automate governed sales workflows without over-customizing.
Quote discounts beyond rep authority launch a screen Flow that captures justification, evaluates margin against CPQ-calculated totals, and submits to the correct approver chain based on tier and region.
On a resume, that gives you ways to describe Flow screen steps, approval process integration, CPQ quote line fields, Apex for regional policy tables, and Slack notifications via Flow actions.
Architecture overview
Project flowCPQ quote exception
Discount beyond threshold on SBQQ quote lines starts the approval Flow.
Screen Flow intake
Reps enter justification and see calculated margin impact before submit.
Policy evaluation
Flow and Apex read margin tiers and regional policy tables.
Approval submission
Standard approval processes route to manager, finance, or VP by tier.
Slack notification
Flow action posts approval requests to approver Slack channels.
Audit trail
Approved discounts write back to CPQ with locked fields and history.
What this project includes
- Screen Flow for discount justification
- CPQ quote line margin evaluation
- Multi-tier approval routing
- Apex regional policy lookup
- Slack notifications via Flow
- Audit-friendly field updates on approval
Tech stack
CPQ plus Flow approvals reflect real B2B Salesforce implementations where declarative automation carries most logic.
Flow
Guides reps through justification and orchestrates approval submission.
Approval Processes
Routes quote exceptions through manager and finance chains.
CPQ
Supplies quote lines, discount fields, and calculated margin for decisions.
Apex
Encapsulates regional policy tables too dynamic for Flow alone.
Slack
Delivers timely approver notifications outside Salesforce.
Salesforce DX
Deploys Flow, Apex, and approval metadata across sandboxes.
Features implemented
Margin-tier routing
Higher discounts require higher approval levels automatically.
CPQ integration
Approvals use live quote totals, not stale Opportunity amounts.
Rep-friendly screens
Screen Flow explains policy before submission.
Regional policies
Apex tables encode market-specific discount limits.
Slack alerts
Approvers act faster with channel notifications.
Locked audit fields
Approved discounts cannot be changed without re-approval.
Resume bullet examples
These bullets show governed sales automation—not generic workflow APIs.
- Built a screen Flow discount approval process integrated with CPQ quote lines that routed exceptions by calculated margin tier.
- Configured multi-step approval processes for manager, finance, and VP thresholds with Slack notifications via Flow actions.
- Implemented Apex policy services for regional discount limits that Flow invoked when standard criteria were insufficient.
- Locked approved discount fields on CPQ quotes and preserved approval history for audit-friendly revenue governance.
Skills demonstrated
This project demonstrates Flow, CPQ, approvals, and Apex extension patterns.
Automation
CPQ
Governance
ATS keywords extracted from this project
Emphasize Flow, CPQ, and approval keywords.
Interview questions based on this project
Approval Flow projects lead to policy and CPQ integration questions.
Why screen Flow for intake?
Reps needed to see margin impact and enter justification before submission; screen Flow kept that UX declarative.
How did CPQ fit in?
Approval criteria read SBQQ quote line discounts and calculated totals rather than static Opportunity fields.
When did Apex help?
Regional policy tables changed frequently; Apex services kept logic maintainable and testable.
How would you improve it?
Add delegation rules for PTO and Einstein prediction of approval likelihood to reduce cycle time.
Common mistakes
Talk about CPQ quotes and approval processes, not REST job trackers.
Margin tiers and audit trails show business governance.
Prefer standard approvals extended by Flow where possible.
Quote line integration distinguishes this from basic Opportunity approvals.
FAQ
Is a discount approval Flow a good Salesforce project?
Yes. It combines Flow, approvals, and CPQ—common in enterprise Salesforce roles.
Do I need CPQ license?
Developer orgs often include CPQ trial; otherwise simulate quote custom objects with discount fields.
Should I mention Slack?
Yes if you wired Flow actions—shows modern notification patterns.
How many bullets should I use?
Two to four bullets on Flow, CPQ integration, and approval tiers.
Turn project details into resume evidence
Use this Flow approval process to strengthen your Salesforce developer resume
Present CPQ, Flow approvals, and recruiter-friendly sales governance with stronger keyword alignment.
Free to start · No credit card required