|
Administering Oracle CRM On Demand > Business Process Management > Modification Tracking > Creating Modification Records Manually
Creating Modification Records Manually
Although the modification tracking feature enables Oracle CRM On Demand to write and track event records automatically, you can create event records manually. This feature might be useful if you want to record events that are external to Oracle CRM On Demand.
Before you begin. You must be signed in to Oracle CRM On Demand as administrator, and your role must include the Manage Modification Tracking privilege. If the Manage Modification Tracking privilege is not enabled for your company administrator’s role, then contact Oracle CRM On Demand Customer Care.
To create modification records manually
- In the upper-right corner of any page, click the Admin global link.
- In the Business Process Management section, click Modification Tracking.
- From the Modification Tracking List page, click New.
- Complete the fields as described in the following table, and then save the record.
|
|
Field
|
Description
|
Key Modification Tracking Information
|
Object Name
|
The name of the record type to which the tracking event applies, for example, Contact. The object name is usually a record type name, or it can be Picklist. (Required)
|
Object Id
|
The row identifier for the record type, typically assigned by Oracle CRM On Demand, for example, 1QA2-NX0XH. (Required)
|
Child Object Name
|
The name of the child record to which the tracking event applies, for example, Contact Address. The child record name appears only if it is applicable; that is, the object is modified as a child of another record in its view, for example, modifying an address in a contact view.
|
Child Row Id
|
The row identifier for the child record, which Oracle CRM On Demand assigns, for example, 1QA2-OBA65.
|
Event Name
|
The name of the event, for example, WriteRecordNew, when a new record is created. See the table of event name descriptions in About Modification Tracking Events for more information on the possible event names. (Required)
|
Modification Number
|
A counter for the number of times that the record has been modified. When a record is initially created, the modification number is set to 0 (zero) and incremented for each modification that is made to the record. (Required)
|
Record Type
|
The record type for which an administrator makes a configuration change that triggers the modification tracking feature. The Record Type field is populated only for a configuration change. An example of modification tracking for a configuration change is when an administrator edits a list of values in a picklist field. In this case, the Record Type field logs the name of the object to which the edited picklist field belongs.
|
Field Name
|
The Web service version 2.0 tag for a field when you edit a picklist for that field. For custom picklist fields, the Web service version 2.0 tag is the generic integration tag. This field is populated only for picklist edits.
|
Modified: Date
|
The date (MMDDYYY) and time (HH:MM:AM|PM) when the modification event has taken place.
|
Related Topics
For related information on modification tracking, see the following topics:
|
