CentraSite Documentation : CentraSite Administrator’s Guide : Object Type Management : Creating a New Type : Define Attributes for a Type : General Procedure : Defining Data Types
Defining Data Types
For the Data Type field, complete the type-specific options:
If you are adding this type of data type...
Do the following...
Classification
In the Taxonomy field, specify the taxonomy by which users will classify the asset.
Note:  
After you create a classification attribute, neither its Taxonomy option or its Default option can be changed.
Computed Attribute
When you choose this data type, you are indicating that the attribute value and the way it is rendered in a profile, will be generated using a Java plug-in.
Choose Java as the implementation type, to indicate that you are using a Java plug-in.
For more information, see Defining a Computed Attribute.
In the field File, specify the name of the archive file that contains the Java plug-in.
Note:  
When you define a computed attribute, the dialog fields Required, Read-Only and Multiplicity are not relevant, so they are automatically removed from the dialog.
Date/Time
In the Display As field, specify whether you want the user to specify:
*The date and time
*The date only
*The time only
Relationship
Using this data type, you specify that an asset of the type you are currently defining can be related to another asset or object.
You define the nature of the relationship in the Relationship Type field, using one of the following options:
*Association
*Aggregation using Source
*Aggregation using Target
*Composition using Source
*Composition using Target
These options allow you to define a loose or tight coupling between the related objects. Depending on the type of relationship, operations on an asset (such as delete, export, move to another organization, set instance-level permissions, create a new version) can be applied automatically also to the related asset or object.
For information about how you can use these relationship types, see Working with Composite Types.
In the Association Type field, specify the type of association that this attribute represents. This is a label that you assign as a meaningful name for the relationship. Examples of labels are hasChild and hasParent, indicating a hierarchical relationship.
In the Relates To field, specify the type(s) of object that can be the target of the relationship. You can specify more than one type of object by using the + icon. If you specify more than one type of object in this field, this means that an object of the current object type can have a relationship to an object that belongs to any of the given object types.
Note:  
The Relates To option is enforced in the user interface and at the API level. Within the user interface, this option determines which types of object are shown to users when they set the attribute. At the API level, this option causes CentraSite to reject any asset whose attribute specifies an object that is not of an allowed type.
After you create a Relationship attribute, you can modify the attribute's Association Type only if there are no assigned instances of the attribute in the registry. Similarly, you can change or delete categories in the Relates To option only if the registry contains no assigned instances of the attribute. You can, however, assign additional categories to the Relates To option at any time (even if assigned instances of the attribute exist in the registry).
For more information about association types, see Working with Association Types.
String or Multiline String
Enable the Internationalized option if you want to store the string values in internationalized string form.
After you create a String or Multiline String attribute, you cannot change the attribute's Internationalized option.
String
Enable the Enumeration option if you want to restrict the attribute to a predefined set of values. When users edit this attribute in CentraSite Control, the enumerated values are presented to them in a drop-down list.
CentraSite also enforces the Enumeration option at the API level, meaning that it will reject any asset whose attribute does not contain one of the enumerated values.
If you enable the Enumeration option for a String attribute, you can add new items to the enumerated list at any time (even if instances of the attribute exist in the registry). However, you can remove an item from the list only if that item is not currently assigned to an instance of this type in the registry.
After you create a String attribute, you cannot switch it from an enumerated String to a non-enumerated String (or vice-versa).
Copyright © 2005-2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback