Salesforce General Certification Questions

Terms in this set (29)

D. Feed tracking

Because Feed tracking is used for tracking field updates and automatically post the updates made on the record to the user. Following is the details and image of the Feed tracking .

Feed Tracking
Feed tracking in Salesforce highlights changes to records by automatically posting them to the feed.
You decide which objects and fields you want to track with a simple point-and-click interface, and voila! The changes begin showing up in the feed. Feed tracking has many uses, but one of the most powerful is perhaps the visibility provided when you're on the go and using the Salesforce1 Mobile App. Feed tracking makes it easy to see what's changing anytime, anywhere.

You can track fields on the user, group, and topics objects, custom and external objects, and the following standard objects: account, article type, asset, campaign, case, contact, contract, dashboard, event, lead, opportunity, product, report, solution, and task.

If you enable feed tracking for certain objects, some fields are automatically tracked by default. Of course, you can modify which fields you want to track. Here are fields that are tracked by default when you enable feed tracking for:
Account: Account Name, Account Owner
Case: Case Owner, Priority, Status
Chatter Group: Allow Customers, Description, Group Access, Information Body, Information Title, Name, Owner Name
Contact: Account Name, Contact Owner, Name
Lead: Lead Owner, Lead Status, Name
Opportunity: Amount, Close Date, Opportunity Name, Opportunity Owner, Stage
Topic: Description
User: About Me, Address, E-mail, Manager, Phone, Title

Sharing rules and field-level security determine visibility of record changes in Chatter feeds. Users must have access permission to a record in order to see changes to that record in their feed.
A. Deleting a master record in a Master-Detail relationship deletes all related detail records.
C. Detail relationships can convert to a lookup relationship if no roll-up summary fields exist on the caere master object.
D. Master-Detail relationship cannot be created if the custom object on the detail side already contains data.

This is the Salesforce standard functionality for Master detail relationship. For detail justifications following is the description:

Master-detail-relationship :- A parent-child relationship in which the master object controls certain behaviors of the detail object:
a) When a record of the master object is deleted, its related detail records are also deleted.
b) 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.
c) The detail record inherits the sharing and security settings of its master record.
d) The master-detail relationship field is required on the page layout of the detail record.
e) By default, records can't be reparented in master-detail relationships. Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the Allow reparenting option in the master-detail relationship definition.

You can define master-detail relationships between custom objects or between a custom object and a standard object. However, the standard object cannot be on the detail side of a relationship with a custom object. In addition, you cannot create a master-detail relationship in which the User or Lead objects are the master.