Account Check Builder Guide: configuration and results
The Example: Account Check Builder Guide Check Set installs with Record Health Check and contains 25 Account Checks that teach every Evaluation Type: three formula Checks, ten query Checks, eleven Compare two queries Checks, and one Apex Check. This page lists every Setup value of each Check exactly as installed, and its result on the Acme Corporation demo Account, so you can study a working Check before you build your own.
How to use this page
Section titled “How to use this page”- Find a Check on the card by its title. Several Record Health Check Name values were kept from
earlier releases and do not describe what the Check does now, such as
Example_Website_URL_Validfor Account Type is set. - In an org where the package is installed, every name has the
rhc__prefix, such asrhc__Example_Website_URL_Valid. - The tables show the values that differ from the defaults. Every Check is active, belongs to the
Example_Account_Check_Builder_GuideCheck Set, and has Publish User Result Event cleared. - Each result names the label the card shows on Acme Corporation, the Account that the demo scratch org creates. In your own org the results depend on your data.
- To change a Check, clone it into a Check Set your organization owns. A package upgrade can replace changes made to the installed record.
The Check Set waits for Run, reveals one row at a time, shows passed and skipped rows, shows Found and Expected on demand, and places one summary below the rows; none of these Checks has a Category. On Acme Corporation the summary reads 7 Passed, 5 Failed, 9 Warnings, 3 Info, and 1 Unable.
Formula Checks
Section titled “Formula Checks”These Checks read fields on the Account and its parent Account.
Check 10: Account Type is set
Section titled “Check 10: Account Type is set”Label: Example: Account Type is set. Record Health Check Name: Example_Website_URL_Valid. Result on Acme Corporation: Pass. Acme’s Type is Customer.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a formula |
| Check Description | The formula checks the standard Account Type picklist. It passes when Type has a value and fails when Type is blank. |
| Applies To | All records |
| Pass Condition | NOT(ISBLANK(TEXT(Type))) |
| Display: Found Formula | IF(ISBLANK(TEXT(Type)), "Not set", TEXT(Type)) |
| Display: Expected Formula | "An Account Type is selected" |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Text |
| Formula Result Type | Text |
| Failure Severity | Warning |
| Message When Failed | {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Set Account Type for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 20: Account has a phone number or website
Section titled “Check 20: Account has a phone number or website”Label: Example: Account Phone or Website. Record Health Check Name: Example_Segregation_Of_Duties. Result on Acme Corporation: Pass. Acme has a Phone and a Website.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a formula |
| Check Description | The formula checks the standard Account Phone and Website fields. It passes when either field has a value and fails when both are blank. This checks completeness, not whether the number or website is valid. |
| Applies To | All records |
| Pass Condition | OR(NOT(ISBLANK(Phone)), NOT(ISBLANK(Website))) |
| Display: Found Formula | "Phone: " & BLANKVALUE(Phone, "Not set") & "; Website: " & BLANKVALUE(Website, "Not set") |
| Display: Expected Formula | "A phone number or website is provided" |
| Display: Value Format | Text |
| Formula Result Type | Text |
| Failure Severity | Warning |
| Message When Failed | {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Add Phone or Website for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 30: Billing address matches the parent bill-to account
Section titled “Check 30: Billing address matches the parent bill-to account”Label: Example: Parent bill-to alignment. Record Health Check Name: Example_Guide_Industry_Manufacturing. Result on Acme Corporation: Pass. Acme’s billing address matches its parent Account’s.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a formula |
| Check Description | The formula passes only when all five billing-address components match the parent; any difference fails and no parent skips. Clone only when centralized parent billing is policy, with rules for normalization and legal-entity exceptions. |
| Applies To | When a formula is true |
| Applies When (Formula) | NOT(ISBLANK(ParentId)) |
| Message When Not Applicable | {!record. |
| Pass Condition | AND(BillingStreet = Parent. |
| Display: Found Formula | BillingStreet & ", " & BillingCity & ", " & BillingState & " " & BillingPostalCode & ", " & BillingCountry |
| Display: Expected Formula | Parent. |
| Display: Value Format | Text |
| Formula Result Type | Text |
| Failure Severity | Info |
| Message When Failed | {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | The billing addresses for {!record. |
| Action Label | Review bill-to address for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Query Checks
Section titled “Query Checks”These Checks progress from a count compared with a fixed number (40, 50), to tests of every returned row (60 to 90), Contact Roles (100, 110), a value found in a list (120), and an expected value from a second query (130).
Check 40: High-priority open Cases stay within the limit
Section titled “Check 40: High-priority open Cases stay within the limit”Label: Example: High-priority Case count. Record Health Check Name: Example_Fewer_Than_Ten_Open_Cases. Result on Acme Corporation: Failed. Acme has 4 open High-priority Cases; the limit is 1.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check counts open Cases with Priority High. It passes when no more than one high-priority Case requires Account-level escalation at the same time. |
| Applies To | All records |
| Source Query | SELECT COUNT() FROM Case WHERE AccountId = {!record. |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | At most |
| Expected Value Comes From | Fixed value |
| Expected Value (Fixed) | 1 |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Critical |
| Message When Failed | {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review Cases for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 50: At least one open Opportunity is Commit
Section titled “Check 50: At least one open Opportunity is Commit”Label: Example: Commit Opportunity count. Record Health Check Name: Example_Significant_Open_Opp. Result on Acme Corporation: Info. No open Opportunity is in the Commit forecast category.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check counts open Opportunities with Forecast Category Commit. It passes when at least one open deal is included in the committed forecast. |
| Applies To | All records |
| Source Query | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | At least |
| Expected Value Comes From | Fixed value |
| Expected Value (Fixed) | 1 |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Info |
| Message When Failed | {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review pipeline for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 60: Every open Case has a Contact
Section titled “Check 60: Every open Case has a Contact”Label: Example: Open Case Contacts. Record Health Check Name: Example_Open_Cases_Have_Contacts. Result on Acme Corporation: Failed. 6 of the 12 open Cases have no Contact.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check reads Contact on each open Case. It passes only when every returned Case has a Contact. With no open Cases, it passes. |
| Applies To | All records |
| Source Query | SELECT ContactId FROM Case WHERE AccountId = {!record. |
| Source Query Field | ContactId |
| How To Read Query Results | Every record passes |
| Comparison Operator | Is not empty |
| If Query Finds No Records | Pass |
| If Field Value Is Empty | Treat as not matching |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | None missing |
| Display: Value Format | Text |
| Failure Severity | Critical |
| Message When Failed | One or more open Cases for {!record. |
| Fix Message | Assign the correct customer Contact to each open Case on {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review open Cases for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 70: Every escalated open Case has a Description
Section titled “Check 70: Every escalated open Case has a Description”Label: Example: Escalated Case descriptions. Record Health Check Name: Example_Guide_Contacts_Have_Email. Result on Acme Corporation: Warning. The escalated open Case has no Description.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check reads Description on each escalated open Case. It passes only when every Description has a value. No escalated open Cases skips the check. It does not assess the quality of the text. |
| Applies To | All records |
| Source Query | SELECT Description FROM Case WHERE AccountId = {!record. |
| Source Query Field | Description |
| How To Read Query Results | Every record passes |
| Comparison Operator | Is not empty |
| If Query Finds No Records | Skip |
| If Field Value Is Empty | Treat as not matching |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | None missing |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | One or more escalated open Cases for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review escalated Cases for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 80: Every open Opportunity has an active owner
Section titled “Check 80: Every open Opportunity has an active owner”Label: Example: Active Opportunity owners. Record Health Check Name: Example_High_Value_Open_Opp. Result on Acme Corporation: Pass. Both open Opportunities have active owners.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check verifies Active on the owner of every open Opportunity. It passes only when every Opportunity owner is an active Salesforce user. |
| Applies To | All records |
| Source Query | SELECT Owner. |
| Source Query Field | Owner. |
| How To Read Query Results | Every record passes |
| Comparison Operator | Equal to |
| Expected Value Comes From | Fixed value |
| Expected Value (Fixed) | true |
| If Query Finds No Records | Pass |
| If Field Value Is Empty | Treat as not matching |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | None inactive |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | One or more open Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review pipeline for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 90: No proposal has a missing or low Amount
Section titled “Check 90: No proposal has a missing or low Amount”Label: Example: Proposal Amount exceptions. Record Health Check Name: Example_Open_Opps_Have_Amount. Result on Acme Corporation: Pass. The proposal’s Amount is $600,000, above the $25,000 minimum.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check returns only proposal-stage Opportunities whose Amount is blank or below $25,000. It passes when the query returns no Opportunity names. |
| Applies To | All records |
| Source Query | SELECT Name FROM Opportunity WHERE AccountId = {!record. |
| Source Query Field | Name |
| How To Read Query Results | Every record passes |
| Comparison Operator | Is empty |
| If Query Finds No Records | Pass |
| If Field Value Is Empty | Treat as not matching |
| Display: Found Text | Proposal opportunities needing review: {!rhcResult. |
| Display: Expected Text | No exceptions |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | One or more proposal-stage Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review Opportunities for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 100: Open Opportunities include a Decision Maker
Section titled “Check 100: Open Opportunities include a Decision Maker”Label: Example: Decision Maker roles. Record Health Check Name: Example_Has_At_Least_One_Contact. Result on Acme Corporation: Pass. One Decision Maker Contact Role is on an open Opportunity.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check counts Decision Maker Contact Roles across open Opportunities. It passes when at least one role exists. This checks the recorded role, not whether the person has verified buying authority. |
| Applies To | All records |
| Source Query | SELECT COUNT() FROM OpportunityContactRole WHERE Opportunity. |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | At least |
| Expected Value Comes From | Fixed value |
| Expected Value (Fixed) | 1 |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Warning |
| Message When Failed | No decision-maker Contact Role is identified across the open pipeline for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review buying roles for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 110: Contacts on open deals have Email or Phone
Section titled “Check 110: Contacts on open deals have Email or Phone”Label: Example: Contact details on open deals. Record Health Check Name: Example_Contact_States_Match_Billing. Result on Acme Corporation: Warning. One Contact Role’s Contact has neither Email nor Phone.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check counts Contact Roles on open Opportunities whose Contact has neither Email nor Phone. It passes when the count is zero. It checks presence, not whether the contact details are valid. |
| Applies To | All records |
| Source Query | SELECT COUNT() unreachableStakeholders FROM OpportunityContactRole WHERE Opportunity. |
| Source Query Field | unreachableStakeholders |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Expected Value Comes From | Fixed value |
| Expected Value (Fixed) | 0 |
| If Query Finds No Records | Pass |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | None missing both |
| Display: Value Format | Number |
| Failure Severity | Warning |
| Message When Failed | One or more open-deal stakeholders for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review buying contacts for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 120: Open-deal Contact Roles include Technical Buyer
Section titled “Check 120: Open-deal Contact Roles include Technical Buyer”Label: Example: Find a Technical Buyer role. Record Health Check Name: Example_Billing_State_In_Contacts. Result on Acme Corporation: Info. No open-deal Contact Role is Technical Buyer.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check searches the Role values on open Opportunities for Technical Buyer. It passes when the role appears. Found shows the value being sought; Expected shows the returned list to search. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM OpportunityContactRole WHERE Opportunity. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| How To Read Query Results | Compare as lists |
| Value to find in the list (formula) | "Technical Buyer" |
| Comparison Operator | List contains any |
| Comparison Query | SELECT Role FROM OpportunityContactRole WHERE Opportunity. |
| Comparison Query Field | Role |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Text |
| Failure Severity | Info |
| Message When Failed | No Technical Buyer is identified across the open-deal buying committee for {!record. |
| Fix Message | Validate the buying process for {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review buying committee for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 130: Cases closed keep pace with Cases created
Section titled “Check 130: Cases closed keep pace with Cases created”Label: Example: Cases closed vs created. Record Health Check Name: Example_Contacts_Cover_Open_Cases. Result on Acme Corporation: Warning. 4 Cases closed and 16 were created in the last 30 days.
| Field | Value |
|---|---|
| Evaluation Type | Verify with a query |
| Check Description | The Query check compares 30-day Case resolution throughput with intake and passes when closures meet or exceed new demand, making backlog direction visible at the Account level. |
| Applies To | All records |
| Source Query | SELECT COUNT() FROM Case WHERE AccountId = {!record. |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | At least |
| Expected Value Comes From | Comparison query |
| Comparison Query | SELECT COUNT() FROM Case WHERE AccountId = {!record. |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Warning |
| Message When Failed | Fewer Cases were closed than created for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review Cases for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Compare two queries Checks
Section titled “Compare two queries Checks”These Checks compare two counts (140 to 200), two totals (210), or two lists (220 to 240).
Check 140: Every won Opportunity has an Amount
Section titled “Check 140: Every won Opportunity has an Amount”Label: Example: Won Opportunity Amounts. Record Health Check Name: Example_Parent_Cities_Require_Data. Result on Acme Corporation: Warning. The won Opportunity has no Amount.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check compares won Opportunities with won Opportunities whose Amount is not blank. It passes when both counts match. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT COUNT() valuedDeals FROM Opportunity WHERE AccountId = {!record. |
| Source Query Field | valuedDeals |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT COUNT() allDeals FROM Opportunity WHERE AccountId = {!record. |
| Comparison Query Field | allDeals |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Warning |
| Message When Failed | One or more won Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review historical deals for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 150: Every proposal has a Next Step
Section titled “Check 150: Every proposal has a Next Step”Label: Example: Proposal Next Steps. Record Health Check Name: Example_Contact_Vs_Open_Opp_Count. Result on Acme Corporation: Warning. The proposal has no Next Step.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check counts proposals with Next Step and all proposals. It passes when the counts match. This checks that Next Step has text, not whether the action has been agreed. |
| Applies To | All records |
| Source Query | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Warning |
| Message When Failed | One or more proposals for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review next steps for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 160: Every proposal has a Primary Campaign Source
Section titled “Check 160: Every proposal has a Primary Campaign Source”Label: Example: Proposal Campaigns. Record Health Check Name: Example_Guide_Open_Deals_Have_Contacts. Result on Acme Corporation: Failed. The proposal has no Primary Campaign Source.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check counts proposals with a Primary Campaign Source and all proposals. It passes when the counts match. This checks the Campaign link, not the accuracy of attribution. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT COUNT() coveredDeals FROM Opportunity WHERE AccountId = {!record. |
| Source Query Field | coveredDeals |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Critical |
| Message When Failed | One or more proposal-stage Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review campaign sources for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 170: Open Opportunity Close Dates are in range
Section titled “Check 170: Open Opportunity Close Dates are in range”Label: Example: Open Opportunity Close Dates. Record Health Check Name: Example_Distinct_Cities_Vs_Contacts. Result on Acme Corporation: Info. Only 1 of the 2 open Opportunities closes within the next 180 days.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check passes when every open Opportunity has a Close Date from today through the next 180 days, detecting both stale dates and dates outside the operating forecast horizon. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Info |
| Message When Failed | One or more open Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review Close Dates for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 180: Every open Opportunity has a Contact Role
Section titled “Check 180: Every open Opportunity has a Contact Role”Label: Example: Open Opportunity Contact Roles. Record Health Check Name: Example_Oldest_Contact_City_Matches. Result on Acme Corporation: Failed. Only 1 of the 2 open Opportunities has a Contact Role.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check compares open Opportunities with open Opportunities represented by at least one Opportunity Contact Role. It passes when both counts match. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT COUNT_ |
| Source Query Field | coveredDeals |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT COUNT() allDeals FROM Opportunity WHERE AccountId = {!record. |
| Comparison Query Field | allDeals |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Critical |
| Message When Failed | One or more open Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review Contact Roles for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 190: Every won Opportunity has a primary Contact
Section titled “Check 190: Every won Opportunity has a primary Contact”Label: Example: Won Opportunity primary roles. Record Health Check Name: Example_Earliest_Vs_Latest_Close. Result on Acme Corporation: Warning. The won Opportunity has no primary Contact Role.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check passes when every won Opportunity retains a primary Contact Role, preserving buyer history for implementation handoff, renewal planning, and expansion. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT COUNT_ |
| Source Query Field | coveredDeals |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT COUNT() allDeals FROM Opportunity WHERE AccountId = {!record. |
| Comparison Query Field | allDeals |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Number |
| Failure Severity | Warning |
| Message When Failed | One or more won Opportunities for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review won deals for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 200: New pipeline value covers recently lost value
Section titled “Check 200: New pipeline value covers recently lost value”Label: Example: New pipeline vs lost value. Record Health Check Name: Example_Open_Pipeline_Covers_Revenue. Result on Acme Corporation: Failed. New open pipeline is $600,000; value lost in the last 90 days is $760,000.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check compares Amount from open Opportunities created in the last 90 days with Amount from Opportunities closed lost in the same period. It passes when new pipeline value equals or exceeds lost value. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT SUM(Amount) newPipeline FROM Opportunity WHERE AccountId = {!record. |
| Source Query Field | newPipeline |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | At least |
| Comparison Query | SELECT SUM(Amount) recentLosses FROM Opportunity WHERE AccountId = {!record. |
| Comparison Query Field | recentLosses |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Currency |
| Failure Severity | Critical |
| Message When Failed | New open pipeline value has not replaced recently lost Opportunity value for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review pipeline for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 210: Total proposal Amount matches total Product value
Section titled “Check 210: Total proposal Amount matches total Product value”Label: Example: Proposal and Product totals. Record Health Check Name: Example_Average_Deal_Vs_Largest. Result on Acme Corporation: Unable to Check. The proposal has no Opportunity Products to total.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check sums proposal Amounts and Product Total Prices across the Account. It passes when the totals match. Differences between individual proposals can cancel out; this is an Account-level reconciliation. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT SUM(Amount) proposalAmount FROM Opportunity WHERE AccountId = {!record. |
| Source Query Field | proposalAmount |
| How To Read Query Results | One row or aggregate |
| Comparison Operator | Equal to |
| Comparison Query | SELECT SUM(TotalPrice) productTotal FROM OpportunityLineItem WHERE Opportunity. |
| Comparison Query Field | productTotal |
| If Query Finds No Records | Unable to evaluate |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Currency |
| Failure Severity | Warning |
| Message When Failed | Proposal Amount does not match the Opportunity Product total for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!record. |
| Action Label | Review proposal Products for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 220: Sales and service share a Contact name
Section titled “Check 220: Sales and service share a Contact name”Label: Example: Sales and service Contacts. Record Health Check Name: Example_Contact_Cities_Overlap_Parent. Result on Acme Corporation: Warning. No Contact on an open Case is also a Contact Role on an open Opportunity.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check compares Contact names on open Cases with names on open Opportunities. It passes when the lists overlap. Matching names do not prove Contact identity; use IDs when distinct people can share a name. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Case WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT Contact. |
| Source Query Field | Contact. |
| How To Read Query Results | Compare as lists |
| Comparison Operator | Lists overlap |
| Comparison Query | SELECT Contact. |
| Comparison Query Field | Contact. |
| If Query Finds No Records | Skip |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | No customer Contact currently connects open service work and open sales work for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review stakeholders for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 230: Sales Contact names cover priority Case Contacts
Section titled “Check 230: Sales Contact names cover priority Case Contacts”Label: Example: Priority Case Contact coverage. Record Health Check Name: Example_Parent_Covers_Contact_Cities. Result on Acme Corporation: Warning. The Contacts on High-priority Cases are not Contact Roles on open Opportunities.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check compares Contact names on open Opportunities with names on high-priority open Cases. It passes when the first list contains every name in the second. Shared names can represent different Contacts. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Case WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT Contact. |
| Source Query Field | Contact. |
| How To Read Query Results | Compare as lists |
| Comparison Operator | Lists contain all |
| Comparison Query | SELECT Contact. |
| Comparison Query Field | Contact. |
| If Query Finds No Records | Skip |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | One or more Contacts on high-priority open Cases for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review handoffs for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Check 240: Open Opportunity names match those with Products
Section titled “Check 240: Open Opportunity names match those with Products”Label: Example: Opportunity Product coverage. Record Health Check Name: Example_Contact_Cities_Exact_Parent. Result on Acme Corporation: Warning. Neither open Opportunity has Products, so the two name lists do not match.
| Field | Value |
|---|---|
| Evaluation Type | Compare two queries |
| Check Description | The Compare Two Queries check compares open Opportunity names with names represented by Products. It passes when the lists match exactly. Duplicate names can hide missing Product coverage; use IDs when names are not unique. |
| Applies To | When a count query matches |
| Applies When (Count Query) | SELECT COUNT() FROM Opportunity WHERE AccountId = {!record. |
| Count Must Be | Greater than |
| Count Value | 0 |
| Message When Not Applicable | {!record. |
| Source Query | SELECT Name FROM Opportunity WHERE AccountId = {!record. |
| Source Query Field | Name |
| How To Read Query Results | Compare as lists |
| Comparison Operator | Lists match exactly |
| Comparison Query | SELECT Opportunity. |
| Comparison Query Field | Opportunity. |
| If Query Finds No Records | Fail |
| If Field Value Is Empty | Ignore the record |
| Display: Found Text | {!rhcResult. |
| Display: Expected Text | {!rhcResult. |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | One or more open Opportunities on {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Review products for {!record. |
| Action URL | /lightning/r/Account/{!record. |
Apex Check
Section titled “Apex Check”This Check runs AccountHasRecentActivityCheck, the Apex class that installs with the package. The
class adds its own message, fix text, and Open account link on the card, which replace the
Message When Failed, Fix Message, and action fields shown here; those fields remain the
fallback. See Check that an Account has recent activity.
Check 250: Account activity meets the 60-day cadence
Section titled “Check 250: Account activity meets the 60-day cadence”Label: Example: Verified engagement cadence. Record Health Check Name: Example_Guide_Recent_Activity. Result on Acme Corporation: Pass. Two Tasks were completed on Acme in the last 60 days, which meets the minimum of two.
| Field | Value |
|---|---|
| Evaluation Type | Verify with Apex |
| Check Description | The 2.0.10 Apex example declares typed parameters, counts completed Tasks and Events during the last 60 days, and returns typed evidence and safe display guidance. It passes when at least two completed activities are recorded. |
| Applies To | All records |
| Apex Class | AccountHasRecentActivityCheck |
| Apex Parameters (JSON) | {"daysBack": 60, "minimumActivities": 2} |
| Display: Value Format | Text |
| Failure Severity | Warning |
| Message When Failed | Fewer than two completed activities are recorded for {!record. |
| Fix Message | For {!record. |
| Message When Unable To Evaluate | {!rhcCheck. |
| Action Label | Log an activity for {!record. |
| Action URL | /lightning/r/Task/new?defaultFieldValues=WhatId={!record. |
This installed Check uses /lightning/r/Task/new. Salesforce’s create pattern is
/lightning/o/Task/new; when you copy this Check, use
/lightning/o/Task/new?defaultFieldValues=WhatId={!record.Id} and test the link.
Test a Check in your org
Section titled “Test a Check in your org”Test each Check with the Salesforce access of the people who will use it.
| Result to prove | How to test it |
|---|---|
| Pass | Use an Account that meets the requirement and confirm the row shows Pass. |
| A failure | Change one value so the requirement is not met. Confirm the label, message, fix message, and link. |
| Skipped | For a Check with Applies To set, use an Account outside its scope and confirm the not-applicable message. |
| Unable to Check | In a sandbox, remove the test user’s access to one field the Check reads, run it, and restore the access afterward. |
| Sharing | Keep one related record hidden from the test user and confirm the result counts only records the user can see. |
Adapt the examples to your org
Section titled “Adapt the examples to your org”Before you copy a Check, answer the question for its order number.
| Order | Setting or requirement to consider |
|---|---|
| 10 | Which Type values describe your Account relationships? This example accepts any populated Type, including values added by your org. |
| 20 | Is either Phone or Website sufficient? This example checks presence, so decide separately whether format or reachability validation is needed. |
| 30 | Does centralized billing require the child address to match its parent? Define how to handle legitimate address differences; a missing parent skips. |
| 40 | Is one simultaneous high-priority Case the approved capacity, and should exceeding it be Critical for every Account segment? |
| 50 | Does the sales organization use Forecast Category Commit, and is one Commit deal per Account a useful requirement? |
| 60 | Should an Account with no open Cases Pass or Skip, and is Contact Name mandatory for every Case type and channel? |
| 70 | Is Case Description the approved place for customer impact, or does the org use another standard or custom Case field? |
| 80 | Confirm that all open Opportunities are user-owned and that Owner Active is readable by intended users. Define the approved transfer process for inactive owners. |
| 90 | Confirm the proposal Stage value, $25,000 floor, currency behavior, and whether blank Amount should be treated the same as an Amount below the floor. |
| 100 | Is one Decision Maker anywhere in open pipeline enough, or must every qualifying Opportunity have one? Confirm the exact Contact Role value. |
| 110 | Is either Email or Phone sufficient, and may the intended users read both fields for every Contact Role they can see? |
| 120 | Confirm the exact Technical Buyer Contact Role value and which Opportunity Stages require it. |
| 130 | Is 30 days long enough for meaningful Account-level Case volume, and should the comparison use all Cases or only selected Case types? |
| 140 | Must every won Opportunity have Amount, and how should migrated or confidential historical deals be handled? |
| 150 | Does Next Step contain the agreed customer action, or does the sales process store mutual actions elsewhere? |
| 160 | Does the organization consistently maintain Primary Campaign Source before proposal Stage, including Opportunities created without a Campaign? |
| 170 | Is 180 days the approved planning horizon for every sales motion, and should overdue Close Dates be reported separately from dates beyond the horizon? |
| 180 | Must every open Opportunity have a Contact Role, or only Opportunities at selected Stages? |
| 190 | Must every won Opportunity retain a primary Contact Role, including renewals, channel deals, and migrated history? |
| 200 | Confirm the 90-day period, currency handling, which open Stages count as replacement pipeline, and whether Amount is the approved measure of replaced value. |
| 210 | Is Opportunity Amount expected to equal Opportunity Product Total Price, or can services, taxes, adjustments, or manual pricing create approved differences? |
| 220 | Which Account segments require one Contact to connect open sales and service work? If separate Contacts are normal, deactivate or narrow this Check. |
| 230 | Must every priority service Contact appear on an open Opportunity, or is sales awareness recorded through Account Teams, notes, or another Salesforce relationship? |
| 240 | Does the sales process require Opportunity Products on every open Opportunity or only after a selected Stage? |
| 250 | Which Task and Event types count toward the cadence? The class counts closed Tasks and Events related to the Account, including future Events, but does not judge whether an activity was meaningful. |
Also identify every Flow, Apex class, report, integration, or saved reference that uses an existing Check Qualified API Name before changing an API name.