IBM InfoSphere Master Data Management, Version 11.3The TASKINSTANCE table stores the details of each instance of a task defined by a specific task definition such as the task due date, creation date, creator, priority, task owner role and its current status.
| Name | Comment | Datatype | Null Option | Is PK |
|---|---|---|---|---|
| TASK_INSTANCE_ID | A unique, system-generated key that identifies a task instance in the system. | BIGINT | Not Null | Yes |
| TASK_ROLE_ASSOC_ID | A unique, system-generated key that identifies the association between a task and the role of the user entitled to that task in the system. | BIGINT | Not Null | No |
| TASK_ACTION_TP_CD | A code that identifies the action taken on a task instance. For example, "Assign", "Unassign", "Approve", and "Reject". | BIGINT | Not Null | No |
| TASK_STATUS_TP_CD | A code that identifies the status of a task instance. For example, "New", "Pending", "In Progress", and "Completed". | BIGINT | Not Null | No |
| CREATOR | The name of the creator for the task instance. | VARCHAR(80) | Not Null | No |
| TASK_OWNER | The person to whom a task instance is assigned. | VARCHAR(80) | Null | No |
| WORKBASKET_ID | A unique, system-generated key that identifies a workbasket associated with a task instance in the system. | BIGINT | Null | No |
| PRIORITY_TP_CD | Priority Type Code identifies the priority of a task, a campaign, a value, and so forth. For example, "high", "medium", "low". | BIGINT | Not Null | No |
| TASK_DUE_DT | The date the task instance is due for completion. | TIMESTAMP | Not Null | No |
| PROCESS_ID | A unique, system-generated key that identifies the process a task instance belongs to in the system. | BIGINT | Null | No |
| CREATION_DT | The date on which the task instance is created. | TIMESTAMP | Not Null | No |
| LAST_COMMENT_ID | A unique, system-generated key that identifies the latest comment associated with the task instance in the system. | BIGINT | Null | No |
| LAST_UPDATE_USER | The ID of the user who last updated the data. | VARCHAR(20) | Null | No |
| LAST_UPDATE_DT | When a record is added or updated, this field is updated with the date and time. On subsequent updates, the system uses this information to ensure that the update request includes a matching date and time on this field; if it does not, the update fails. | TIMESTAMP | Not Null | No |
| LAST_UPDATE_TX_ID | A unique, system-generated key that identifies the specific transaction within the log system that either created, updated, or deleted the data row. | BIGINT | Null | No |