Feature catalog
Find every capability of Record Health Check 2.0.11, what it supports, and the guide that explains it. Record Health Check is a read-only evaluation framework: it reports whether records meet configured requirements, and it never changes business records, blocks saves, or keeps a result history by itself.
Configure Check Sets and Checks
Section titled “Configure Check Sets and Checks”| Capability | Supported behavior | Detailed guide |
|---|---|---|
| Custom Metadata configuration | Check Sets define one record-page review; Checks define the questions in that review. Configuration can move through normal Salesforce metadata processes. | Configure Check Sets and Checks |
| Record-object matching | A Check Set names one Salesforce object. The App Builder picker shows active Check Sets matching the record page’s object. | Configure the component |
| Automatic and Manual runs | When the page opens (RUN_) runs the Checks as soon as the record page opens. When the user clicks Run (RUN_) waits until the user selects Run. | Choose how Checks run |
| Card presentation | Configure title, subtitle, heading visibility, summary, all-at-once or one-by-one reveal, passed and skipped visibility, Found/Expected disclosure, and Run/Rerun button labels, icon, and visibility. | Check Set fields |
| Ordered Checks and categories | Evaluation Order controls presentation order. Prerequisite references control dependency scheduling. Category groups summaries without changing the outcome. | Check fields |
| Applicability | Applies To chooses all records, a formula, or a count query to decide whether a Check applies. A Check that does not apply is SKIPPED, not PASS. | Configure Check Sets and Checks |
| Prerequisites | A Check can name another Check in the same Check Set that must pass first; otherwise it is SKIPPED. Dependency cycles are rejected. | Check fields: Prerequisite Check |
| Stop after a system error | On the record-page card, a Check Set can skip the Checks that have not run yet after a system error, keeping the results already completed. | Check Set fields |
| Configuration validation action | Validate Record Health Check Configuration audits Check and Check Set metadata and returns error, warning, and JSON report outputs. | Flow action inputs and outputs |
Evaluate record health
Section titled “Evaluate record health”| Evaluation Type | Supported behavior | Detailed guide |
|---|---|---|
Formula (FORMULA) | Evaluate current-record and supported parent-relationship fields with Salesforce formula evaluation. The Pass Condition decides the result, and optional display formulas show separate Found and Expected values. | Formula reference |
Query (QUERY) | Run user-mode SOQL within the configured row limit for one value, any-row, every-row, or list-membership decisions. Configure no-row, empty-value, and maximum-row outcomes explicitly. | Query reference |
Compare two queries (COMPARE_) | Compare two counts, individual values, or lists, including overlap, contains-all, and exact-list behavior. | Compare two queries |
Apex plugin (APEX) | Run reviewed bulk Apex implementing RecordHealthCheckPlugin, returning exactly one typed outcome for every requested record ID. | Write an Apex Check |
| Typed plugin definitions | Optional definitions declare integer, choice, string, and Boolean parameters, defaults, bounds, help, nullability, and scope capacity. | Plugin definitions |
| Typed outcome builders and per-record recovery | Equality/list builders reject contradictory values, while bounded per-record recovery isolates ordinary record failures. | typed outcomes |
| Typed plugin evidence | Plugins can attach bounded evidence rows with synthetic or permission-checked field provenance. | plugin evidence |
| Apex presentation overrides | Optional display plugins add rich values, guidance, safe actions, labels, and formats without changing evaluation. | Apex presentation |
| Plugin contract verification | Extend the packaged contract-test support class to verify bulk query growth, complete scope coverage, permission behavior, and prohibited side effects. | Verify an Apex Check |
| Bulk query planning | Formula, Query, Compare two queries, and Apex Checks load and evaluate as many as 200 requested records together. | Bulk-query grammar |
Explain and display results
Section titled “Explain and display results”| Capability | Supported behavior | Detailed guide |
|---|---|---|
| Honest outcomes | Results distinguish PASS, FAIL, SKIPPED, UNABLE_, and ERROR. Failed, Warning, and Info are severity presentations of FAIL. | Statuses and labels |
| Stable Reason Codes | Programmatic reasons distinguish business outcomes from access, configuration, data, and framework problems. | Reason Codes |
| Found and Expected values | Show the compared values, or administrator-authored display formulas and text, without changing the verdict. | Display Found and Expected |
| Display formats | Automatic, Number, Currency, Percent, Ratio as percent, Checkbox, Date, Date/Time, Text, and Raw formats follow the running user’s locale where applicable. | Display formats |
| Lists and multiple currencies | List previews show at most 10 values and the total count. Each value keeps its own currency; formatting never converts currencies. | List previews |
| Guidance and actions | Failure, unable, applicability, and fix messages support safe merge tokens. Optional Action Label and Action URL provide a read-only next step. | Configure action links |
| Merge tokens | Record, result, Check, Check Set, run, and query-row values can be inserted into messages and safe links with typed formatting and explicit fallbacks. | Merge syntax |
| Inline links and grouped display | Explicit link nodes, record links, line breaks, and ordered groups render through bounded same-org/HTTPS URL policy with plain-text fallback. | structured presentation |
| Diagnostics | Authorized viewers can see restricted diagnostic detail, such as the specific Reason Code and field, and produce a redacted support report. Ordinary users receive safe guidance without internal details. | Browser diagnostics |
| Diagnostic contract 2.0 | Opt-in Apex diagnostics expose bounded, value-free incident coordinates and lifecycle traces with sanitized compiler categories. | Authorized diagnostics |
| Detached draft preview | Administrators can validate or execute one unsaved Check against its saved Check Set without publishing events. | Validate and preview a draft |
| Readiness receipts | Explicit, private, 30-day receipts bind verification to the exact actor, org, definition, capabilities, and record scope. | Readiness receipts |
| Localization and accessibility | Labels can use Salesforce translations; values follow locale and timezone rules. The card supports keyboard use, responsive layout, SLDS 1, SLDS 2, and the active Salesforce theme. | Languages and locales, theme and accessibility |
Run from Salesforce and integrations
Section titled “Run from Salesforce and integrations”| Entry point | Supported behavior | Detailed guide |
|---|---|---|
| Lightning record page | One component runs the selected Check Set for the current record. It is intentionally unavailable on App and Home pages because those pages have no record context. | Lightning record page |
| Record Health Check Preview | A separate administrator component validates and previews a detached Check from a Lightning App page, Home page, or tab. It does not save or activate metadata. | Validate and preview a draft |
Save and RefreshView refresh | Automatic cards refresh after a standard record save or refresh notification. Manual cards refresh only after their first completed Run. Stale and overlapping runs cannot replace newer results. | Refresh after a record save |
| Flow | Separate actions run one Check or one Check Set and return stable status, count, reason, and JSON outputs. A third action validates configuration. | Flow guides |
| Synchronous Apex | RecordHealthCheck. accepts a typed request for one Check or Check Set. Result modes provide complete evaluation (EVALUATION), evaluation with display (EVALUATION_), or summary plus actionable results (SUMMARY). | Run from Apex |
| Queueable Apex | Submit up to 200 known record IDs for later execution and monitor the Apex job ID. | Queueable |
| Batch Apex | Evaluate up to 2,000 known IDs with the packaged Batch class, or any number that a query finds with your own Batch class. | Batch |
| Scheduled Apex | Run a fixed list of up to 2,000 IDs every day with the packaged scheduler, which starts the packaged Batch class, or schedule your own class. Move existing Future callers to Queueable. | Scheduled, replace Future |
| Agentforce | Packaged agent actions run one Check or Check Set for one record and return its status, counts, and bounded diagnosis fields without exposing restricted details. | Agentforce actions |
| REST agent tool | A versioned REST adapter exposes Check and Check Set operations for authorized integration users. | Agent tool REST API |
| MCP service | The companion Node service maps MCP tools to the versioned REST contract, with documented authorization, timeouts, and deployment checks. | Deploy the MCP service |
| Versioning and correlation | Contract versions protect long-lived consumers. Run IDs, correlation IDs, and execution origins connect work and diagnostics across transaction boundaries. | Contracts, integration options |
Publish and receive results
Section titled “Publish and receive results”| Capability | Supported behavior | Detailed guide |
|---|---|---|
| Event publication modes | NONE publishes nothing. ACTIONABLE publishes a Set Run event for every record and Check Result events only for results that need attention. ALL publishes Set Run and Check Result events for every result. | Choose where results go |
Check Result event (Record_) | Publishes one Check outcome with its identity, status, severity, and Reason Code. | Check Result metadata |
Check Set Run event (Record_) | Publishes one summary per record with its counts and, for a Batch, Queueable, or Scheduled job that publishes events, one final event when the job completes or fails. | Check Set Run metadata |
Error Log event (Record_) | Publishes restricted operational incidents only when enabled and authorized. | Error Log metadata |
| Flow, Apex, and Pub/Sub consumers | Subscribers can route events to approved storage, automation, or external systems. Events are not permanent storage themselves. | Save results, Pub/Sub |
Security and safety
Section titled “Security and safety”Choose the narrowest Permission Set for each task instead of treating these as levels of access: Record Health Check Card User, Record Health Check User, Record Health Check Admin, Record Health Check MCP Integration, Record Health Check Diagnostics Viewer, Record Health Check Error Log Publisher, and Record Health Check Readiness Auditor.
| Capability | Supported behavior | Detailed guide |
|---|---|---|
| User-context access | Business-record reads use user mode, and Apex plugins run with sharing. The package does not grant access to subscriber business objects or fields. | Security and data access |
| Purpose-specific access | Seven Permission Sets separate card, automation, administration, integration, diagnostic viewing, restricted logging, and read-only readiness review. | Permission Sets |
| Run and diagnostic permissions | Record Health Check Run authorizes execution. A direct Record Health Check Admin or Record Health Check Diagnostics Viewer Permission Set assignment authorizes restricted diagnostic detail when the Check Set also enables it. | Custom Permissions |
| Plugin side-effect protection | Plugin dispatch rejects detected record writes, callouts, email, Queueable, and Future work. Platform Event, Batch, and Scheduled prohibitions also require contract tests, static analysis, and review because Apex exposes no complete transaction counter for them. | Verify an Apex Check |
| Safe templates and links | Query templates, merge tokens, and Action URLs are validated and checked against their documented limits. Unsupported or inaccessible inputs return an unable-to-evaluate result instead of a guessed verdict. | Merge syntax, bulk-query grammar |
| Namespaced configuration | Qualified API names and foreign-package field namespaces are preserved exactly across package and subscriber metadata. | Names and API identities |
| Request and field limits | Record, Check, query-row, FormulaEval, token, field-size, and output limits are documented and enforced. | Limits at a glance, field limits |
Package, examples, and operations
Section titled “Package, examples, and operations”| Capability | Supported behavior | Detailed guide |
|---|---|---|
| Immutable 2GP package versions | Install a specific 04t version and test that same version in a sandbox before upgrading production. | Choose a package version |
| Install, upgrade, and uninstall | Guides cover sandbox-first installation, permission assignment, configuration backup, rehearsing an upgrade from the previous version, and safe uninstall preparation. | Install |
| Packaged examples | Four active Example Check Sets contain 50 Checks (49 active) across Account, Contact, and Opportunity. Matching docs explain Formula, Query, Compare two queries, Apex, applicability, display, and remediation patterns. | Explore installed examples, examples library |
| Production operations | Back up subscriber-owned Custom Metadata, monitor events and jobs, test least-privilege users, and preserve evidence for support. | Production operations |
Explicit boundaries and non-features
Section titled “Explicit boundaries and non-features”| Boundary | Current behavior | Detailed guide |
|---|---|---|
| No record mutation or enforcement | The framework advises. Use Validation Rules, Flow, or Apex when Salesforce must block or perform an action. | When to use Record Health Check |
| No automatic history store | API responses and optional Platform Events are transient until an approved subscriber saves them. | When to use Platform Events |
| No generic freshness evaluator | Express freshness through Formula, Query, Compare two queries, or reviewed Apex using explicit timestamps or provenance. | Derived values and freshness |
| Formula globals | $User, $Profile, $Setup, $Permission, and $CustomMetadata are not treated as checked-record fields and are not supported in a Pass Condition. | Formula limitations |
| Polymorphic owners | User-only owner formulas cannot reliably evaluate Queue or Group owners and return unable instead of guessing. | Polymorphic relationships |
| Account activity example | The packaged Apex example counts closed Tasks dated on or after the start of its look-back window, and Events dated on or after that day, including future Events, whose WhatId is the Account. It does not count Contact WhoId activity or shared relations. | Activity limitations |
| Person Accounts | Generic Contact-count examples can count the underlying PersonContact. Use explicit Person Account applicability and fields. | Person Accounts |
| Currency conversion | Display preserves available currency identity but does not perform corporate, dated, or Advanced Currency Management conversion. | Currency limitations |
| Save refresh events | Browser save refresh uses the non-publishing lifecycle; it does not publish Check Result or Check Set Run events unless a normal configured run requests publication. | Refresh after a record save |
| Unsupported query shapes | Unsafe or unsupported SOQL shapes, inaccessible schema, row-cap overflow, and unprovable values return unable rather than a partial verdict. | Platform limitations |