Dev 401-008: Design Applications for Multiple Users' Experience Part 2
Universal Containers Scenario
1.At Universal Containers(UC), hiring managers in the IT and Engineering departments should only open positions in IT and Engineering departments.
2.Recruiters should be able to create positions for and department in the company.
3.UC needs to understand how to leverage page layouts and record types to enforce this behavior.
4.At Universal Containers(UC),hiring managers in IT and Engineering departments need to specify technical criteria desired for their candidates such as programming language or operating system.
5.Hiring managers in the other departments don't need or want to see these technical criteria fields when they fill out position details.
6.Recruiters need to be able to create all kinds of positions.
7.UC needs to understand how to use custom page layouts to model this behavior.
Record Types
1.Record types are used to tailors user interaction experience to specific business needs.
- Note: Record types only affect the way that data is displayed in the UI. it is not a form of sub-classing.
2.They can determine page layouts, in conjunction with profiles.
3.Or limit picklist options.
Module Review
1.What are the different types of licenses that are available?
CRM and SaleseForce.com Platform
2.What do profiles control?
User Interface/Permissions
3.What are the permissions that allow a System Administrator to manager the application?
Customize the permissions.
4.True of false:System Administrators can customize the permissions of both standard and custom profiles.
False.
5.Ture or False when creating a new profile, it's possible to copy over setting from an existing profile.
True.
6.If you remove access to an app from a profile, will uers in that profile still be able to see the tabs included in that application?
Yes.
7.If you hide a tab from a profile, will uses in tha profile be able to see records for that object?
Yes.
8.If you have two record types for an object, do you need to have two page layouts for that object?
Not necessary.
9.If a user doesn't have access to a specific type will they be able to see the records that have that record type.
Yes.
10.True of False: A field hidden by field-level security is still visible through API.
False.
11.When should you use field-level security?
12.When should you user records types?
13.When should you use page layout?