Creating a Field

from the configuration console, select build > business objects open a business object the application opens the workspace for the selected business object select the fields tab the application displays a list of fields select add new the application displays a list of field types see form field types docid 1rvguxdd6glw0fmpandjt the number of fields in a business object is limited to 300 to ensure optimal performance in case you need to add more fields, do so in a different business object and link them using the relationship table docid\ fmuv10aqntq bblz6u7nm select a field type the application displays the setting field details workspace enter information in the fields depending on the type of field that you create, the application displays different fields fields unique to a field are listed under that field type; fields that are common to all fields are listed here field description field name a unique name without spaces or special characters you cannot add field name as "other" display name the name that appears to users description an optional description of the field field type automatically set by the application based on the field type that you select you can only make changes to this value for the number and text field types permissions these permissions are set internally and cannot be configured field annotations field annotations (not used for guid fields) optional you can select an annotation from the list to specify a field type this is not commonly used you can select from the following annotations emailaddress url phonenumber orgunitname field attributes unique (not used for link fields) specifies if you can assign a unique id to a record this id is unique across all instances (records) in the business object table this is the same as the unique index used in a microsoft sql database nullable (not used for link fields) specifies if you can enter a null value in the field values are not enforced in this field, but when they are defined, they must be unique (even though unique is not checked) hidden in ui specifies that the application does not display this field in the user interface if you check this, you cannot use this field when creating a form this option is typically activated by default and is of particular use in group and member business objects searched specifies if this field can be searched for example, number fields often produce unexpected results when performing a text search you can check this field to make your field search correctly an example is the incidentnumber field in the incident business object stored (not used for link fields) specifies if the application stores the value of the field in the database if unchecked, the application evaluates the value of the field at runtime but does not store its value audited specifies that changes to this field are audited in the audit stream disabling this audit type removes the previously audited data clearing the audited checkbox deletes all existing audit history to retain this data, back up the audit history before disabling the audit flag commonly used shows the business object in the common objects area of the main business objects page select save if you try to add or edit a field for a business object that has more than one million records, you get an error message contact ivanti sre (site reliability engineering) via your portal and raise a ticket they can edit the database directly to make the change for you