Platform App Builder

1. Salesforce Fundamentals: 23%

Extend functionality with : AppExchange

Permissions : Permission set and profiles settings include built-in access settings for many
entities, like objects, fields, tabs, and Visualforce pages
However, permission sets and profiles don’t include access for some custom processes and apps.

Extend access to objects, records and fields with : Custom Permissions

Custom permissions let you define access checks that can be assigned to users via permission sets
or profiles, similar to how you assign user permissions and other access settings.
For example, you can define access checks in Apex that make a button on a Visualforce page
available only if a user has the appropriate custom permission.

Custom Permissions can be enabled in Permission Sets or in Profile.

2 Sharing Rule Types :

● Owner-Based Sharing Rules
● Criteria-Based : based on field values

Grant Access Using Hierarchies : Determine whether users have access to records they don’t
own, including records to which they don’t have sharing access, but someone below them in the
hierarchy does
● Grant Access Using Hierarchies option is always selected on standard objects and isn’t
editable.
● When Grant Access Using Hierarchies option is selected, View All Users option displays
group members and people above them in the hierarchies when a record is shared with them
using a sharing rule or manual sharing
● When Grant Access Using Hierarchies option is disabled, activities associated with a
custom object are still visible to users above the activity’s assignee in the role hierarchy.

Record access granted to users via sharing sets isn’t extended to their superiors in the role hierarchy.

Assignment Rules :
● Lead Assignment Rules : assign Leads to Users or Queues
● Case Assignment Rules : assign Cases to Users or put into Queues

For each rule type, only one rule can be in effect at any time.

Reports, Report Types, and Dashboards :

● Report Types : Tabular, Summary, Matrix, Joined
● Report types that can be converted to a Joined report : Tabular, Summary, Matrix
○ Cross filters are not supported in joined reports.
 ○ The Rows to Display filter is not supported in joined reports.
○ Bucket fields are not supported in joined reports.

● A dashboard filter can have up to 50 values.

● Each dashboard can have up to 20 components.

● Source to configure a reporting Snapshot : Tabular and Summary

● Highlight Total in report : Conditional highlighting of summary totals fields.

Social Accounts
You must login with your own personal social network account to work with social accounts.
Link: Link Twitter Profiles to Accounts, Contacts, and Leads

2. User Interface: 17%

App Launcher
Apps are accessed in Lightning Experience via the App Launcher.
In order to create an App Launcher component in Lightning an admin must contact Salesforce to have
the component activated for the Lightning App Builder.

Path
● Formerly known as Sales Path, Path Guide Users along the steps in a process.
● Available for Accounts, Leads, Opportunities, Campaigns, Contacts, Quotes, Contracts,
Fulfillment order, Orders, Service appointments, Work orders, Work order line items and
Custom Objects
● Path is supported on Lightning record pages in the new Salesforce mobile app.

Lightning Components framework

● It uses JavaScript on the client side and Apex on the server side.
● It uses events to communicate data between components.
● It uses a stateful client and stateless server architecture.
● The framework is client-side centric, while Visualforce relies on server calls.

Build:
● A standalone app.
● Components for the Salesforce app.
● Custom components that override and extend the Salesforce1 app.

Build with Lightning App Builder:

● Dashboard-Style App
 ● Apps optimized for a particular task
● Simple, single-page apps with drill-down capability

When activating a page in the Lightning app builder, what declarative options are available?
● Select a tab icon for the page.
● Select the tab visibility.
● Set the tab order in the navigation menu.

What kind of custom tabs can be included in an application?

● Lightning Page tab
● Visualforce tab
● Custom Object tab
● Web tab

Standard Lightning Components

● Filter List
● List view
● Recent Items
● Report Chart
● Rich Text
● Visualforce Page

Choose where to embed the dashboard. (Record pages don’t support embedded dashboards.)
● To embed a dashboard on an app page, select App Page.
● To embed a dashboard on the Home tab, select Home Page.

Global actions
● log call details
● create or update records
● send email

★ Global actions live on a special layout of their own, known as the global publisher layout.
★ If an object page layout isn’t customized with actions, the actions on those object record pages
are inherited from the global publisher layout.
★ Actions to create records for an object that is the detail object in a master-detail relationship
must be object-specific, not global.

To enable the Publisher Actions area on Page Layouts, navigate to Setup | Customize | Chatter |
Settings

Navigation menu item in the Salesforce Mobile App

Groups are not included in the selected list for the navigation menu.
3. Data Modeling and Management: 22%

Encrypted fields :
They are available in Validation Rules or Apex Scripts even if the user is not having the permission
"View Encrypted Data".

Notes on Changing Custom Field Types :

● You can only convert rich text area fields into long text area fields.
● Formula fields are special read-only fields that cannot be converted to any other data type.
Likewise, you cannot convert any other field type into a formula field.
● Backup data before converting in case of data loss.
● Auto-number fields can contain a maximum of 30 characters. Before converting a text custom
field into an auto-number field, change any records that contain more than 30 characters in that
field.
● Currently defined picklist values are retained when you change a picklist to a multi-select
picklist.
● You cannot change the data type of a custom field referenced by other items in Setup, like
Visualforce pages, Apex code, processes, or flows.
● If data is lost, any list view based on the custom field is deleted, and assignment and escalation
rules may be affected.
● You can’t change the data type of any custom field that is mapped for lead conversion.
● Existing custom fields cannot be converted into encrypted fields nor can encrypted fields be
converted into another data type.

