10.4. Human Task Persistence

The model below is an entity relationship diagram (ERD) that shows the persistent entities used by the Human Task service.

The data model above is organized around 2 groups of entities:

Two other important entities in the data model are the i18ntext and organizationalentity.

The foreign key column in the tables in Section 10.4.2, “Task Related Entities” indicate whether or not a column in a database table has a foreign key constraint on it. The null column describes whether or not the database table column being describe can be null.

Please note, that if an entry is described as not allowing a null value and there is no associated entry, the column will contain the value -1 or 0.

The task entity contains the information for describing a task.

The subtasksstrategy entity is used to save the strategy that describes how parent and sub-tasks should react when either parent or sub-tasks are ended.

The organizationalentity entity is extended to represent the different people assignments that are part of the task.

The attachment entity describes attachments that have been added to the task.

The task_comment entity describes comments added to tasks.

The delegation_delegates table is a join table for relationships between the task entity and the organizationalentity.

The peopleassignments_stakeholders table is a join table that describes which organizationalentity entities are task stakeholders of a particular task.

The peopleassignments_potowners table is a join table that describes which organizationalentity entities are potential owners of a particular task.

The peopleassignments_exclowners table is a join table that describes which organizationalentity entities are the excluded owners of a particular task.

The peopleassignments_bas table is a join table that describes which organizationalentity entities are business administrators of a particular task.

The peopleassignments_recipients table is a join table that describes which organizationalentity entities are notification recipients for a particular task.

The following paragraphs and tables describe the group of entities having to do with deadline, escalation, and notification information.

The deadline entity represents a deadline for a task.

The escalation entity describes an escalation action that should be taken for a particular deadline.

The booleanexpression entity represents an expression that evaluates to a boolean. These expressions are used to determine if a constraint should be applied.

The notification entity describes a notification generated by an escalation action.

The email_header entity describes an email that will be sent as part of a notification.

The notification_email_header table is a join table that describes and qualifies which email_header entities are part of a notification.

The reassignment entity describes reassignments associated with escalations.

The reassignments_potentialowners table is a join table that describes which organizationalentity entities are potential owners if a reassignment happens as part of an escalation.

The notification_bas table is a join table that describes which business administrators will be notified by a notification.

The notification_recipients table is a join table that describes which recipients entities will be received a notification.

The content entity represents the content of a document, output document, fault or other object.

The i18ntext entity is used by a number of other entities to store text fields. The deadline, notification, reassignment, and task entities use this entity to store descriptions, subjects, names, and other documentation.

Foreign keys can not be set to null, and any foreign key that is not being used will be set to 0.