Every characteristic referenced on an object references a characteristic
type. The characteristic type controls the validity of the information
entered by a user when they enter the characteristic's values. For
example, if you have a characteristic type on user called "skills",
the information you setup on this characteristic type controls the
valid values that may be specified by a user when defining another
user's skills.
When you setup a characteristic type, you must classify it as one
of the following categories:
-
Predefined value. When you setup a characteristic of this
type, you define the individual valid values that may be entered by
a user. A good example of such a characteristic type would be one
on User to define one or more predefined skills for that user. The
valid values for this characteristic type would be defined in a discreet
list.
-
Ad hoc value. Characteristics of this type do not have
their valid values defined in a discreet list because the possible
values are infinite. Good examples of such a characteristic type would
be ones used to define a user's birth date or their mother's maiden
name. Optionally, you can plug-in an algorithm on such a characteristic
type to validate the value entered by the user. For example, you can
plug-in an algorithm on a characteristic type to ensure the value
entered is a date.
-
Foreign key value. Characteristics of this type have their
valid values defined in another table. For example perhaps you want
to link a user to a table where User is not already a foreign key.
Valid values for this type of characteristic would be defined on the
user table. Please be aware of the following in respect of characteristics
of this type:
-
Before you can create a characteristic of this type, information
about the table that contains the valid values must be defined on
the foreign key reference table.
-
The referenced table does not have to be a table within the
system.
-
Not all entities that support characteristics support foreign
key characteristics. Refer to the data dictionary to identify the
entities that include the foreign key characteristic columns.
-
File Location. Characteristics of this type contain a
URL. The URL can point to a file or any web site. Characteristics
of this type might be useful to hold references to documentation /
images associated with a given entity. For example, the image of a
letter sent to you by one of your customers could be referenced as
a file location characteristic on a customer contact entry. When such
a characteristic is defined on an entity, a button can be used to
open the URL in a separate browser window. Note that for references
to a file, the recommendation is to use the Attachment functionality
to link documents to an object rather than a characteristic type of
File Location. Refer to Attachment Overview for more information.
The documentation related to file location remains for upgrade purposes.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]