★ You can convert a Text Area(Long) to Email, Phone, Text, Text Area or URL without data loss.
★ You can convert a Text to Auto Number without data loss

2 Types of lookup relationships available for external objects

● External lookup : links a child standard, custom, or external object to a parent external object.
○ Cascade-delete isn’t available for external object relationships.

● Indirect lookup : links a child external object to a parent standard or custom object.
○ Only objects that have a custom field with the External ID and Unique attributes are
available as parent objects in indirect lookup.

Cross-Object formula can reference fields from PARENT objects that are up to 10 relationships
away

Record Types :
● Display different picklist values
● Different Page Layouts

Field History Tracking ;

● Track changes on a specific field
● Enabled at the object level
 ● Can track field history on up to 20 fields

Rollup Summary Field :

● Number, Currency, Percentage, Date, and Date/Time are available when you select MIN/MAX
as the rollup type.
● Number, currency, and percent fields are available when you select SUM as the roll-up type.

● After you have created a roll-up summary field on an object, you cannot convert the object's
master-detail relationship into a lookup relationship

Which two will prevent a formula field from being referenced by a Roll-Up Summary field?
★ A cross-object workflow updating a field referenced by the formula field.
★ A cross-object field reference in the formula field.

★ Standard picklist fields can be controlling fields but not dependent fields.
★ Multi-select picklist fields can be dependent but not controlling

★ The Owner field on the detail object is not available and is automatically set to the owner of its
associated master record.

★ Custom objects on the detail side of a master-detail relationship cannot have sharing rules,
manual sharing, or queues, as these require the Owner field.

Auto-number field :
● You can specify a Starting number
● A display format : allows you to control the appearance

Schema Builder lets you add the following to your schema :

● Custom objects
● Lookup relationships
● Master-detail relationships : max 2 per objects
● All custom fields except: Geolocation

What are some capabilities of Schema Builder?

● Create Custom Objects and Fields
● Edit Field Properties : eg. Modify custom field help text on standard objects
● Manage Field Permissions
● Create lookup or master-detail object relationships
● View Object detail in a new window | View Page Layouts detail in a new window
● Showing selected objects on a page.
● You can delete the custom objects that you no longer need by using Schema Builder.
● Conveniently avoid “custom field clutter” by using Schema Builder to delete custom fields that
you no longer need.
Overriding Standard Buttons
Link: Considerations for Overriding Standard Buttons

● You can override buttons on the detail page but not the edit page of a record.
● You can only override these standard buttons: New, View, Edit, and Delete.
● You can’t relabel or relocate standard buttons on a record detail page.
● You can’t change buttons on lookup dialogs, reports, or tabs. However, you can change the
buttons on list view and search result layouts under search layouts.

4. Business Logic and Process Automation: 28%

What are the steps for creating a dynamic approval process?

● Create (user) lookup fields on the object being approved
● Create a custom object as an approval matrix
● Populate the approval matrix record
● Create Apex code to populate the user fields from the approval matrix record
● Create or update an approval process to utilize the new lookup fields.

Email approval request : Approvers must have the "API Enabled" system permission.

Workflow rules, Triggers

If any of the triggered workflow rules result in another field update that’s also enabled for workflow
rule re- evaluation, a domino effect occurs, and more workflow rules can be re-evaluated as a result of
the newly- triggered field update.
★ This cascade of workflow rule re-evaluation and triggering can happen up to five times after the
initial field update that started it.
★ Recursive triggers may cause your organization to exceed its limit for workflow time triggers per
hour.
★ Time-dependent actions aren’t executed for a reevaluated workflow rule.

● You can send outbound message with the help of workflow rules.
● Some Salesforce functionalities are ignored when processing field updates in workflow rules and
approval processes.
○ Field-level security
○ Record type picklist value assignments
○ Validation rules

● Field updates are not available on currency fields if the organization uses multi-currency.
●

Salesforce processes any rules in the following order :

1. Validation rules
2. Assignment rules
 3. Auto-response rules
4. Workflow rules (with immediate actions)
5. Escalation rules

Process Builder & Flow Deployment Consideration :

★ To deploy a process or flow as active your org must have 75% flow test coverage.
★ To calculate your org flow test coverage, salesforce divides the number of covered flows and
processes by the sum of the number of active processes and active autolaunched flow.

5. App Deployment: 10%

Sandbox templates : Specify Objects whose data should be replicated in Partial Copy, re-use when
creating a Partial Copy.

Change sets
● Change sets can only contain modifications you can make through the Setup menu.
● Change sets can only be sent between organizations that are affiliated with a production
organization.
● Account Team is unavailable in the change set.

Unmanaged package
● The components can be edited in the organization they are installed in.
● Tests are executed during deployment.
● The developer who created and uploaded the unmanaged package has no control over the
installed components, and can’t change or upgrade them.
● Unmanaged packages should not be used to migrate components from a sandbox to production
organization. Instead, use Change Sets.

*unmanaged cannot be upgraded*

*unmanaged have a version number*
*unmanaged namespace is removed*

Managed package
Managed package is a collection of components that are made available to other organisations
through the AppExchange.
★ Managed packages allow for property protection.
★ Managed packages have upgradable components.

Track changes in Production

★ Diff the metadata.
★ Use a change log request form.
★ Check the setup audit trail every week.