You can add a field to the page when users must be able to see a field that exists in the repository but is not part of a global configuration, or any field that has been removed and you have denied access. For example, you previously removed an extended field named chipset from the Asset Details page. Users must be able to see and enter a value for this field, so you add the field back onto the page. In addition, if you previously added an extension but did not save the global configuration, use these steps to add the extended field to the page.
Important! When you add a field to an object having multiple asset families (Assets and Models) and legal templates (Legal Documents), the field is added to all families and templates for the object, regardless of the family or template to which you added the field. For example, you add a field for the Hardware asset family. The field is added to all other asset families, including Computer, Other, Projects, Service, and Software.
To add a field
The configuration to 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 add a field for a global configuration. You cannot add a field for a local configuration.
A wizard appears.
Note: For extended fields, a link appears that matches the object label specified when defining an extended field (for example, asset hardware Extensions). Click the link and select the extended fields to add to the page.
All users see the 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.
|
|