ADM 203 Flashcards
Cards from the course
What is the default user on a case
There are default case users. It’s different than others
Lookup vs. Master Detail
25 Lookups 2 M-D fields
not required-required
parent can be deleted vs. delete cascade
How do you build a many-to-many relationship with custom objects.
The preferred method is a detail with two masters
If the junction object has security requirements
should not use a detail with two masters
If two master-details relationships exists
first one built is primary. It controls tab color and look and feel from the primary master
what is the difference between roll-up summary field and formula field
Rollup Summary is actual data; Rollup summary only available on M-D relationships, there are some ‘fake’ summary fields on Account-Opps & Accounts-Campaigns
Why is it significant that modification of a detail record causes a save event on the parent?
validation rule on master could look at PRIORVALUE of a rollup summary field and throw an error
How deep can Master Detail relationships go?
3 levels deep
Talk about lookup Field filters (p89)
based on fields or values filtered values don't appear in search required or optional allow the admin to add help text can change error message
Custom Objects (p91)
have standard field names including ‘name’ field by default. You can change it.
not deployed allows only admin to see it
what can you do/not do if a custom object doesn’t have a tab
You can’t search for them
You can’t get to them directly
You can get to them via related lists
Can only be accessed with custom profiles
Lots of questions about M-D relationships
Come up with some
three types Custom Tabs
custom object
visual force
web tab
Custom tab rules
must have logo & color
exist at the View level of MVC
visibility set on profile level
records can still be visible through related lists, reports, dashboards and API (but still controlled with profiles)
Custom Apps
Allow you to use a logo control default tabs shown exist at MVC view level not security (use profiles) best practice is to have only one app
The list that is in the ‘Create new” upper left option of the user interface is determeined by?
the tabs visible in the App that the user is currently using. also in the same order
Describe the setup audit log
Metadata changes are recorded changes via: UI, API, Package installations, change sets who, a change was made, when records logging in as another user. saves for 6 mos
Automation (p105)
Add some of these to this side
debugs
debugging looks at automation
debug log is not on by default, needs to be turned on for specific monitoring for short periods of time.
stores 20 transactions
what are the 4 sandboxes
not in deck
developer - config but not data (only 200M data allowed to be added)
developer pro
partial data
*full data - a carbon copy of production (except user name). Including SF record IDs
What is ‘standard validation’?
p106
A term used mostly just by SF
Date must be date, picklists, lookups, numbers, required?
Custom validation
p106
Validation rules
apex triggers
Validation rules p106
conditional required fields
special formatting
prevent modification of records
use formula syntax, used to find error condition, not happy condition.
execute when record is saved, not on delete
are not an ‘ordered’ list
Rule functions with test questions
VLOOKUP( ) (e.g. state & zipcode lookups)
REGEX( ) regular expressions
ISCHANGED( )
What are custom settings?
A table (but not an object) in SF
heirarchical or list
Could be used to create a ‘disable triggers’ setting in the trigger logic to turn them off in an emergency
For the test - read the answers slowly
Read the questions slowly too and understand the scenario well.
Workflows
p109
send an email assign a task update a field outbound message (webservices type message) Any combination of these
Workflows
p109
Immediate or later
One object only
fire when record is saved
execution requires criteria to evaluate to true
Execute process or Workflows
Entry criteria -> workflow filter -> immediate actions -> time-based actions
Entry critera: on-create, on-create or update, oncreate or update when record did not previously meet filter criteria
Email limitations (not in book) There's a limit to "mass emails"
Emails from workflows do not count
Campaign emails do count
Emails triggered by Apex qualify as mass emails - trick is to use Apex make the determination, then use a work flow to make the email go out.
Workflow emails have limits of 1000/day/user
Emails to users don’t count, they’re not external
Using workflow to assign a task to a role has a unique behavior
It assigns it to the owner of the record. For use if you have one person assigned to a role, then if you put someone else in the role, it will continue to work.
Field update
p110
A field update can trigger another evaluation of the workflow. This nesting can only go down 5? levels.
Email templates
p112
Must be created before they can be used by workflows (duh)
can be sent manually, mass emails, through workflow
Letterhead
it’s clunky not overly useful
Organization wide addresses
Are aliases when using email addresses usually in the from: field to make it the reply to for an alias.
Workflows
Can have multiple time triggers in one flow
Time based Workflow
p114
If the time trigger interval has already past, SF will execute the trigger as if it happened.
What caused the trigger to fire must still be true at the time of the execute action. Every update of the record causes the trigger criteria is still valid and still applies.
First time based workflow
prompts you to create a default workflow user.
If the workflow fires, the actions are attributed to the workflow user if the triggering user is de-activated.
Time based workflow
will fire for only on create or on create and did not previously meet condition. makes sense because it would queue up multiple “fires” if it did it for every update.
Invalidating the criteria flushes the queue of the workflows actions.
Viewing time based workflow queue
search for ‘time based work flow’ under setup.
Approval processes
p118
Entry Criteria
Initial actions
Approval Steps
Final actions
Entry Criteria
is record eligible to be approved
Can fire any of the four actions a workflow can do
Any initial step
Any approval step
Any final step
can be routed to
managers
related team members
hardcoded users
can have parallel approval processes (multiple approvers at one time)
Look ups & Master Detail
Third relationship between objects is called heirarchical used in the user record. To allow you to build additional manager layers to support approval processes.
Users with modify all
can approve all steps even without being part of the approval process
When to approval processes start
When a user manually starts it.
The record is automatically locked.
Look into what ‘recall’ looks like
The “process visualizer” for approval processes
is the ‘view diagram’ button on the approval process. And you cannot edit the process from the process visualizer.
Not many test questions about approval process.
and the questions are generally sort of easy.
know the unanimous approval or first accept/reject.
An approval step could submit to a queue. These are always first response.
Know the user interface settings
Know how to get to it
Quick create - bypasses validation rules, should always be turned off, really. And these can’t be edited.
Enable separate loading of related lists is used when related lists get long.
Enhanced lists gives pagination and bulk edit from lists.
Enhanced profile list views
Search settings
p 122
Used to enhance productivity and user adoption
