As a Salesforce.com partner, Reside developers each have the task of becoming certified with SFDC. Having recently taken the 401 Developer Exam - I can say that it is a challenging exam. Here are some notes from my personal stack of flash cards to help you get prepared!
True/False
- Even if an app is visible, the app’s tabs won’t show up unless a profile has permissions to view the tabs & permissions to view the associated objects.
- All standard profiles get full access to a custom object when it is created.
- The dataloader cannot load more than 50k records @ a time.
- If a user is assigned to a standard profile, the only way to restrict acces is thru object-level security.
- Permissions on standard profiles are editable.
- Every workflow rule must be based on a single object you choose when you create the rule.
- When object vs. record-level permissions conflict, the most restrictive settings win.
- When creating email templates, you can use any merge fields and they will appear in your email.
- Sharing rules can be created for both master & detail objects in a Master/Detail relationship.
- Sharing rules & role hierarchies can never be stricter than our org-wide defaults.
- Users assigned to roles get access to the data of all users who fall directly beneath them in the hierarchy.
- A detail object record has its own org-wide sharing settings.
- All objects user same org-wide options (private, public – read/write, public – read only)
- If you completely hide a tab user can no longer see any of the records
- It’s ok to set the assignee of a workflow task to a role, instead of a user.
Listing…
- 2 “timing” actions of workflow
- 2 field types needed in a field dependency
- 3 options to select when doing tab settings & permissions
- 3 types of sandboxes
- 3 org-wide settings and when do you use them?
- 3 data types that can be external ids
- 3 types of reports
- 3 security levels on the platform (for data)
- 3 rule evaluation criteria
- 4 types of email templates
- 4 ways to set record level security
- 4 types of workflow
- 6 dashboard component types
- 7 key technologies behind the platform
- 8+ things that profiles control
General Questions
- Which data types are read only?
- What kinds of tabs can you have?
- How do you enable tags?
- How do sharing rules work on a junction object?
- How do you test time triggered workflow rules?
- Which dashboard would you use for a list? For trends over time?
- What can you do in the page layout of the user object?
- When should you use the data loader?
- When would you use an Apex trigger over a workflow rule?
- Who can change ownership of a record?
- Can a Master record have multiple Detail relationships?
- Queues are supported for which objects?
- What features do you get “out of the box”?
- How would you send an email to everyone in your org?
Define & Know
- All SFDC Data Types
- Analytic Snapshot
- Approval Processes
- Cascade Delete
- Collaborative Application
- Custom Tab
- Declarative Interface
- Default Workflow User
- Each Version of Salesforce.com
- Encrypted Fields
- External ID
- Field Dependencies
- Field Level Security
- Internationalize
- Junction Object
- Localize
- Look-up Relationship
- Manual Sharing
- Master-Detail Relationship
- Mini Page Layout
- Model View Controller
- Multitenant Architecture
- Object Level Security
- Org-Wide Defaults
- Outlier
- Profile
- Record Level Security
- Record Type
- Roles
- Sandbox
- Search Component
- Sharing Rules
Good Luck!
What Would Google Do?
Tuesday, November 17th, 2009Just finished reading Jeff Jarvis’ What Would Google Do? The books premise is how the Google business model can be used in nearly all aspects of business and society from airlines to religion. The key elements of a Google model are:
The first part of the book is a great read. While it does borrow on a number of other books and principles including the Cluetrain Manifesto, it continues to emphasize the nature of business today and how the influence of crowds and social networks of the Internet are changing the way businesses interact with their clients and how small voices can make tremendous impact on huge and entrenched industries.
While many of the examples seem far fetched or a matter of extreme optimism, it’s refreshing to think that companies will actually start to behave and act like human beings; and treat their customers as intelligent and thoughtful. Just think if we could eleiminate monopolies and oligarchies to achieve open competition, communication, ideas, and democracy across business, social structures, and politics? Now that is some juice worth drinking!
Tags: Google, Google Juice, Jeff Jarvis, social media, social network, What would Google Do?
Posted in Business Strategies, Communities / Portals, Innovation, Marketing, Opinion / Commentary, Social Networking, Web / Internet | No Comments »