The process engine functions together with the process engine database. This database is needed for the persistence of the cases and tasks. The table underneath shows a subset of the information stored by the process engine.
| Field name | Explanation | Type | Set by | Extra Information |
|---|---|---|---|---|
| TaskId | Unique ID for a task | Integer | Auto by PE | |
| TaskStarted | Time the task is created | DateTime | Auto by PE | |
| DueDate | Date or time when a task should be finished, can be used for monitoring | Date or Date/Time | Should be modeled at a task by a BE | |
| TimeOutdate | Date or time when a task will be closed | Date or Date/Time | Auto by PE, uses the expression at the timer exit at a task | |
| User | The user who is assigned to the task by the routing algorithm, or the assignTask service | String (Multivalued) | Auto by PE | |
| Team | The teams which are assigned to the task by the routing algorithm, or the assignTask service | String (Multivalued) | Auto by PE | |
| Role | The roles which are assigned to the task by the routing algorithm, or the assignTask service | String (Multivalued) | Auto by PE | |
| Executed By | The user name of the person who has completed the task | String | Auto by PE | |
| TaskStatus | The status of a case when entry is stored | String | Auto by PE | Possible values: Open, Completed, Exception, locked |