Force.com Platform Fundamentals

Preface
Introducing the Force.com Platform
About the Sample Recruiting App
Reviewing Database Concepts
Building a Simple App
Enhancing the Simple App with Advanced Fields, Data Validation, and Page Layouts
Adding Advanced Fields
Introducing Validation Rules
Check It Out in Mobile
Introducing Page Layouts
Becoming Familiar with the Page Layout Editor
Try It Out: Group Fields into a New Section
Try It Out: Add Spaces Between Fields
Try It Out: Edit Field Properties
Look at What We've Done
Taking Your Page Layouts Mobile
Introducing Compact Layouts
Expanding the Simple App Using Relationships
Securing and Sharing Data
Collaborating with Chatter
Automating Business Processes
Analyzing Data with Reports and Dashboards
Moving Beyond Point-and-Click App Development
Learning More
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Try It Out: Edit Field Properties

We just used the page layout editor to organize our Position page layout in a logical, easy-to-read fashion, but the page layout editor lets us do more than design the presentation of data—we can also use it to help determine which fields are required, and which fields are read-only:
  • If a field is required, a user won't be able to create a position record without specifying a value.
  • If a field is read-only, a user who views a position record edit page won't be able to change its value.
Required fields are denoted with a red asterisk (Red asterisk), while read-only fields are denoted with a lock icon (Lock icon).

Although we can make these changes on the page layout, don't forget our earlier warning! Page layouts should never be used as the sole means to restrict access to sensitive data that a user shouldn't view or edit. That's because page layouts control only a record's edit and detail pages; they don't control access to those fields in any other part of the platform.

Warning

At this point, we don't have any fields that need to be read-only, but we do want to make sure that the salary range is always defined for each position, so let's make the Min Pay and Max Pay fields required. Once we do that, we'll be all done with our Position object!

To make the Min Pay and Max Pay fields required, we need to edit the properties of each field:

  1. In the page layout editor, double-click the Min Pay field, or select the wrench icon (Wrench icon) next to the field name.

This popup window allows us to edit the Min Pay field's properties. We can set the field to either read-only or required. If we didn't want a user to see the Min Pay field at all, we could simply drag it off the layout and onto the palette. We want to make sure it stays visible for right now, so let's leave it in its current spot.

  1. Select the Required checkbox, and click OK.
  2. Repeat these steps for the Max Pay field.
  3. Click Save to finish customizing the page layout.

Hooray! We're all done with our Position object's page layout.