There are two different kinds of properties, which are the properties of a model and those of an element. In the first table, you will find the description of the model properties, whereas in the second table the element properties will be described.
| Group | Function | Description |
| General | ||
| Name | Name of model | |
| Description | General description of the model | |
| Objective | Contains the aim of the model | |
| Version comment | A comment can be written for every version for a better understanding of changes. | |
| Meta-information | ||
| Owner | This contains the user who is responsible for the model | |
| Version | Current: the current version of the model Deployed: the version of the currently deployed model |
Depending on the element, the properties can vary. Below are all properties described which means that you can find a description for every property of every element. So it might happen that not every function is relevant for what you are currently searching for.
| Group | Function | Description |
| General | ||
| Name | Name of model | |
| Short name | A short name for the element can be configured here | |
| Description | General description of the model | |
| Objective | Contains the aim of the model | |
| Workflow (Use dynamic name) | This is only relevant for workflow executions. This enables to configure dynamic names of tasks so that it is easier to allocate tasks to workflows | |
| Business intelligence | ||
| Rating | Tasks and areas can be highlighted in a model. The highlights are only visible if the appropriate option is enabled in the View tab (Annotations > Rating Map) | |
| Meta-information | ||
| Owner | This contains the user who is responsible for the model. For detailed information on owners click here | |
| ModelResponsible | This user is responsible for the implementation (modeling) and the content of the model | |
| WorkflowResponsible | This user is responsible for the model execution and therefore gets all user failed tasks and all activity failed tasks where no User in charge is set | |
| Version | Current: the current version of the model Deployed: the version of the currently deployed model |
|
| Edit event | ||
| Edit event | Opens the Edit event dialog for the detailed configuration of an event for the selected element | |
| Customize | ||
| Fill color | The color of the selected element can be set here | |
| Font color | The font color of the currently selected element can be set here | |
| Use default colors | If you tried out some colors but do not like them you can simply recover the initial color by choosing this option | |
| Advanced picker | Opens a new window in order to pick additional colors with the color picker | |
| Timings | ||
| Target duration | Contains the planned duration of a task | |
| Processing time | Detailed and planned net-processing time (min/max/average) | |
| Throughput time | Detailed and planned throughput time (min/max/average) | |
| Event information | ||
| This section contains information about the configured event (the type of event, trigger time etc.) | ||
| Condition | ||
| Condition name | This field is for the configuration of the condition name | |
| Exception name | This field is for the configuration of the exception name which will then be displayed on the exception path | |
| Open condition editor | By clicking this button the editor where you can configure conditions opens | |
| Connections | ||
| Connections: in | List of references with incoming connections of the selected element | |
| Connections: out | List of references with outgoing connections of the selected element | |
| The visibility of the remaining scopes (Roles, Documents, ...) are dynamic and depend on the references of the element | ||
The properties can be extended at any time by adding new fields. These fields can be created at model or element level and support various types such as Text, Date, Number, Boolean, Rich Text, Single or Multiple Users.