Available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, Developer, and Database.com Editions
Standard Objects are not available in Database.com
You can select certain fields to track, and display the field history in the History related list of an object. The field history data is retained for up to 18 months. You can track the field history of custom objects and the history of the following standard objects.
Contract line items
Modifying any of these fields adds a new entry to the History related list. All entries include the date, time, nature of the change, and who made the change. Note that not all field types are available for history tracking. Certain changes, such as case escalations, are always tracked.
Additional field history increases beyond your current limits will require the purchase of the Field Audit Trail add-on, following the Spring ‘15 release. Once the add-on subscription is enabled, your field history storage will be changed to reflect the retention policy associated with the offering. If your org was created prior to June 2012 and your field history limits remain static, Salesforce commits to retain your field history without a limit. If your org was created after June 2012 and you decide not to purchase the add-on, field history will be retained for a maximum of 18 months.
Changes to fields with more than 255 characters are tracked as edited, and their old and new values are not recorded.
Tracked field values are not automatically translated; they display in the language in which they were made. For example, if a field is changed from Green to Verde, Verde is displayed no matter what a user’s language is, unless the field value has been translated into other languages via the Translation Workbench. This also applies to record types and picklist values.
Changes to custom field labels that have been translated via the Translation Workbench are shown in the locale of the user viewing the History related list. For example, if a custom field label is Red and translated into Spanish as Rojo, then a user with a Spanish locale will see the custom field label as Rojo. Otherwise, the user will see the custom field label as Red.
Changes to date fields, number fields, and standard fields are shown in the locale of the user viewing the History related list. For example, a date change to August 5, 2012 shows as 8/5/2012 for a user with the English (United States) locale, and as 5/8/2012 for a user with the English (United Kingdom) locale.
If a trigger causes a change on an object the current user doesn’t have permission to edit, that change is not tracked because field history honors the permissions of the current user.