1.
Best option to sum different objects - summary report
2.
Console: The
console is a tab that combines a list view and related records into one screen
with different frames so users have all the information they need when
interacting with Salesforce. With the console, users can quickly find, view,
and edit records such as cases, accounts, and contacts with fewer clicks and
without switching back and forth between screens. Administrators choose the
information displayed in the console to accommodate users’ varied and evolving
business needs. Console layouts define what objects are available to users in
the console’s list view frame. For example, if you want users to see list views
of cases and contacts in the console, then you would add both cases and
contacts to a console layout, and then assign that console layout to the appropriate
user profiles. A user can only view objects in the console’s list view frame if
those objects are added to the console layout to which
their
profile is assigned.
36.
System
Fields: Salesforce.com has the ability to set system fields through
the API. When you are migrating data from an external system, the API lets
customers set the CreatedBy, CreatedDate, LastModifiedByID, LastModifiedDate,
and a number of other fields on most objects that were previously read-only. By
setting these fields, records will appear to have been created at their
original created time from your old system. The objects you can edit audit
fields are: Account, Contact, Opportunity, Case, Task, Lead, Event, Custom
objects.
37.
Encrypted
Custom Fields: Encrypted custom fields are text fields that can contain
letters, numbers or symbols but are encrypted. The value of encrypted fields is
visible to users with “View Encrypted Data” permission.
To
enable encrypted fields for your organization, contact salesforce.com.
● Encrypted
fields are encrypted with 128-bit keys and use the AES (Advanced Encryption
Standard) algorithm.
● Encrypted
custom fields cannot be unique, an external ID, or have default values.
● Although
other text fields can contain up to 255 characters, encrypted text fields are
limited to 175 characters due to the encryption algorithm.
● Encrypted
fields are not available for use in filters such as list views, reports,
roll-up summary fields, and rule filters.
● Encrypted
fields cannot be used to define report criteria, but they can be included in
report results.
● Encrypted
fields are not searchable, but they can be included in search results.
● Encrypted
fields are not available in the following: Salesforce CRM Mobile, Force.com
Connect for Outlook, Force.com Connect for Lotus Notes, Force.com Connect
Offline, lead conversion, workflow rule criteria or formulas, formula fields,
outbound messages, default values, and Web-to-Lead and Web-to-Case forms.
● You can
use encrypted fields in email templates; however, the value is always masked regardless
of whether you have the “View Encrypted Data” permission.
● If you
have created encrypted custom fields, make sure your organization has secure
connections using SSL (Secure Sockets Layer) enabled. To enable this setting
for your organization, see Setting Session Security.
If
you have the “View Encrypted Data” permission and you grant login access to
another user, be aware that the other user will be able to see encrypted fields
unmasked (in plain text). To avoid this possibility, first clone your profile
and remove the “View Encrypted Data” permission from the cloned profile, then
assign yourself to the cloned profile before granting login access to the other
user. If you do not have the appropriate permissions to clone and change your
profile, contact your administrator for assistance.
Only
users with the “View Encrypted Data” permission can clone the value of an
encrypted field when cloning that record.
Encrypted
fields are editable regardless of whether the user has the “View Encrypted
Data” permission. Use validation rules, field-level security settings, or page
layout settings to prevent users from editing encrypted fields.
You
can still validate the values of encrypted fields using validation rules or
Apex scripts. Both works regardless of whether the user has the “View Encrypted
Data” permission. Data for encrypted fields in the Debug Log is masked.
Existing custom fields cannot be converted into encrypted fields nor can
encrypted fields be converted into another data type. To encrypt the values of
an existing (unencrypted) field, export the data, create an encrypted custom
field to store that data, and import that data into the new encrypted field.
Mask Type is not an input mask that ensures the data matches the Mask Type. Use
validation rules to ensure that the data entered matches the Mask Type
selected. Use encrypted custom fields only when government regulations require
it because they involve additional processing and have search-related
limitations.
Page Layouts:
a.
Page layouts for the user object only include custom fields,
custom links, S-controls, and Visualforce pages
b.
Tagging, related lists, custom buttons, and standard field
customizations are not included on page layouts for the user object
c.
Field level security is only available only for the custom
fields on User object
d.
Field level security is not available for the standard
fields on the User object
e.
You can define mini-page layout for the User object but
can’t add standard fields or related list
f.
Only Administrator can use the import wizard for Accounts,
Contacts, Leads, Solutions and custom objects
g.
Administrator has access to import into any field even if a
field is hidden or read only in the page layout or field level security setting
h.
Individual users can import only into the fields that are
accessible to them via their page layout or field level security settings
i.
In Personal, Group and Professional editions page layout
control which field user can access in related list, list views, reports,
connect offline, email and mail merge templates, custom links.
j.
In Enterprise, Unlimited and Developer editions, the access
is controlled by field level security
k.
When editing a Person Account page layout, if you add
shipping address next the billing address in the Address information section a
link will display on the person account edit page that lets you copy the
billing address into the shipping address. Also, an equivalent link appear if
you add other address to the Address information section
l.
Contact fields and related list are available on the Person Account
page layouts. However , contact custom links and custom
buttons are not available
m.
Some Items can only be moved to certain sections on the page
layout. For example you can drag a custom s-control to any field section on the
page layout, but not to a Related list section or Button section
Visual force:
n.
Visualforce uses a tag based markup language to give
developers more powerful way to build applications and customize the Salesforce
interface. With Visualforce, you can:
i.
Create custom user interfaces that easily leverages
standards Salesforce styles
ii.
Create custom user interfaces that completely replace the
Standard Salesforce Styles
iii.
Build wizard and other navigation patterns that uses data
specific rules for optimal , efficient application interaction
o.
Visual force is a framework that lets developers to build
sophisticated, custom user interfaces that can be hosted natively on the
force.com platform
p.
Visualforce framework includes a tag based markup language similar
to HTML
q.
In Visualforce markup language, each Visual force component
correspond to a course and fine grained user component such as related list,
page section or a field
r.
Developer can use Visualforce to create a Visual force page
definition. The page definition consist of 2 things:
i.
Visual force markup
ii.
Visual force controller
s.
Visual force markup: consists of Visualforce tags, HTML,
javascript or any web-enabled code
t.
Visualforce controller: is a set of instructions that
specify what happens when a user interacts with the component specified in the
associated visual force markup such as when user clicks on a button or links
u.
Controller also provides the data access that should be
displayed in a page and can modify component behavior
v.
Standard Controller: consists of the same functionality and
logic that is used for a standard Salesforce page. If you use a standard
controller, clicking on a Save button in a Visualforce page results in the same
behavior as clicking Save on the standard edit page
w.
Custom Controller: is a class written in Apex that
implements all of the page logic without leveraging a standard controller
x.
Like other
Apex classes, Custom controller also execute entirely in system mode in which
the object and field level permissions of the current user are ignored. You can
specify whether a user can execute a method in a custom controller based on the
user’s profile
y.
Controller
Extension: A controller Extension is a class written in Apex that adds
to or Overrides behavior in a Standard or custom controller. Extension let you
leverage the functionality of another controller while adding your own logic
39.
Standard
controller executes in User mode in which the permissions, field level
security and sharing rules of the current user are enforced
40.
Because standard controllers execute in user mode—in which
the permissions, field-level security, and sharing rules of the current user
are enforced—extending a standard controller lets you build a Visualforce page
that respects user permissions. Although
the extension class executes in system mode, the standard controller executes
in user mode. As with custom controllers, you can specify whether a user can
execute methods in a controller extension based on the user’s profile.
41.
Custom picklist can be controlling or dependent
42.
Standard picklist can only be the controlling
43.
Standrad picklist can not be dependent
44.
A dependent field works in conjuction with a controlling
field to filters its values. The value chosen in the controlling field effects
the values available in the dependent field
45.
The field that drives filtering is called as Controlling
field.
46.
Standard and Custom checkboxes can be the controlling field
47.
Standard and Custom picklist with at least 1 and less then
300 values can be the controlling field
48.
The field that has its value filtered is called as Dependent
field
49.
Custom picklist and multi-select picklists can only be the
dependent fields
50.
Universally Required:
a.
Always require a value in this field in order to save a
record
b.
Required across all record types
c.
Always display on edit page
51.
Universally Required only works in Custom fields
52.
Universally Required does not work in Standard fields
53.
Unique:
a.
Don’t allow duplicate values
b.
Treat “ABC” and “abc” as duplicate values (case insenstive)
c.
Treat “ABC” and “abc” as different values (case senstive)
54.
Textarea can’t be a unique field
55.
We can set the
External ID of a field only for the TEXT, NUMBER and EMAIL data type for
the custom fields. Means External ID can only be for custom fields of type
TEXT, NUMBER and EMAIL
56.
External IDs is available on all objects which support
custom fields
57.
User defined cross-referenced field
58.
Why it is important:
a.
Increases Report and API SOQL performance
b.
Used with Upsert to easily integrate app with other systems
59.
An object can have 3 external ID fields
60.
An external ID contains record IDs from a system outside of
Salesforce. You can match against this field during importing or integration,
or when using the upsert call. Also, external ID fields are indexed, so
selective filters on them should run quickly.
61.
Encrypted Fields: Encrypted fields allows for masking data
from all the users except those with “View Encrypted Data” permission. This is
provisioned feature and you must contact with Salesforce.com to enable it
62.
Encrypted custom fields can not be Unique fields
63.
Encrypted custom fields can not be External ID fields
64.
Encrypted custom fields can not have default values
65.
Encrypted fields can be modified regardless of whether the
user has “View Encrypted Data” permission
66.
How can we prevent user
to modify the Encrypted fields:
a.
Use validations rules, field level security setting or page
layout setting to prevent the user from editing encrypted fields
67.
Object Relationship:
a.
A relationship is a bi-directional association between two
object
b.
Relationship allows us to create links between one objects
to other
68.
Force.com platform support the following 4 types of relationship:
a.
Lookup relationship
b.
Master-detail relationship
c.
Many-to-Many relationship
d.
Self
69.
Lookup
Relationship:
a.
Creates a loosely typed relationship between two objects
b.
Child row is not automatically deleted when parent row is
deleted
c.
No inherited sharing and security. Means the child row does
not inherit the sharing and security from the parent record
d.
25 lookup relationships can be created per object. We can
create maximum 25 lookup on a record
e.
Lookup field data on child record is not necessarily
required. Means the Lookup field value can be null on child record
70.
Mater-Detail
relationship:
a.
Mater-Detail relationship closely links two objects together
such that the master record controls certain behavior of the detail record
b.
When a master record is deleted, the detail record is
automatically deleted
c.
Owner field on the Detail record is not available
d.
Owner field on the Detail record is set to the owner of the
Master record
e.
Owner of the Detail can not be different for Master and
Detail record
f.
The security setting for the master record controls the
detail record
g.
Same security and sharing setting are applied on Detail as
on the Master record
h.
The Master-Detail relationship field (which is the field
linking the two objects) is required on the Page Layout of the Detail record
i.
Only 2 Master-Detail relationship are allowed per object
71.
Many-To-Many
Relationship:
a.
Allow for the relationship of 2 objects in a Many-To-Many
fashion
b.
Implementing a Many-To-Many relationship requires a third
junction object
72.
Junction
object: When modeling a many to many relationship, you use a
junction object to connect the two object
a.
Junction object is a custom object with two master detail
relationships
b.
When creating a junction object, consider the following
things:
i.
Name the object with a label that indicates it’s purpose
ii.
Use the auto number data type
73.
What is a
Custom App: A custom application is a logical container for all the
objects, tabs, processes and services associated with a business function
a.
A force.com app consist of a name, description, an ordered
list of tabs, optionally a custom logo and default lending page
b.
Salesforce.com provides standard apps like Sales, Marketing,
Call Center
c.
Custom App display CustomForce logo by default
d.
You can insert your own logo, you need to upload it in to
the Document object as a JPG or GIF file. The logo size should be less then 20
KB size
e.
You can set your landing page from the Default Landing tab
drop down menu
74.
What is a
Custom Tab:
a.
A custom Tab is a user interface component, you create to
display custom object data or other web content embedded in the application
b.
There are 3 types of custom tabs:
i.
Custom Object Tab :: display the data of custom object in
user interface
ii.
Web Tab :: display any external web based application or web
page in a user interface
iii.
Visualforce Tab::Display any visual force page
c.
Universal Container wants to make sure that user will be
able to easily access the new custom objects they have created. They need to
create new custom tabs that will quickly guide the people
75.
Page
Layouts:
a.
Page Layout defines the organization of
i.
Fields
ii.
Custom Links
iii.
Visual force pages
iv.
Custom s-control
v.
Related Lists on an object detail page or edit page
b.
Page Layout customizations include
i.
Field locations
ii.
Page section customizations
iii.
Field property: Field property can be “read only, required”
c.
Page layout standard section names can not be modified for
standard page layouts
d.
Making a field required on a page layout or through
field-level security ensures users must enter a value
e.
If you make a user field universally required, you must
specify a default value for that field
f.
Use field-level security as the means to restrict users’
access to fields; then use page layouts primarily to organize detail and edit
pages within tabs. This reduces the number of page layouts for you to maintain
g.
Field-level security does not prevent searching on the
values in a field. If you do not want users to be able to search and retrieve
records that match a value in a field hidden by field-level security, contact
salesforce.com Customer Support for assistance with setting up your
organization to prevent unwanted access to those field values.
h.
Page layouts can specify whether a given field is required,
but the API does not enforce such layout-specific field restrictions or
validations in create() and update() calls.
It is up to the client application to enforce any such constraints, if
applicable
i.
Means if a field is set to required from page layout, the
API will not enforce the user to make it as required
j.
Record types can control which picklist values can be chosen
in a given record and which page layouts users with different profiles can see.
However, such rules that are configured and enforced in the Salesforce user
interface are not enforced in the API. For example, the API will not validate
whether the value in a picklist field is allowed per any record type
restrictions associated with the profile of the logged-in user. Similarly, the
API will not prevent a client application from adding data to a particular
field simply because that field does not appear in a layout associated with the
profile of the logged-in user
k.
When a custom object is created, a Tag object related to it
is also created. These object names are of the form: MyObjectName__Tag, similar to AccountTag and other standard object
tag objects.
l.
In the Salesforce user interface, you can mark a custom
field as required, and this is also enforced in the API. Every custom field has
a field isRequired, with a data type boolean. The
default value is false. If set to true, every request must supply a
value (or leave the current value) to this field. Otherwise, the request will
fail. Once the value is set to true, the next time the field is edited or
created, the validation will apply, and if there is no value supplied or
default value specified, the request will fail.
m.
To edit the isRequired field, you must log in as a
user with the "Customize Application" permission
.
76.
Workflows:
a.
Standardize the internal procedure and automated the
business processes
b.
Event based and time-dependent triggering engine
c.
Capabilities of workflow:
i.
Field updates: restricted to updates on source object only
ii.
Tasks and alerts
iii.
Outbound messaging
iv.
Approval Process
v.
More sophisticated workflows may require use of API
d.
Workflow rules are automated processes that trigger criteria
based on your business requirements
e.
Workflow have two parts:
i.
Rule criteria: which records should trigger the rule
ii.
Workflow actions: what should happen once the rule is
triggered
f.
Each workflow rule consist of the following:
i.
Criteria that cause Salesforce to apply the workflow rule.
ii.
Immediate actions that execute when a record matches the
criteria. For example, Salesforce can automatically send an email that notifies
the account team when a new high-value opportunity is created
iii.
Time-dependent actions that Salesforce queues when a record
matches the criteria, and executes according to time triggers. For example,
Salesforce can automatically send an email reminder to the account team if a
high-value opportunity is still open ten days before the close date.
g.
Workflow
Evaluate Criteria:
i.
When a record is created, or when a record is edited and did
not previously meet the rule criteria
ii.
Only when a record is created
iii.
Every time a record is created or edited
h.
Immediate
Workflow Actions:
i.
New Task
ii.
New Email Alert
iii.
New Field update
iv.
New outbound message
v.
Select existing action
i.
You can’t add a time-dependent workflow action for “Every
time a record is created or edited” evaluation criteria
j.
For Email Alert action the Recipient type can be the following items:
i.
User
ii.
Creater (record creator)
iii.
Owner
iv.
User
v.
Public groups
vi.
Role and subordinates
vii.
Roles and internal subordinates etc..
k.
For Email Alert action we can enter 5 email addresses to be
notified in the Additional emails
l.
You cannot add time-dependent workflow actions on an active
rule. You must de-active that rule and then add the time trigger
77.
Formula
Fields: A read-only field that derives its value from a formula
expression you define. The formula field is updated when any of the source
fields change.
a.
The output type for a formula field can of these types:
i.
Currency (18 decimal places)
ii.
Date
iii.
Date/Time
iv.
Number (18 decimal places)
v.
Percent (18 decimal places)
vi.
Text
b.
Formula field help text displays on the detail page
c.
Formula field are not displayed on Edit page and auto
calculated
d.
Smart custom fields that can be used to build business
specific calculations using simple wizards and excel like formula calculations
e.
Supported on standard and custom objects
f.
Formula fields can reference standard, custom or other
formula fields
g.
Formula fields can reference fields on related objects
h.
Cross
object formula fields:
i.
Cross objects formula fields enables you to incorporate the
merge fields from multiple objects for calculations and display
ii.
Create formula that reference fields on parent or
grandparent objects up to 5 level
iii.
The cross object formula fields can refer the objects up to
5 levels
iv.
This enables to display fields from related objects on
detail pages
v.
Use a simple wizard to browse across objects and insert
fields in formula
i.
Formula fields only display on detail pages
No comments:
Post a Comment