Salesforce implementation key points
The CRM project first aligns Sales Cloud and Platform licensing boundaries; sandbox Dev/Test/Prod and change sets or CI/CD need to be finalized in the first Sprint.Integrate with ERP/marketing stack to prioritize lead/account master data attribution.MiCount provides Lightning delivery lists and governance templates.
Salesforce · Developer
Apex · Flow · LWC · API · Recommended 3–4 weeks
Implemented business logic and integration on Platform: Apex/Trigger boundaries, Record-Triggered Flow, LWC components, and REST/Bulk API and Named Credential.Can be directly compared to Developer Documentation step by step practice.
learning path
Apex & test
Trigger Handler, Bulk, Test Class coverage and Governor Limits.
LWC & integration
wire service、@AuraEnabled、Named Credential REST。
DevOps
SFDX, Scratch Org, CI run test, Package 2GP concept.
official document comparison
| theme | Learning points | Link |
|---|---|---|
| Apex Developer Guide | Syntax, DML, Async Apex | Apex |
| LWC Guide | Components, events, interacting with Apex | LWC |
| REST API | OAuth, Composite, Bulk 2.0 selection | REST |
| Flow Advanced | Invocable Apex, error handling | Flow |
Arithmetic · Delivery Engineering Specifications
Code quality
- Trigger has only one line of entry; Handler class is testable; SOQL/DML loops are prohibited.
- Test data scripts for each Story: Apex Test + Key Flow.
- Custom Metadata stores configurations to reduce hard-coded IDs.
integrated
- Named Credential + External Credential; the key does not enter Git.
- Bulk synchronization uses Batch Apex or Bulk API; idempotent key design.
- Errors are entered into Platform Event or custom Log objects and can be alerted.
Hands-on Tasks (Acceptance Criteria)
Task: ERP master data synchronization (Account/Product) minimal integration
- Named Credential points to Mock REST; Apex Batch pulls upsert Account.
- Failed lines are written to Integration_Log__c; Dashboard displays 24h number of errors.
- Test Class covers success/failure/batch boundaries; coverage ≥ 85%.
- Deployment documentation: Sandbox steps, Connected App, Profile permission list.
Production release follows the admin change process; see the official Salesforce documentation for Governor Limit.