An attribute is used to define the properties of your entities, thereby defining the data that can exist in your application. A multivalued attribute can contain more than one value of the same type. |
An attribute is a property of an entity. Every attribute is of a specific data type. For example the entity Person can have attributes like: Name (type: string), Gender (type: Boolean) and Date of birth (type: Date).
An attribute can:
An attribute can get a value through logic, or it can be set by the user, a service, a function flow or a web service.
When the value is derived through logic, a business rule, decision table or data rule determines the value of the attribute. The value is usually dependent on values of other attributes. When an attribute gets a value in this way we say that the value is "system set". A system set value is only determined when the value is necessary, for example when it is shown on a page or used as input for a service.
The value can also be set explicitly by the user. We call this value "user set". This is the case when the value is filled in on a page. Other ways to make give an attribute a user set value is through the use of a service. This also covers other situations like the use of a web service or a function flow. When an attribute has a user set value, this value will be fixed until the value is cleared, or another value is explicitly set.
Property | Description | ||
---|---|---|---|
![]() | Go to unit test overview for this attribute. | ||
Go to the Decision Requirements Graph for this attribute. | |||
Entity | Choose the entity the attribute belongs to.
| ||
Name | Identifies the attribute. Only letters, numbers and underscores (_) are allowed. The name should start with a letter or an underscore. The maximum length of the name is determined by a database setting | ||
Askable | Tick this box in case the value of the attribute can be given by the user. If an attribute is not askable, the value of the attribute has to be derived.
| ||
Functional name | Optional, can be used in documentation | ||
Type | Choose type of attribute. The options are: boolean, String, Number, Date, DateTime, Percentage, Currency, Integer | ||
Acts as Reference |
Check this box if the value of the attribute is a reference to an aggregate (version), document, case or task. This affects the way full-text search handles the value of the attribute. See Search in structured and unstructured information. When checked, the Value list and Default Value section disappear and you can choose to what this attribute refers. It can refer to an aggregate id, aggregate version, task id or process id if the attribute is an integer, or to a document id if the attribute is a string. When referring to a document, you can also provide the connection name in which this is stored. | ||
Multi-valued | Tick this box in case the attribute needs to be a multivalued attribute . It can then have more than one value. | ||
Value list | A Value list is a drop down menu of possible values an attribute can have.
| ||
Description | Is optional, but recommended. | ||
Default value | The initial value of an attribute is set by the default type in combination with the default value. The choices are: None, Constant, Expression, Decision table, External.The default type “None” cannot be combined with a default value e.g. no initial value will be set. For the other default types you can fill in the associated default value which will derive the initial attribute value.
| ||
Question | When the attribute is used on a page, this text will be shown to the user. You can fill in a text for every language of your project. The double arrow down indicates that another language has been filled in as well, and you should not forget to update that one as well when you change the text. The question text can contain TSL | ||
Explain | You can fill in a text for every language of your project. The double arrow down right next to the selected language indicates that another language has been filled in as well, and you should not forget to update that one as well when you change the text. The explanation text can contain TSL | ||
Validation rule | Choose one or more Validation rule. Validations check the correctness of the input for that attribute at run-time. A validation rule can be selected from the drop-down list, or created in-place. Validation rules can also be added to an attribute by dragging and dropping. | ||
Validation type | Is a standard validation rule you can create within the attribute. The following validation types are available:
Please see Validation types. |