Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
34 Cards in this Set
- Front
- Back
Assign limited admin privileges to users in your org who aren’t administrators
|
Delegated Adminstration
|
|
3 objects exposed as read only in Force.com sites
|
Products, Pricebooks, and Ideas
|
|
Must be enabled to use Territory Management
|
Customizable Forecasting
|
|
Use this permission to allow a user to be an administrator of the territory hierarchy
|
“Manage Territories” permission
|
|
Only control the visibility of fields on detail and edit pages
|
Page Layouts
|
|
Specify the default level of access users have to each others’ records. First step in record level security
|
Organization Wide Settings.
|
|
Six standard Salesforce Profiles
|
Sales, Support, Solution, Marketing, Contracting, Read
|
|
T/F You can’t change the user license in a cloned permission set
|
True
|
|
Consists of a set of users. Can contain individual users, other groups, or the users in a particular role or territory
|
Group
|
|
Account sharing system that grants access to accounts based on the characteristics of the accounts
|
Territory Management
|
|
Flexible collection of accounts and users where the users have at least read access to the accounts, regardless of who owns the account
|
Territory
|
|
Create copies of your Salesforce org in separate environments. Use them for development, testing, and training, without compromising the data and applications in your production org
|
Sandbox
|
|
Intended for coding and testing in an isolated environment.Include a copy of your production org’s configuration (metadata)
|
Developer Sandbox
|
|
Sandboxes intended to be used for quality assurance tasks such as user acceptance testing, integration testing, and training
|
Partial Copy Sandbox
|
|
Intended as testing environments. Support performance testing, load testing, and staging. These environments are a replica of your production org, including all data—for example, object records and attachments—and metadata
|
Full Sandbox
|
|
Automatically move accounts and their associated opportunities and cases into territories based on any standard or custom account field
|
Assignment Rules
|
|
These objects have territory fields
|
Accounts, Opportunities, and Users
|
|
Can be associated with multiple territories
|
Accounts and Users
|
|
Can be associated with only one territory
|
Opportunities
|
|
Can convert a master-detail relationship to a lookup relationship as long as no _________ fields exist on the master object
|
Roll-up summary
|
|
You can convert a lookup relationship to a master-detail relationship, but only if the ______ field in all records contains a value
|
Lookup
|
|
Only these relationship are available for external objects
|
Lookup
|
|
Indirect lookup relationship fields can be created on _____ objects only
|
external
|
|
Allow data from the two related objects to be joined in one report.
|
Lookup Relationship
|
|
Allow data from three objects to be joined in one report: the master object, the detail object, plus one other lookup object. If the detail object has multiple lookup relationships, a separate report type is available based on each lookup
|
Master Detail Relationship
|
|
Provide two standard report types that join the master objects and the junction object
|
Many to Many Relationships
|
|
A group of tabs that works as a unit to provide application functionality
|
Application
|
|
Control which tabs you can see or hide, as well as which apps are available to you
|
Profiles
|
|
Closely links objects together such that the master record controls certain behaviors of the detail and subdetail record
|
Master Detail
|
|
Links two objects together. Similar to master-detail relationships, except they do not support sharing or roll-up summary fields
|
Lookup Relationships
|
|
Relationship links a child standard, custom, or external object to a parent external object.
|
External Lookup
|
|
Relationship links a child external object to a parent standard or custom object
|
Indirect Relationship
|
|
A special lookup relationship available for only the user object
|
Hierarchial
|
|
Lets you automate business processes by building flows and distributing them to the right users or systems.
|
Visual Workflow
|