You can define an extended field to help ensure that you capture all data in your repository that is critical to your asset management program. For example, when entering an asset for a blade server, there is no way to enter the chipset. Define an extended field named chipset, which adds the field to the Asset Details page. Users can enter the chipset information (for example, Intel 5520) with the other information such as the asset name, serial number, memory, processor, operating system, and so forth.
Important! These steps work only the first-time you complete the wizard and define the extended field for the object. Before you define the extended field, verify that you have the following information for reference: table name, label, format (character, boolean, currency, date, decimal, or integer), field name, attribute name, field size, and whether an entry for the extended field is required. After you complete the wizard, you can configure the extended field like any field.
To define an extended field
The configuration of the page is enabled.
For example, when configuring a legal document, you select Legaldoc Status History in the Object drop-down list. You deny permissions to move fields for that part of the object (the status history). The permission changes apply only to the status history part of the object, and not to the other parts of the object.
Important! You can only define an extended field for a global configuration. You cannot define an extended field for a local configuration.
A wizard appears.
Note: To change the default object label for the extended field, change the label in the Object Label field. For example, change the default label asset hardware Extension to Hardware Extension.
All users see the extended field on the page.
Note: After you add a field and define an extended field, and save the field to a local or global configuration, users can define an event for the field. For more information about managing events, see the User Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|