Config and Set Up Flashcards
Custom Fiscal Year
- Can be defined using custom periods and can be based on existing template or an existing template which can be modified
- Can use a different structure such as quarters
- Will impact forecasting, reports, and quotas
- If this type of year is enabled, it CANNOT be reverted back to a standard year
6 Things Default Locale configuration impacts
1.) Date
2.) Time
3.) Number
4.) Phone Number
5.) Name
6.) Address
Lightning App Navigation Bar
- Can be customized to fit the users’ needs
- Apps can be created and customized by navigating to ‘App Manager’ in Setup
- The items that are visible can be selected and rearranged, and the utility bar in the footer can be enabled by adding a utility item to the app
- The navigation bar color and logo can be customized for each Lightning app
- The app can be assigned to user Profiles
Search Personalization
- This type of search is customized based on factors such as recent user activity, geographic location where users work most often, and ownership
- Personalization is generally available for the following standard objects:
1.) Accounts
2.) Cases
3.) Contacts
4.) Leads
5.) Opportunities
6.) Tasks - Prioritizing specific results over others can make users more productive, which is both time and cost-efficient
6 Steps to creating a Custom List View
1.) Create and name a new list view or clone an existing list view
2.) Select the ‘List View Sharing’
3.) Add List View filters
4.) Select the fields to display
5.) Optionally, create a ‘List View’ chart
6.) Use Sharing Settings to adjust visibility if required
Charts
- Can be added to a list view
- Can be a vertical bar, horizontal bar, or donut
Custom Home Page
- Similar to Lightning App pages (they are NOT tied to a specific record)
- When these types of pages are activated for an app or an org default, they occupy the home tab and are the first page shown to the user when they navigate to an app
- The 6 steps to creating this type of page are:
1.) Create a new page or clone an existing Home page
2.) Select a standard or custom template
3.) Add components to the layout
4.) Optionally set component visibility
5.) Activate the Home page
6.) Set the page as Default for the Org, App, or for an App/Profile combination
Global Actions
- Can be created to perform any of the following:
1.) Creating a Standard Object record (Account, Campaign, Case, Contact, Contract, Event, Group, Lead, Opportunity, Question, Task)
2.) Creating a Custom Object record
3.) Logging a Call
4.) Sending an e-mail
5.) Displaying a Visualforce page
6.) Displaying a custom Canvas
7.) Launching a Lightning component - Can be added to any page that supports actions
- Available in places like the home page, and allows action types such as creating a record or logging a call
- Has NO automatic relationship with any record
- Can be found on the (+) icon in the Salesforce header
- Allows creation of object records
Mobile Smart Actions
- Preconfigured just like Default actions per object
- This type of action appears as a single action element in the page layout editor
- For example, on the Account object, the actions include New Task, New Contact, New Opportunity, etc.
- These are displayed only in the Salesforce mobile app
Suggested Records
Lists up to 5 records that have a name that matches the search term
Lookup Search
- A feature that allows a user to search for a record of an object and associate it to a record of another object using a lookup field
Lookup Field
- Field that can be used to associate two records together in a relationship
- When a user types in this field, they see a dynamic list of suggested matches instantly
Lookup Filters
These types of filters can be used to restrict the valid values and lookup dialog results for relationship fields
Dependent Lookups
A lookup field that includes a lookup filter that references fields on the source object record
Search Layout
- This type of layout determines which fields users can view, filter on, and sort by on the search results page for global search and lookup search
- This type of layout for an object can be configured to select the fields that should be shown as columns on the search results page
- CAN be created for individual objects
- The following can be customized in this type of layout:
1.) Fields in a record’s instant results preview
2.) Fields that can be filtered
3.) Fields shown in a recommended result
4.) The secondary field in instant results - This type of layout can be configured from the Setup Menu or Object Manager for BOTH lookup and global search
- Standard Users CANNOT customize this type of layout
- Standard buttons aren’t available in these types of layouts
- These types of layouts can be accessed for a particular object from the Object Manager in Setup
- Encrypted fields CANNOT be filtered
3 Steps to Finalizing a User
1.) An account verification link sent via e-mail is clicked (by default, the link will expire after 7 days)
2.) A password is created
3.) A security question is created
‘Adding Multiple Users’ button
- Allows the creation of up to 10 multiple users at once
- The username will be the same as the email address when adding a user with this method
- All users will have the SAME user license assigned
- Individual user records will need to be edited after creation to choose further details
4 Levels of Security (from largest to smallest):
1.) Org Security Controls (ex: Login Access. Login Hours, IP Restrictions, and Password Policies are controlled here)
2.) Objects (ex: Account, Contact. Profiles and Permission Sets are controlled here)
3.) Object Record (ex: Salesforce. Org-wide Defaults, Role Hierarchy, Sharing, and Teams are controlled here)
4.) Fields on a Record (ex: Name, Type, Lead Source. Field-Level Security and Page Layouts are controlled here)
9 Changes Tracked by the Setup Audit Trail
1.) Tracked Changes
2.) Customization Changes
3.) Groups and Sharing
4.) Data Management
5.) E-mail Deliverability and Delivery
6.) Delegated Adminstrators
7.) Notification Changes
8.) Apex
9.) Lightning Components
Enhanced Domains
- Enables the use of the company’s unique ‘My Domain’ name on all URL’s across the org, including Experience Cloud sites, Salesforce sites, etc.
- It meets the latest browser requirements
- It is recommended for all Salesforce orgs and would be required by the Summer ‘22 release
- These Domains are available in Hyperforce orgs and in orgs that have a deployed ‘My Domain’ that is routed via the Salesforce Edge Network
- It is not going to be available in scratch and Developer Edition orgs
Public Groups
- This type of group can be used in an org and may contain specific users, users in particular roles or territories, users in roles and those below them in the hierarchy, and other ______ groups
- This type of group can be created for features such as Sharing Rules, Sharing Records, adding Users to a Content Library, and folder access
- ONLY Admins can create these types of groups
- Users in these types of groups can be made up of Users, Roles, Roles and Subordinates, Territories, & Territories and Subordinates
Org-Wide Defaults
- Determines access to other Users’ data for records they do NOT own
- Provides access to custom objects and MOST standard objects
- The 5 types of access are:
1.) Public Read/Write/Transfer
2.) Public Read/Write
3.) Public Read-Only
4.) Private
5.) Controlled by Parent - Changing these settings and increasing default access (ex: From Public Ready-Only to Public Read/Write) will take effect IMMEDIATELY)
- Changing these types of settings and decreasing default access in an existing org with significant data will take some time for Salesforce to recalculate User access
Sharing Rules
- Allows record access to be:
1.) Granted to other users based on their role, territory, public group membership, or manager groups, that they wouldn’t normally have access to according to the OWD settings
2.) Extended across the role hierarchy, these types of records owned by 1 role with users in another role at the same level
3.) Extended across the territory hierarchy, these types of records owned by users in a territory or with users in a territory - Access granted can be ‘Read Only’ or ‘Read/Write’
- For campaign members, this option can inherit from Lead and Contact rules or from the Campaign itself
- If this allows a User to view or edit certain records but the User’s Profile does not give them ‘Read’ access to the object, then the User will not be able to access the records associated with this option
Manual Sharing
- Allows users to share records with other users on a one-off basis
- With this option, records can be shared with other Users, Roles, Roles and Subordinates, Territories, Territories and Subordinates, Public Groups, Manager Groups or Manager Subordinate Groups
- Can be used to share specific records and manage record shares by clicking ‘Sharing’ on the record in Lightning Experience
- This option includes a Share Window, which allows managing who the record is shared with and sharing any associated records
- This is available only for Accounts, Opportunities, Cases, Contacts, Leads, and records of custom objects in Lightning Experience
- The access level for the record and any associated records can be Full Access, Read/Write, Read Only, and Private
- A User should be able to ______________ this record if they’re:
1.) The owner of the record
2.) Above the owner of the record in the role hierarchy
3.) a User that has full access (ex: a Superuser)
4.) Admin
Access options:
1.) Read/Write (view and edit, add associated records, notes and attachments)
2.) Read-Only (view, add associated records, cannot edit or add attachments or notes)
Permission Sets
- This can be assigned to a User to extend the User’s settings and permissions granted by their Profile
- Used to expand user privileges beyond what their Profile allows
- Add Permissions: Can allow be used to increase privileges, not remove
- Assign to Specific Users: Enables granting of specific permissions and settings at the User level
- Users can be assigned one or more ________________________
- Includes most Profile settings (ex: object and field permissions, tabs, apps, and Visualforce page access)
Permission Set Group
- Can be created which groups permission sets together and then assigns them to a User
- Mulitple __________ groups can also be assigned to a single User
- Permissions in this type of group can be disabled or “muted” by adding a ‘Muting _____________’
- Only 1 muting ___________ set is allowed in this type of group
Master-Detail Relationship
Tight parent-child relationship: child record inherits ownership and sharing from parent.
Deletion cascade: Deleting the parent also deletes the child.
Child record must have a parent (required field).
Roll-up summary fields are available on the parent to summarize child data.
Cannot re-parent a child record unless Allow reparenting is enabled.
Standard objects cannot be on the child side of a master-detail relationship.
Mobile App Configuration
Access via Salesforce Mobile App (iOS & Android).
Mobile app reflects most of the Lightning Experience UI.
Admins can use the Salesforce App Manager to configure:
Navigation menus.
Compact layouts.
Record pages.
Global actions.
Mobile Cards show important record info at the top of record pages.
Enable or disable mobile settings via Setup → Quick Find → Mobile.
Escalation Rules
Used in Case Management to automatically escalate cases based on criteria.
Must be activated to function.
Escalation rules contain:
Rule Entries (criteria and timing).
Escalation Actions (assignments, notifications).
Timers start based on when the case is created or modified.
Useful for enforcing SLA compliance.
Color Customization
Customize color settings in Themes and Branding.
Allows for:
Custom themes for different profiles.
Company logo and background color changes.
Brand consistency across the org.
Set default theme for entire org or per app.
Access via Setup → Quick Find → Themes and Branding.
Territories
It’s mainly used in Sales Cloud to help companies manage complex sales team structures and ensure that the right people are working the right accounts.
Align reps to accounts more flexibly than with just Role Hierarchy or Ownership.
Handle overlapping assignments (like two reps in different roles on the same account).
Assign multiple territories to one account.
Share access to records based on territory membership.
Territories do NOT change record ownership.
Users can belong to multiple territories.
You can assign accounts (not opportunities or contacts directly) to territories.
Opportunities can inherit territory assignment from their account.
Territory models can be in Planning or Active state.
