Using Custom Objects

Oracle CRM On Demand Marketing provides support for custom objects, which enables you to model data that is not available in the standard application. Oracle Customer Care handles the creation of custom objects. You cannot create them directly in Oracle CRM On Demand Marketing. Custom objects have the following features:

One to many relationship with marketing contacts. Each marketing contact in Oracle CRM On Demand Marketing can be associated with multiple custom object rows for a given custom object. A custom object cannot be associated with entities other than Contact.

Import utility. Custom objects can be imported using the import utility. Imports can be one-time or recurring on a defined schedule.

Custom objects for list segmentation. Custom object data can be used for list segmentation. Custom objects appear under the list segmentation user interface as a separate profile.

Custom objects for response management. Custom object data can be used across all response management and queue assignment rules in regards to suppression, scoring, and queue assignment.

Custom objects with nurture campaigns. Custom object data can be used in conditions for workflow and adaptive campaigns.

To create a custom object, provide the following information to Oracle Customer Care:

Object name. The name of the custom object.

List of attributes. A list of custom object attributes. For each attribute, provide the following information.

Attribute name. The name of the attribute.

Data type. The data type of the attribute. The following table shows the available data types:

Data Type

Description

Text Area (255)

A text value up to 255 characters

Text Area (2000)

A text value up to 2000 characters

Number

A valid integer value

Decimal

A valid decimal value

Check box

A Boolean value

Percent

A valid numeric value

URL

A valid Web link

Date

A date value only

Date/Time

A timestamp value with the date and time

Picklist

A picklist with a predefined list of values

Mandatory flag. A flag indicating whether the attribute is mandatory

Primary key flag. A flag indicating whether the attribute is part of the custom object primary key