Platform note
Salesforce Lightning
Salesforce Lightning is the application layer used to extend Salesforce with custom objects, flows, forms, automations, and business applications. It is often encountered where CRM data became the foundation for broader internal processes beyond sales alone.
In many organizations, Lightning-based customizations carry material business logic around customer handling, approvals, service, and internal operations.
What it was typically used for
Organizations used Salesforce Lightning for CRM extensions, approval flows, customer onboarding, service operations, field processes, case handling, partner workflows, and internal applications built on top of Salesforce objects and security models.
Why it still matters in rescue work
Business logic in Salesforce is often fragmented across declarative automation, custom code, object rules, and role-based permissions. Rescue work has to map how the platform behaves in practice, not just how the data model looks in configuration screens.
Artifacts to inspect when extracting business logic
- Objects, fields, and relationships: entity design, ownership, and validation assumptions.
- Flows and process automation: approvals, branching, updates, and notifications.
- Validation rules and formulas: embedded business constraints and derived logic.
- Apex code and triggers: custom processing, integrations, and exception handling.
- Lightning pages and components: user flow, role-specific UI, and screen-level behavior.
- Profiles, permission sets, and sharing rules: access-driven business logic and segregation.