# Fast Starts

**Copy-paste-ready guides that get one KernDX capability working in about 30 minutes, with 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.

## What do you need to do?

New to KernDX? [From Plain Apex to KernDX](/from-plain-apex-to-kerndx) shows the Apex you already write next
to the KernDX version; then start at the top of the lists below and work down. Deciding whether to use it? Start with [Why KernDX](/strategic-guide-overview).

| I need to | Try it in minutes | Learn it properly | Look up a method |
|---|---|---|---|
| **Query records**<br>SOQL, selectors, counts and totals | [Fast Start: Selectors](/fast-start-selectors) | [Selectors guide](/selectors-guide) | [QRY_Builder](/reference/apex/qry-builder) |
| **Save records**<br>Insert, update, upsert, delete, unit of work | [Fast Start: DML](/fast-start-dml) | [DML guide](/dml-guide) | [DML_Builder](/reference/apex/dml-builder) |
| **Run code on a trigger**<br>Logic before and after a save | [Fast Start: Trigger Actions](/fast-start-trigger-actions) | [Triggers guide](/triggers-guide) | [TRG_Base](/reference/apex/trg-base) |
| **Log what happened**<br>Instead of `System.debug` | [Fast Start: Logging](/fast-start-logging) | [Logging guide](/logging-guide) | [LOG_Builder](/reference/apex/log-builder) |
| **Run work in the background**<br>Queueable jobs in steps | [Fast Start: Async Processing](/fast-start-async-processing) | [Async Processing guide](/async-processing-guide) | [UTIL_AsyncChain](/reference/apex/util-asyncchain) |
| **Call another system**<br>HTTP callouts and retries | [Fast Start: Outbound APIs](/fast-start-outbound-apis) | [Web Services guide](/web-services-guide) | [UTIL_HttpClient](/reference/apex/util-httpclient), [API_Outbound](/reference/apex/api-outbound) |
| **Run a scheduled job**<br>Schedulable and the job runner | [Fast Start: Scheduled Jobs](/fast-start-scheduled-jobs) | [Async Processing guide](/async-processing-guide#scheduler-framework) | [SCHED_Base](/reference/apex/sched-base) |
| **Validate records**<br>Rules that stop bad data | [Fast Start: Custom Validations](/fast-start-custom-validations) | [Validation guide](/validation-guide) | [UTIL_ValidationRule](/reference/apex/util-validationrule) |
| **Control who can see records**<br>Sharing, field security and user mode | [Fast Start: Security](/fast-start-security) | [Security guide](/security-guide) | [QRY_Builder.Builder](/reference/apex/qry-builder-builder), [UTIL_Sharing](/reference/apex/util-sharing) |
| **Test my code**<br>Test data and pretend query results | [Fast Start: Test Data](/fast-start-test-data) | [Test Data guide](/test-data-guide) | [TST_Builder](/reference/apex/tst-builder), [TST_Mock](/reference/apex/tst-mock) |

> **Namespaces in code samples:** `kern.` on a class and `kern__` on an object, field, or metadata type mark the managed package's namespace.
> On the managed package, framework references need those prefixes even where a sample omits them; repackaged under your own namespace, replace `kern`/`kern__`
> with your prefix; on an unmanaged deploy, drop them. See [How to read the code samples](/installation#how-to-read-the-code-samples).

## Start here: the daily drivers

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

- [**Trigger Actions**](/fast-start-trigger-actions): add behaviour to a trigger by creating a configuration record, with no trigger code to write. Each behaviour can be switched off without a deployment (a 4-level kill switch, the master off-switch you flip in an incident), and every bypass is audit-logged.
- [**Selectors**](/fast-start-selectors): one query class per object that respects the running user's field-level security (FLS = field-level security), is easy to swap out in tests, and catches mistyped field names at compile time.
- [**DML**](/fast-start-dml): writes that enforce the current user's permissions and record sharing by default (USER_MODE), batched into one all-or-nothing transaction, with async saves and automatic parent-before-child ordering.
- [**Security**](/fast-start-security): field-level security and object permissions (FLS/CRUD: object create, read, update, delete) enforced by default. When a check is bypassed, the framework records the reason the caller gave.
- [**Logging**](/fast-start-logging): structured logs you can search and keep, with one tracking ID that follows a single user action across triggers, queries, callouts, and jobs (a correlation ID), plus flood control. This is the replacement for `System.debug`.

## Build features

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

- [**LWC**](/fast-start-lwc): build Lightning components on `ComponentBuilder` (a base class with the common wiring already built in) and shared patterns, instead of starting from raw `LightningElement`.
- [**Outbound APIs**](/fast-start-outbound-apis): callouts that survive flaky external systems. They retry on failure; after repeated failures they stop calling the failing system for a cool-off, then resume (a circuit breaker); a repeated request returns the first result instead of running twice (an idempotency key); and messages that fail every retry are set aside for inspection rather than lost (a dead-letter queue).
- [**Inbound APIs**](/fast-start-inbound-apis): a two-class pattern for receiving REST calls. A small class carries exactly the fields to move in or out and converts itself to and from JSON (a DTO), and a repeated request is answered from the first result instead of running again.
- [**Async Processing**](/fast-start-async-processing): chained queueables and batches, with one tracking ID (a correlation ID) threaded through the whole run so you can follow it end to end.
- [**Scheduled Jobs**](/fast-start-scheduled-jobs): schedule a class with a record you edit on a screen, with no deployment to change it, then put it on the job runner, which runs many jobs from a few of the org's scheduled-job slots, as often as every five minutes.
- [**Feature Flags**](/fast-start-feature-flags): switches that turn behaviour on or off per org or user from configuration, with no deployment needed to flip them.

## Harden

Add governance and safety once the feature works.

- [**Custom Validations**](/fast-start-custom-validations): validation rules you define as configuration, that Flows can call and that return structured errors.
- [**Resilience**](/fast-start-resilience): circuit breakers (stop calling a failing system for a cool-off, then resume) and retry policies for downstream systems that fail under load.
- [**Data Masking**](/fast-start-data-masking): field-level masking for logs and exports, so personal data and secrets are redacted by rule before they leave.
- [**Test Data**](/fast-start-test-data): builder-based test factories that avoid inline DML and keep working across namespaces.

## CI & quality

Drop the framework's guardrails into your pipeline.

- [**Code Scanning**](/fast-start-code-scanning): PMD rulesets, an ESLint plugin, and secret scanning that run in your pipeline to catch problems before they merge.
- [**E2E Testing**](/fast-start-e2e-testing): Playwright-first end-to-end tests that run against the deployed org, so you exercise the real UI.
