To create a generic object, you need create authorization for the relevant folder. When you create a generic object, you must first enter information on the initial screen and save your object. After saving, the system displays this initial version of the generic object, including all fields and items. To assign authorizations and status profiles to your generic object, you must branch to the version overview. For more information about authorizations and status for generic objects, see Status and Authorizations for Generic Objects.
The definition of the generic object, combined with the effects of authorizations and status, determine what particular users can do and when. For example, whether users can:
· Change values in fields
· Add properties and items, and change or delete these.
If you have write and delete authorization for the folder to which the generic object belongs, and if the status of the generic object is not protected, you can delete it.
Properties that you add to a generic object:
· Have a label and value that can be changed
· Are deleted if the label and value are empty
Items that you add to a generic object:
· Have the properties that the system administrator has defined for them in the definition of the generic object type
· Can be deleted by users with write authorization for the object
In the definition of the generic object, the system administrator can also allow predefined items in a generic object type to be deleted.