rajendraprasathfern/nexus-lme

Purpose and Platform

This is a Salesforce DX source repository for the Nexus_LME lending-management application. It is deployed into Salesforce, where custom objects, declarative Flows, Apex, Lightning Web Components (LWC), tabs, permissions, and a Lightning app compose the runtime. The supplied README is the stock SFDX guide; the metadata defines the actual product.

User Entry Points

The Lightning application and exposed custom-object tabs provide the principal UI surface:

• force-app/main/default/applications/Nexus_LME.app-meta.xml

• force-app/main/default/tabs/Application__c.tab-meta.xml

• force-app/main/default/tabs/Financial_Account__c.tab-meta.xml

A utility bar is configured for the app at force-app/main/default/flexipages/Nexus_LME_UtilityBar.flexipage-meta.xml. Access is governed through force-app/main/default/permissionsets/Nexus_User.permissionset-meta.xml.

Lending Domain Model

Account is the customer/borrower identity, augmented with business fields such as tier and year started. A loan application belongs to an Account and captures requested amount, term, purpose, and status:

• force-app/main/default/objects/Account/Account.object-meta.xml

• force-app/main/default/objects/Application__c/Application__c.object-meta.xml

• force-app/main/default/objects/Application__c/fields/Account__c.field-meta.xml

Supporting financial disclosures—income, liabilities, and assets—relate to Accounts and/or Applications, forming the underwriting input boundary:

• force-app/main/default/objects/Income__c/Income__c.object-meta.xml

• force-app/main/default/objects/Liability__c/Liability__c.object-meta.xml

• force-app/main/default/objects/Asset__c/Asset__c.object-meta.xml

Application Intake and Financial Capture

The loan-application Flow orchestrates declarative application creation/update. A dynamic LWC provides configurable financial-data entry and is the main custom client-side implementation:

• force-app/main/default/flows/Laon_Application_Flow.flow-meta.xml

• force-app/main/default/lwc/dynamicFinancialsForm/dynamicFinancialsForm.js

• force-app/main/default/lwc/dynamicFinancialsForm/dynamicFinancialsForm.js-meta.xml

The LWC-to-Apex boundary is represented by the financial service and its wrapper/DTO class:

• force-app/main/default/classes/FinancialService.cls

• force-app/main/default/classes/FinancialWrapper.cls

Account Origination and Transactions

Approved/processed applications lead to Financial_Account__c, linked to both borrower Account and Application. It carries loan principal, current balance, rate, disbursement, repayment, fee, and accrued-interest totals:

• force-app/main/default/objects/Financial_Account__c/Financial_Account__c.object-meta.xml

• force-app/main/default/objects/Financial_Account__c/fields/Application__c.field-meta.xml

• force-app/main/default/flows/Financial_Account_Creation_FLow.flow-meta.xml

Transactions are linked to financial accounts and record amount, date, type, and notes. The transaction Flow is the declarative transaction entry/orchestration path:

• force-app/main/default/objects/Transaction__c/Transaction__c.object-meta.xml

• force-app/main/default/objects/Transaction__c/fields/Financial_Account__c.field-meta.xml

• force-app/main/default/flows/Create_Transaction_Flow.flow-meta.xml

Interest Processing

Interest rates can be supplied by centrally stored loan configuration, while account-level cumulative interest and balances are persisted on financial accounts:

• force-app/main/default/objects/Loan_Configuration__c/fields/Default_Interest_Rate__c.field-meta.xml

• force-app/main/default/objects/Financial_Account__c/fields/Interest_Rate__c.field-meta.xml

• force-app/main/default/objects/Financial_Account__c/fields/Total_Interest__c.field-meta.xml

Daily processing is split between a scheduled/declarative job Flow and bulk-capable Apex batch logic:

• force-app/main/default/flows/Daily_Interest_Job.flow-meta.xml

• force-app/main/default/classes/InterestCalculationBatch.cls

This boundary is important: UI and Flows initiate record-oriented business processes; Apex batch execution handles scalable recurring interest calculations within Salesforce governor limits.

Delivery Model

Source follows Salesforce metadata packaging under force-app/main/default, with org/project definitions in sfdx-project.json and scratch-org configuration in config/project-scratch-def.json. Salesforce is the persistence layer, workflow runtime, identity/authorization provider, and job-execution infrastructure; no external integrations are evident in the repository tree.