How srutikarlakshmi26/salesforce-dev-portfolio works
This Salesforce project automatically assigns High, Medium, or Low priority to Leads on insert and update. A before-trigger delegates to a handler, which evaluates each record using ordered revenue and industry rules and sets the custom picklist before the record is saved. The graph separates trigger dispatch, rule evaluation, and Lead schema. Relationships are supported by the README; Apex excerpts were not provided, so implementation details beyond that documentation are not inferred.
Main entry points: LeadTriggerHandler.cls Evaluate records · LeadTrigger.trigger LeadTrigger · Lead.object-meta.xml Lead object · Lead_Priority__c.field-meta.xml Lead priority field
Components 8
Trigger dispatch
- LeadTrigger
force-app/main/default/triggers/LeadTrigger.trigger
Priority rules
- LeadTriggerHandler
force-app/main/default/classes/LeadTriggerHandler.cls - Evaluate records
force-app/main/default/classes/LeadTriggerHandler.cls - Determine priority
force-app/main/default/classes/LeadTriggerHandler.cls
Lead schema
- Lead object
force-app/main/default/objects/Lead/Lead.object-meta.xml - Lead priority field
force-app/main/default/objects/Lead/fields/Lead_Priority__c.field-meta.xml
Other components
- Sales rep
- Salesforce org
Connections 8
- Sales rep → Salesforce org: edits Lead
README.md - Salesforce org → LeadTrigger: invokes before save
README.md - LeadTrigger → LeadTriggerHandler: delegates
README.md - LeadTriggerHandler → Evaluate records: evaluates records
README.md - Evaluate records → Determine priority: gets priority
README.md - Evaluate records → Lead priority field: sets value
README.md - Salesforce org → Lead object: stores Lead
- Lead object → Lead priority field: defines field
README.md