Taskana is configured via a configuration file 'taskana.properties'. This configuration file contains all parameters to control the behaviour of the taskana library.
General Parameter
Parameter | Description | Sample Value |
|---|---|---|
taskana.domains | The comma separated list of administrative domains | DOMAIN_A, DOMAIN_B |
taskana.classification.types | The comma separated list of classification types | TASK, DOCUMENT |
taskana.classification.categories | The comma separated list of classification categories | EXTERNAL, MANUAL, AUTOMATIC, PROCESS |
Security Configuration
The properties file contains the specification of the lists of access ids (i.e. users or groups) that belong to the roles user, business_admin or admin.
The keywords to specify these roles are as follows:
Role | Keyword |
|---|---|
user | taskana.roles.user |
business_admin | taskana.roles.businessadmin |
task_admin | taskana.roles.taskadmin |
admin | taskana.roles.admin |
Each entry may contain a list of access ids that are separated by the '|' character. Whitespace at the begin or end of each access id is ignored. This is, as sample config may look like
...
The taskana.validation.allowTimestampWithServiceLevelMismatch allows the user to create tasks with timestamps that do not match i.e. exceed the service level of the classification. If the property is set to true, the planned and due timestamp of a Task can be set to points in time, which are further apart than the service level of the classification would normally allow.
Additional User Info
If you are using the USER_INFO table you can add the Full/Long name when retrieveing Tasks/TaskComments/TaskHistoryEvents with the property taskana.addAdditionalUserInfo