A Salesforce administrator at a cloud software logistics enterprise is documenting the system process execution flow during lead conversion. When a sales representative converts a qualified lead record in Salesforce, system validation, target record instantiation, field mapping, downstream automation, and lead status updates occur in a strict sequential order. Place the following lead conversion system execution steps in the correct chronological order from first to last.
- 1Lead object validation rules evaluate to verify that pre-conversion criteria and mandatory lead fields are satisfied.
- 2Destination Account and Contact records are created or selected, and an optional Opportunity record is created.
- 3Custom Lead field values are transferred to corresponding mapped fields on the target Account, Contact, and Opportunity records.
- 4Record-triggered flows, workflow rules, and Apex triggers execute on the target Account, Contact, and Opportunity records.
- 5The original Lead record status updates to Converted and the lead record is set to read-only.
Cevap
The correct chronological execution sequence for Salesforce lead conversion is: 1) Lead validation rules evaluate eligibility, 2) Target Account, Contact, and Opportunity records are created or matched, 3) Lead custom field mapping populates data on target records, 4) Record-triggered flows and automations execute on target records, and 5) The original Lead status updates to Converted and becomes read-only.
The correct sequence begins with evaluating validation rules on the Lead object to verify data accuracy prior to conversion. Next, Salesforce creates or links the target Account, Contact, and optional Opportunity records. Custom field mapping then populates data onto those target records. After target fields are populated, record-triggered flows and automations execute on the destination objects. Finally, the original Lead record status updates to Converted and the record becomes read-only.
Adım Adım Çözüm
Anahtar Kavram
Salesforce Lead Conversion Order of Execution
Tahmini Süre:1m 30s