Salesforce

A practical overview of Salesforce core fundamentals: how the multitenant platform works, standard and custom objects, Lookup and Master-Detail relationships, formula fields and validation rules, and the main Flow types. The article also explains the Salesforce security model, from profiles, CRUD/FLS, and record-level sharing to Permission Set Groups and muting, compares Data Loader and the Data Import Wizard, and shows what Headless 360 means for AI agents and least-privilege access.

Jet BI helped a London-based field service company evolve its existing Salesforce Agentforce implementation so the AI agent could support incomplete requests, multi-skill jobs, customer record creation, resource matching and Work Order/Service Appointment creation while keeping employees in control and building on the company’s Salesforce Field Service architecture.

A practical breakdown of Salesforce's AgentExchange security review for developers and ISVs shipping Agentforce actions, topics, and templates. Covers what changed after the 2026 AppExchange-to-AgentExchange merge (agent-type classification, VerifiedCustomerId, prompt injection defenses, random-token enclosures) versus what stayed the same (CRUD/FLS, static analysis, manual pen testing, annual re-review). Explains the $999 per-attempt fee structure, the free false-positive documentation route that avoids paying twice, the four accepted/rejected scanning tools, and the #1 and #3 most common failure reasons (CRUD/FLS enforcement and sharing violations). Ends with a pre-submission checklist and a CTA for a pre-submission code audit with Jet BI.

An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.

This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.

This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.