Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a scenario, determine the appropriate data model.
0/14
Standard versus custom objects
Learn this conceptStandard object selection for business entities
Learn this conceptCustom object versus custom field
Learn this conceptPicklist versus related object
Learn this conceptMaster-detail versus lookup for parent-child models
Learn this conceptJunction objects for many-to-many relationships
Learn this conceptSelf-relationships on the same object
Learn this conceptHierarchical relationships on the User object
Learn this conceptSchema Builder for data model design
Learn this conceptRecord types for layouts, picklists, and processes
Learn this conceptRecord type assignment and the Master record type
Learn this conceptSales, support, lead, and solution processes
Learn this conceptCustom metadata types versus custom objects
Learn this conceptHierarchy versus list custom settings
Learn this conceptGiven a scenario, explain the capabilities of the various relationship types and the implications of each on record access, user interface, and reporting.
0/14
Given a scenario, determine the considerations when selecting or changing a field data type.
0/19
Given a scenario, determine the options and considerations when importing and exporting data, including the capabilities of external data sources.
0/9
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
Business processes let an org run more than one sales, support, lead, or solution lifecycle by showing different Stage or Status picklist values to different users. Each process is a named subset of values from one special field, then assigned to a record type so the right profiles get that lifecycle. Use them when teams follow different paths through the same object, not as a way to hide records.