Quick Start Guide

This walkthrough takes you end-to-end through building, running, and verifying your first Decision Rule. The example is intentionally simple — flag accounts whose annual revenue is over $1 million — so you can focus on learning how DRE works rather than the business logic.

By the end of this guide, you will have:

• ✅ Built a working Decision Rule

• ✅ Run it on a real Salesforce record

• ✅ Seen the result on the record page

• ✅ Understood the Result Summary and Result Items

Time required: About 10 minutes You'll need: DRE Admin access, an Account record with Annual Revenue filled in

Before You Start

Make sure you've completed the Ready-to-Build Checklist on the main Getting Started page. The key things:

• You have DRE Admin access (not Standard)

• You're working in a Sandbox or test environment

• You can see the Decision Rules app in Salesforce

• You have an Account record you can safely experiment on, ideally with Annual Revenue over $1M

What You'll Build

A rule that does this:

"For any Account where the Annual Revenue is greater than $1 million, mark the description as 'High Revenue Account.'"

In DRE terms:

Simple. Let's build it.

Step 1 — Open the Decision Rules App

1. In Salesforce, click the App Launcher (the 9-dot grid icon, top left).

2. Type Decision Rules in the search box.

3. Click to open the app.

4. Click the Decision Rules tab in the navigation bar.

5. Click the New button to start creating a rule.

You should now see the rule creation screen.

Step 2 — Name Your Rule

DRE will first ask for some basics.

1. Decision Rule Name: Type Quick Start - High Revenue Account

   💡 Why this name? Clear names matter. When your team has many rules, "Quick Start - High Revenue Account" is far easier to find than "Rule 1."

2. Salesforce Object: Choose Account from the dropdown.

   ℹ️ Don't see Account in the dropdown? Your admin needs to add it to the list of available objects. Ask them to update the RuleObjectFilterOptions setting.

3. Click Next.

Step 3 — Add Your Condition

Conditions are the "if" part of your rule. You'll add one condition now.

Fill in the condition fields:

Click Save Condition.

💡 About operators: DRE supports the usual comparisons — equals, not equals, greater than, less than, contains, in a list, and more. For this rule, we just need greater than.

ℹ️ About field names: Salesforce fields have two names — a friendly label ("Annual Revenue") and a technical API name ("AnnualRevenue"). DRE uses the API name. If you're not sure of a field's API name, ask your admin or check the field details in Setup → Object Manager.

You should now see your condition listed. Click Next to move on.

Step 4 — Add Your Action

Actions are the "then" part of your rule. You'll add one action now.

Fill in the action fields:

Click Save Action.

💡 About Outcome Event: This tells DRE when to run the action. Passed = only when the rule passes. Failed = only when it fails. All = every time, regardless. For learning, Passed is the simplest.

💡 About Assignment Types: Pre-Defined Static Value writes a fixed value you specify. There are also options to compute values (e.g., copy a value from another field, or use a formula) — but for your first rule, stick with static.

You should now see your action listed. Click Next to move on.

Step 5 — Finalize and Activate

Almost done.

1. Review your rule: You should see one condition and one action listed.

2. Conditional Logic: Choose AND.

   ℹ️ Since you only have one condition, AND and OR behave identically here. AND is the safer default when you eventually add more conditions.

3. isActive: Make sure this is set to true (checked or "yes" — whichever your version shows). An inactive rule won't run.

4. Click Submit.

Congratulations — your rule is built and active. 🎉

Step 6 — Run Your Rule on a Real Record

Time to try it.

6.1 Open a Test Account

1. Click the Accounts tab.

2. Open an Account where Annual Revenue has a value filled in.

3. If you have a choice, pick one where you know the revenue is over $1M — that way the rule should clearly pass.

💡 Best practice: Try both! Run it once on an Account with revenue over $1M, then again on one under $1M. Seeing both Pass and Fail outcomes will help you understand DRE.

6.2 Click the Run Button

1. Look at the top-right of the record page — you should see action buttons in a row.

2. Click Run Decision Rule.

3. A small window will open. Select Quick Start - High Revenue Account from the dropdown.

4. Click Execute.

DRE will run your rule. It usually takes 2–5 seconds.

6.3 See What Happened

After a moment, you'll see results on the record page itself. Look for the Decision Rule Outcome panel (your admin placed this during setup).

You should see:

• Outcome: Passed (if revenue was over $1M) or Failed (if not)

• Status: Completed

• A list showing the condition that was evaluated and its result

6.4 Check the Description Field

If the rule Passed:

1. Scroll to the Description field on the Account.

2. It should now say: "Flagged by Quick Start rule — High Revenue Account"

3. 🎉 It worked. Your rule successfully evaluated the data and updated the record.

If the rule Failed (Annual Revenue was not over $1M):

1. The Description field will be unchanged.

2. That's correct — you set your action to run only on Passed, so nothing happened.

3. Try again on a different account with revenue over $1M to see the Pass behavior.

Step 7 — Look at the Result Records (Optional but Worth It)

Every time a rule runs, DRE creates records you can look at later. This is your audit trail — useful for compliance, reporting, and answering "why did this happen?" questions.

See the Result Summary

1. Click the App Launcher and search for Decision Rule Result Summary.

2. Open the most recent record — it's from the run you just did.

3. You'll see:

   • Which Account it ran on

   • The overall outcome (Passed, Failed, Unknown)

   • When it ran

   • How many conditions were evaluated and how many passed

See the Result Items

1. From the Result Summary record, scroll down to the Decision Rule Result Items related list.

2. Each row is one condition that was evaluated.

3. You'll see exactly what value was checked, what it was compared to, and whether it passed or failed.

This level of detail is one of DRE's most valuable features. Anytime someone asks "why did this rule decide that?" — open the Result Items and you'll have a clear answer.

What You Just Learned

In 10 minutes, you've covered the fundamentals:

✅ How to create a Decision Rule — name it, pick the object, save ✅ How conditions work — pick a field, an operator, a value to compare ✅ How actions work — choose when to run (Outcome Event) and what to do ✅ How to run a rule manually — click the button, pick the rule, execute ✅ How to read the results — on-page panel + Result Summary + Result Items

Everything else in DRE builds on these basics. You now know the core mechanics.

Something Didn't Work?

The most common first-time problems and how to fix them:

If something else goes wrong, send a screenshot to your admin or to support@cloudmaveninc.com.

Clean Up (Optional)

If you'd rather not leave a "Quick Start" rule sitting in your org:

1. Open Decision Rules and find Quick Start - High Revenue Account.

2. Click Edit and change isActive to false.

   💡 Why deactivate instead of delete? Deactivating preserves the rule and your test history. You can reactivate later, or use it as a template for your real rules.

3. To remove it completely, click Delete — but only if your admin's audit settings allow it.

Where to Go Next

Now that you've built your first rule, here's where to go:

🎯 If You Want a Real-World Example

➡️ Sample Workflow — Loan / Credit Decisioning A complete multi-rule workflow showing how to chain rules together for a realistic business process.

📘 If You Want to Build Production Rules

➡️ User Guide In-depth coverage of conditions, actions, operators, and rule patterns.

✅ If You Want Tips From Experienced Users

➡️ Best Practices What to do and what to avoid.

💡 If You're Looking for Inspiration

➡️ Use Cases Examples of how other teams use DRE.