|
|
![]() |
![]() |
![]() |
|
Contents Introduction Concepts User Help Modeler Help Browser Help
|
|||
![]() |
|||
![]() |
![]() |
Defining Default ValuesDefault PropertiesWhen a type is defined, a default item is automatically created, with the name "Default". You can edit the values of properties for the Default item, if authorised. When you do this, these values will be used as default values for properties of any new item created of the corresponding type. An example would be where we have a type "Project" with a property "Status" and we want newly created project items to have the status "Initial". This can be achieved by editing the default Project item Status property to have the value "Initial". Default RelationshipsYou can also specify defaults for the legal relationships defined between a type and other types. Following on the project example, assume the type "Project" had a legal relationship "owned by" defined to type "Business Unit". If we want all newly created projects to be "owned by ACME Conglomerate" we would simply link the Default of the type "Project" to the Business Unit called "ACME" Conglomerate" via the relationship "owned by". The default values appear when a new item is created, but can be overwritten by user entries if desired. Default Documents and TemplatesYou can store a document in the default item of a type which has either Document or Template property types. Every time you create new item of a type that contains a default document in a document property type, a clone of the document gets created and associated with the new item. The document can then be edited by user using the appropriate helper application on the client. Referred to the documents and template sections respectively for information on managing versions of these property types. Default documents associated with template property types work in a very similar way. The only difference is that it is not possible from the user to change the name or extension of the document stored in a template property type.
|