Skip to content
Runs on
Lightning record pages
Rules in
Formula · SOQL · Apex
Package
Namespaced 2GP · rhc

A coach on every Salesforce record

Turn business rules into plain-language guidance on Lightning record pages, with no blocked saves and no data changes.

  • No code required
  • Never changes record data
  • Open source

4 evaluation types · 25 checks per card · 0 record changes

Installing in production? Use the production installer

Record Health Check card on an Account: a passed check, then a failed check that says the account owner is inactive, shows what it found and what it expected, and offers a fix link to open the owner record
3 passed2 failed1 warning1 info1 skipped

How it works

From rule to fix in three steps

Write the rule once in Setup, and every user sees the guidance on the record they are working in.

  1. Write a rule

    Describe what must be true about a record with a formula, a query, two compared queries, or Apex.

    Custom Metadata
  2. Add the card to a record page

    Drop the Record Health Check component on any Lightning record page in App Builder.

    App Builder
  3. Users see what to fix

    Each result explains what it found, what it expected, and links straight to the fix.

    Record page

Guided path

The fastest path to a working Check

Follow one focused sequence from understanding the card to configuring your first production-ready experience.

Examples

See it solve real Salesforce problems

Compare four ways to answer a business question about an Account. Each example shows why the method fits, what a user sees, and what to do next.

01Keep branch billing aligned with headquartersFor branches billed through headquarters, confirm the complete billing address matches the parent Account.Runs on: AccountVerify with a formula

Why this method?

Both addresses are available from the Account and its parent, so a formula can compare them directly. No related-record query or custom Apex class is needed.

A difference in any billing-address field needs attention. An Account without a parent is skipped. Display formulas show the two addresses but do not determine Pass or Fail.

Example result

Found
Branch: 100 Congress Ave, Austin, TX 78701
Display formula on the branch Account
Expected
Parent: 500 Elm St, Dallas, TX 75202
Display formula on the parent Account
Result
Info
Next step
Confirm the legal bill-to location with Finance before correcting either Account.

Key configuration

Pass Condition
AND(BillingStreet = Parent.BillingStreet, BillingCity = Parent.BillingCity, BillingState = Parent.BillingState, BillingPostalCode = Parent.BillingPostalCode, BillingCountry = Parent.BillingCountry)
Display: Found Formula
Complete branch billing address
Display: Expected Formula
Complete parent billing address
Open full setup and testing
02Keep the high-priority support backlog within capacityCount open, high-priority Cases for an Account without blocking Case updates.Runs on: AccountVerify with a query

Why this method?

The information is on Cases related to this Account. A query counts the open Cases marked High priority, and the Check compares that count with the service team’s limit.

No matching Cases returns a count of zero, so this Check passes. Hidden records are excluded; missing required permissions may produce Unable to Check.

Example result

Found
4 open high-priority Cases
COUNT() of matching visible Cases
Expected
at most 3
Fixed value configured by the service team
Result
Warning
Next step
Review Case ownership and the response plan.

Key configuration

Source Query
SELECT COUNT() FROM Case WHERE AccountId = {!record.Id} AND IsClosed = false AND Priority = 'High'
Comparison Operator
At most
Expected Value
Fixed value: 3
Open full setup and testing
03Protect product continuity across open pipelineCheck whether this Account’s open Opportunities include a product recorded on its previously won Opportunities.Runs on: AccountCompare two queries

Why this method?

One query finds products on open Opportunities. Another finds products on won Opportunities. The Check passes when the two Product ID lists share at least one value.

Product names are illustrative; the Check compares Product IDs. When either list is empty, the Check is skipped, because If Query Finds No Records is set to Skip.

Example result

Found
Open pipeline: Product A, Product B
Source query → Product2Id
Expected
Won Opportunities: Product B, Product C
Comparison query → Product2Id
Result
Pass — Product B appears in both lists
Next step
If the lists do not overlap, confirm the intended sale before changing product selection.

Key configuration

Source Query Field
Product2Id
Comparison Query Field
Product2Id
Comparison Operator
Lists overlap
If Query Finds No Records
Skip
Open full setup and testing
04Score a customer Account’s readinessUse a developer-created Apex class to combine Contacts, open pipeline, recent activity, and billing address into one readiness score.Runs on: AccountVerify with Apex

Why this method?

The decision combines several objects, a configurable activity window, and weighted scoring. A developer implements that logic in an Apex class; an administrator can then configure its threshold and parameters.

The class awards 25 points for each criterion, so possible scores are 0, 25, 50, 75, and 100. With a minimum of 75, any three criteria pass. Accounts outside the applicability formula are skipped.

Example result

Found
75 points — three of four criteria met
Score returned by AccountStrategicReadinessCheck
Expected
at least 75
minScore in Apex Parameters (JSON)
Result
Pass
Next step
If the score drops below 75, review which of the four criteria is missing.

Key configuration

Apex Class
AccountStrategicReadinessCheck
Apex Parameters (JSON)
{"minScore": 75, "activityDaysBack": 60}
Applies When
ISPICKVAL(Type, "Customer - Direct")
Open full setup and testing

Documentation

Choose what you want to do

Go straight to the guides for the job in front of you.

Resources

Explore the ecosystem

Go beyond the core package with optional extensions.