Skip to content

admin_cert_object_manager_and_lightning_app_builder.md

Latest commit

 

History

History
227 lines (136 loc) · 11 KB

admin_cert_object_manager_and_lightning_app_builder.md

File metadata and controls

227 lines (136 loc) · 11 KB
Raw

Object Manager and Lightning App Builder: 20%

This topic has 3 sub-topics

  1. Describe the standard object architecture and relationship model. It includes topics e.g.; Standard Objects, Parent-Child Relationship, Master-Detail Relationship, Lookup Relationship, Junction Objects and Relationship, and Record Types.

  2. Create, delete and customize fields and page layouts on standard and custom objects and know the implications of deleting fields. It's all about fields and page layouts.

  3. Assign page layout, record types, and business processes based on any given scenario for custom and standard objects.

Standard Objects

Common Standard Object includes

Object Description
Account Has 1:N relationship with cases and opportunities. Products and Campaigns are not related to it.
Contact
Lead
Opportunity
Case Customer Feedback, inquiry, or complaint.
Campaign Aimed at Campaign Members
Products Related to opportunities
Solution A regularly occurring customer problem that has the solution
Work Order Tracks the different tasks that need to be taken out on a product

Master-Detail Relationship

  • In this relationship, if you delete the master record, it automatically deletes the associated detail records.

  • You can't give a new master to a detailed record.- There is no owner field in the detail record, instead, it's shared from the master record because the owner of the master record also owns the detailed record.

  • Detailed records can't have Sharing Rules, Manual Sharing, and Queues, because these require an owner field, which detail records don't have.

  • Detailed records inherit the Sharing and security settings of the master record.

  • Master relationship field is required on all detailed page layouts (Permanent lookup field).- A custom object can have up to 2 master-detail relationships.

Roll-Up Summary Fields

  • These fields are only allowed on master records in a master-detailed relationship. Example fields includes

  1. Count: count the number of related detail records for any given master record.

  2. Sum: Accumulates different fields in the detailed records to be displayed on master record page.

Lookup Relationships

Features of Lookup Relationship include

  1. Loosely coupled
  2. No roll-up summary fields.
  3. Don't share security settings.
  4. When you try to change the lookup relationship to the master-detail relationship, make sure every detailed object has a lookup field for the master object.
  5. We can also create a dependent lookup field, a lookup field with a filter => You can only lookup objects or related records which satisfy the filter condition.
  • You always create a field on the N side of the 1:N relationship e.g.; 1 Provider can have N patients.
  • On the 1 side, the related list is maintained.

Junction Relationship Object

  • This object is created to be used in a many-to-many relationship.

  • This object will have 2 master-detail relationships.

Customization Relationship

Accounts and Contacts Relationship

Changing and Deleting Fields

Required Fields

  • If a field is a universally required field, it's automatically added to all page layouts.

  • Required field can't be hidden.

  • You can make text, number, and picklist fields as required.

  • They are immune to field security => even if the user doesn't have the right access to see this field, that user will be able to see it.

Picklists

  • Standard picklist values can be added, updated, and deleted.

  • Global Value Sets are set of picklist values to be set once and reused by custom picklist fields.

  • Master picklist is a complete list of picklist values taht can be used in a Record Type.

Validation Rules

They make sure that the data user has entered meets the specific rules you have set out before data is saved.

System validation rules check the following things.

  1. Layout Rules compliance.
  2. Required Fields.
  3. Valid Field Formats.
  4. Field Length (max/min)

Custom validation rules are set up by the user manually. You should be aware of following key validation terms.

  1. PRIORVALUE
  2. ISCHANGED

Cross Object Formula Field

  • It's a formula field that spans two related objects and references merge fields on those objects up to 10 levels/relationships away.

  • Formula fields are not editable on the page layout because data is calculated on the fly. Only the formula is stored in the page layout.

Page Layouts and Field Level Security

  • We can hide or visibility of a field in a number of ways e.g.; Page layouts and Field level security.

  • Field hidden using field-level security will not show up on 1. Page Layouts 2. Search Results 3. Related Lists 4. List Views 5. Reports.

  • Field is hidden using Page layout still available on 1. Reports 2. Search Results 3. List Views.

  • Page Layout can make a field read-only or required.

List Views and Search Layouts

  • Users can only fields in the List View they have access to. Field level security absolutely applies to List View.

  • User with Manage Public List Views permission either via profile or permission set, allows sharing to 1. The users themselves, 2. A group or Roles 3. Everybody

  • Users with the above permission can edit other public list views and add more filters to them.

  • Users without the above permission set can only make List View for themselves only.

  • Search Layouts are ordered groups of fields, that show up in search results for a particular record e.g.; 1. Lookup Dialogs 2. Search Results for an entire org 3. Related Lists

  • Search Layouts also control the recently viewed list views.

Lightning App Builder

  • You must activate a page for a user to view it, even if it has been saved.

  • You can assign a page to Org default, App Default, App, Record Type, or by Profile.

Page Layout Assignments

  • You can assign page layouts to different profiles without using record types if you like using page layout assignment.

Record Types

  • It's used to show different versions of one particular object.

  • There can be multiple reasons to do it. e.g.; For different users, you don't want to show all the fields, or maybe different users needed to see different fields of the same object.

  • Real-life examples include, you may be recording student library, accounts and courses information. For an accountant, library information maybe not useful.

  • Another example can be, in a hospital, you can refer a patient and get a referral of a patient. When you are getting referral, the referral number field should be editable because you will be entering the value you got. In-case you are creating referral for a patient, it should be autogenerated and noneditable.

  • when you use record type, you achieve the following 3 main things.

  1. Show Different page layouts.
  2. Show different picklist values.
  3. Show different business processes.

Assignment Rules

  • Automatically assigning records to a certain owner.

  • You can have multiple assignment rules and they are executed in order.

  • An assignment rule is executed when its rule is met. When one of the assignment rule met, other rules will not executed, just like if-else statement.

Business Processes

  • It's just a path you see on top of the object detail page e.g.; Opportunity (Sales Process), Cases (Support), Solution, and Lead.

  • It helps visually user to see the steps that the user should take to move to the next step.

  • Paths can be created on most Standard Objects, and are controlled by picklist values.

Queues

  • They are used to collect, prioritize, and share the workload among number of users.

  • We can prioritize the workload based certain filter or a condition without assigning it to a certain individual.

  • A Listview is automatically created when a queue is created for any object (Standard or custom)

  • Only members of a queue can accept records from that queue and take ownership.

References