KernDX

Appearance

Fast Starts ​

Copy-paste-ready guides that get one KernDX capability working in ~30 minutes — no prior framework knowledge needed. Each one is a self-contained walkthrough: the smallest example that runs, then the few options you'll actually reach for. New to KernDX? Start at the top and work down.

Start here — the daily drivers ​

These five are the spine of almost every KernDX project. Learn them first.

  • Trigger Actions — metadata-driven trigger handlers with an audited bypass and a 4-level kill switch, no trigger code to write.
  • Selectors — one FLS-safe, mockable query class per object, with inherited methods and compile-time field safety.
  • DML — USER_MODE-by-default writes with transactional batching, async DML, and dependency ordering.
  • Security — FLS/CRUD enforced by default, with bypasses that are audit-logged with the reason the caller gave.
  • Logging — structured, correlated logging with flood control, the replacement for System.debug.

Build features ​

Reach for these as you build out UI, integrations, and background work.

  • LWC — components built on ComponentBuilder and shared patterns instead of raw LightningElement.
  • Outbound APIs — resilient callouts with retry, circuit breaker, idempotency body-hash, and a dead-letter queue.
  • Inbound APIs — a two-class REST routing pattern with DTO marshalling and replay-safe 409s.
  • Async Processing — chained queueables and batches with correlation IDs threaded through the whole run.
  • Feature Flags — metadata-driven flags that gate behaviour per org or user, no deploy to flip.

Harden ​

Add governance and safety once the feature works.

  • Custom Validations — declarative, Flow-invocable validation rules that return structured errors.
  • Resilience — circuit breakers and retry policies for fragile downstream dependencies.
  • Data Masking — field-level masking for logs and exports, PII and secrets redacted by rule.
  • Test Data — builder-based test factories, no inline DML, and robust across namespaces.

CI & quality ​

Drop the framework's guardrails into your pipeline.

  • Code Scanning — PMD rulesets, an ESLint plugin, and secret scanning that run in your pipeline.
  • E2E Testing — Playwright-first end-to-end tests that run against the deployed org.