Foundation · Module 25

Advanced Metadata

Rules, Layouts & One-Click Actions

Three small admin tools that make a big difference: stop bad data from being saved, show the right fields to the right people, and put common actions just one click away.

⏱ ~15 min to complete80 pts available🏅 Badge: Metadata Power User

About & Business Case #

Why building objects and fields isn't always enough #

Tara Nair · Sales Admin

"Reps keep typing negative deal amounts by mistake. Support agents see 20 fields on a record when they only need 5. And logging a call takes four clicks, every single time."

An "object" is a type of record, like Contact or Opportunity. A "field" is one piece of information on it, like Email or Amount. Setting up objects and fields — the basic Metadata Engine — gets your data model in place.

But real teams need more than that. They need rules that catch bad entries before they're saved. They need screens built for each type of user. And they need shortcuts for the actions people do all day long.

What you'll be able to do

Get cleaner data, simpler screens for each role, and one-click shortcuts — all without writing a line of code.

Implementation #

Three tools that build on your objects and fields #

1 Validation Rules — stop bad data at the door #

A Validation Rule stops a record from being saved when something looks wrong, and shows an error message explaining why. You pick a field, a condition (like "equals", "is blank", or "less than"), and write the message people will see.

Create the ruleGo to Object Manager → Opportunity → Validation Rules → "New Rule". Criteria: Amount less than 0. Error Message: "Amount can't be negative."

2 Page Layouts — the right screen for each team #

A Page Layout controls which fields show up on a record's screen, and in what order. You can create more than one layout for the same object, and give different teams different layouts — so a Support agent's screen can look simpler than a Sales Admin's screen, even on the same kind of record.

Create the layoutGo to Object Manager → Opportunity → Page Layouts → "New Layout". Name it, then remove a field the Support team doesn't need to see.

Choose the panels and listsEverything on the record page comes from the layout. Use "+ Add built-in component…" for panels like Notes, Attachments, Activity or Record History, and the Related Lists tab to pick which lists (including Activity, Notes, Attachments and Record History) appear on the Related tab. Anything you leave out isn't loaded, so the page opens faster.

Pick the tabs and the quick-actions barIn the layout's Record Detail tab, turn tabs on or off (Opportunity also has Revenue Schedule and Quotes) and choose whether the quick-actions bar shows.

3 Quick Actions — one-click shortcuts #

A Quick Action is a button on a record's page that does one-click work: open a web address, create a related record (like logging a call as a Task), or trigger a workflow. You pick which object each button appears on — or leave that blank to show it everywhere.

Add the actionGo to Setup → Automation → Quick Actions → "New Action". Label: "Log a Call" · Object: Opportunity · Action Type: Create Record.

They work together

These three tools can stack on the same object. A Quick Action can create a record. That record is shown using a Page Layout. And a Validation Rule still checks it before it saves.

How to Use #

Day-to-day: reps and support agents #

Get stopped before a bad saveTry to save a negative Amount and you'll see the error message right away — no bad data gets through, and no admin has to clean it up later.

Use your own simpler screenSupport agents just see the Page Layout built for their role — fewer fields, less clutter, same record.

Log a call in one clickClick the "Log a Call" Quick Action instead of navigating to create a new Task manually.

Day-to-day: admins #

Add a new rule when you spot bad dataNoticed a new kind of mistake creeping in? Add another Validation Rule — no code, no deploy, live immediately.

Roll out a new layout to a new teamWhenever a new department joins, build them their own Page Layout instead of overwhelming them with every field.

What to try next

Look at the Metadata Engine trail if you haven't yet — these tools build directly on top of it.

Quiz #

Test what you learned #

1. What does a Validation Rule do?

It hides fields from certain users

It blocks saving a record when its condition is met, and shows an error message

2. Why would you create more than one Page Layout for the same object?

To show different fields to different profiles or record types

Because every object can only ever have one layout