Print      Open PDF Version of Online Help


Previous Topic

Next Topic

Customizing the Audit Trail

You can specify which fields are tracked in the audit trail for the Opportunity and Service request, as well as Fund and Fund Request record types, if those vertical record types are set up for your company. When there are changes to audited fields, an audit trail record is generated.

The auditing of opportunities and service requests is enabled by default for all companies. However, auditing of funds and fund requests might need to be set up for your company.

For each of the record types, you can specify that other fields, both standard and custom fields, are audited. However, there is a maximum number of audited fields allowed for your company across all record types. If you need to increase the maximum number of audited fields, contact Customer Care. The total number of audited fields available, and the number available for the different record types is displayed on the Audited Fields page.

For each of the record types, certain fields are audited by default, as shown in the table. However, the set of fields that are audited by default for Fund and Fund Request record types depends on whether your company used the application before Release 14 and whether these record types were set up for your company as follows:

  • Pre-Release 14 company with Funds and Fund Requests set up. The default set of fields are audited as shown in the table.
  • Pre-Release 14 company without Funds and Fund Requests set up. No fields are audited for funds and fund requests.
  • Post-Release 14 company with Funds and Fund Request set up. No fields are audited by default for these record types. You must select which fields are audited for funds and fund requests.
  • Post-Release 14 company without Funds and Fund Requests set up. No fields are audited for funds and fund requests.

This strategy ensures that if your company does not use the Fund and Fund Request record types, the default fields listed in the table do not count towards your maximum number of auditable fields. You can allocate the number of fields audited by default for the Fund and Fund Request record types between the Opportunity and Service Request record types.

Record Type

Audited Fields

Opportunity

Revenue, Close Date, Forecast, Sales Stage, Probability, Owner

Service Request

Subject, Description, Area, Cause, Type, Source, Priority, Status, Owner

Fund

Status, Partner, Target Amount, Owner (pre-Release 14 companies only)

Fund Request

Claim Approved Amount, Claim Requested Amount, Claim Decision Date, Due Date, Fund, Pre-approval Decision Date, Pre-approval Requested Amount, Pre-approved amount, Status, Owner (pre-Release 14 companies only)

The following considerations apply to fields regarding auditing:

  • For foreign key fields, the name (not the ID) is stored and displayed in the audit trail. For example, if the Account relation on Opportunity is audited, the audit trail displays the account name instead of the Row ID.
  • No address fields are available for any of the auditable record types (Opportunity, Service Request, Fund, Fund Request).
  • Picklist fields show the user's language dependent values (LDVs).
  • ID columns that are not displayed on the layouts are not available for auditing.

Before you begin. To perform this procedure, your role must include the Customize Application privilege and the Administer Field Audit privilege.

To customize the audit trail for a record type

  1. In the upper-right corner of any page, click the Admin global link.
  2. Click the Application Customization link.
  3. In the record type Application Customization page, click the record type Field Audit Setup link.
  4. In the Audit Field Setup page, move fields from the Available fields list to the Audited Fields list as required.

    An error message is displayed of you exceed the company limit.

    The Available Fields list contains all the standard and custom fields for the record type that are not already audited.

  5. Click Save.

    Auditing of a field becomes effective immediately after it is enabled.


Published 05/11/2007