I started this project with what sounded like a small goal: call an Agentforce agent from a Lightning Web Component and show the reply in my own UI. The first API call wasn’t the difficult part. The interesting work began after that: The finished app is a Lightning Web Component backed by an Apex controller…. Continue reading
Salesforce order of execution is the platform’s deterministic save pipeline for an insert, update, or upsert request, but that pipeline has important exceptions, versioned behaviors, and “side-loop” branches that often matter more than the mainline path. In the current Apex Developer Guide, the canonical save sequence begins with loading old and new values, runs before-save… Continue reading
Executive summary Salesforce security is easiest to reason about as three stacked control planes that all must align: identity/session access, object-and-field permissions, and record-level sharing. Authentication and session controls decide who can get in and under what conditions; profiles, permission sets, and permission set groups decide what capabilities a user has on objects and fields;… Continue reading
Executive summary Salesforce asynchronous execution is not a single feature. It is a family of distinct runtime models with very different guarantees around transaction boundaries, ordering, retries, state transfer, user context, observability, and scale. The durable “server-side async” tools are Queueable Apex, Batch Apex, Scheduled Apex, Future methods, and event-driven subscribers such as platform event… Continue reading
Executive Summary Salesforce integrations should be designed from the outside in: start with business timing, user experience, data ownership, failure tolerance, compliance constraints, and expected scale, then choose the narrowest technology that solves that exact problem. Salesforce’s own architecture guidance is explicit on several high-level principles: avoid unnecessary data replication when virtualization is sufficient, favor… Continue reading