TASK_AUDIT_LOG view: Business Process Choreographer database view

IBM BPM, V8.0.1, All platforms > Reference > Database views for Business Process Choreographer
TASK_AUDIT_LOG view

Use this predefined Business Process Choreographer database view for queries on audit log information for human tasks.

Inline tasks are logged in the AUDIT_LOG_B view. All other task types are logged in the TASK_AUDIT_LOG view. Depending on the choices made in IBM Integration Designer, inline human tasks can also trigger Common Event Infrastructure (CEI) events to be emitted for Business Flow Manager staff activity events and Human Task Manager task events.
Audit events are related to task entities. The audit event types depend on the entity to which the event refers. The audit event types include:

Task instance events (TIE)
Task template events (TTE)
Escalation instance events (EIE)

The following table describes the TASK_AUDIT_LOG view.

subtasks and follow-on tasks.
Structure of the TASK_AUDIT_LOG view
Name TIE TTE EIE Description
PARENT_TASK_NAME x The name of the parent task instance or template. This is only set for subtasks and follow-on tasks.
PARENT_TASK_NAMESP x The namespace of the parent task instance or template. This is only set for subtasks and follow-on tasks.
PARENT_TKIID x The identifier of the parent task instance.
PRINCIPAL x x x The name of the principal whose request triggered the event.
PROCESS_APP_ACRONYM x x x The acronym of the process application if the root container is a process application. This is only set if the task template is deployed from the Process Center.
SNAPSHOT_ID x x x The snapshot ID of the root container, which can be either a process application or a toolkit. This is only set if the task template is deployed from the Process Center.
SNAPSHOT_NAME x x x The snapshot name of the root container. This is only set if the task template is deployed from the Process Center.
TASK_KIND x x The kind of the task. Possible values are:
KIND_HUMAN 101
KIND_ORIGINATING 103
KIND_PARTICIPATING 105
KIND_ADMINISTRATIVE 106
TASK_STATE x The state of the task or task template. Possible values for task templates are:
STATE_STARTED 1
STATE_STOPPED 2 Possible values for task instances are:
STATE_INACTIVE 1
STATE_READY 2
STATE_RUNNING  3
STATE_FINISHED 5
STATE_FAILED 6
STATE_TERMINATED 7
STATE_CLAIMED 8
STATE_EXPIRED 12
FORWARDED 101
TKIID x x The identifier of the task instance.
TKTID x x The identifier of the task template.
TOP_TKIID x The identifier of the top task instance.
USERS x x The new user IDs assigned to a task or escalation work item. If the value is made available via the NEW_USER field, this may have the value null. See the field NEW_USER for a list of events to which this attribute applies.
VALID_FROM x Valid-from date of the task template that is related to the current event.
WORK_ITEM_REASON x x The reason for the assignment of the work item. Possible values are:
POTENTIAL_OWNER 1
EDITOR  2
READER 3
OWNER  4
POTENTIAL_STARTER 5
STARTER  6
ADMINISTRATOR 7
POTENTIAL_SENDER 8
ORIGINATOR 9
ESCALATION_RECEIVER 10
POTENTIAL_INSTANCE_CREATOR 11
The reason is set for all events related to work items: ESCALATION_RECEIVER is set for escalation work item related events, while the other reasons apply to task work item related events.

Database views for Business Process Choreographer

Related information:
Human task events

Name	TIE	TTE	EIE	Description
PARENT_TASK_NAME	x			The name of the parent task instance or template. This is only set for subtasks and follow-on tasks.
PARENT_TASK_NAMESP	x			The namespace of the parent task instance or template. This is only set for subtasks and follow-on tasks.
PARENT_TKIID	x			The identifier of the parent task instance.
PRINCIPAL	x	x	x	The name of the principal whose request triggered the event.
PROCESS_APP_ACRONYM	x	x	x	The acronym of the process application if the root container is a process application. This is only set if the task template is deployed from the Process Center.
SNAPSHOT_ID	x	x	x	The snapshot ID of the root container, which can be either a process application or a toolkit. This is only set if the task template is deployed from the Process Center.
SNAPSHOT_NAME	x	x	x	The snapshot name of the root container. This is only set if the task template is deployed from the Process Center.
TASK_KIND	x	x		The kind of the task. Possible values are: KIND_HUMAN 101 KIND_ORIGINATING 103 KIND_PARTICIPATING 105 KIND_ADMINISTRATIVE 106
TASK_STATE	x			The state of the task or task template. Possible values for task templates are: STATE_STARTED 1 STATE_STOPPED 2 Possible values for task instances are: STATE_INACTIVE 1 STATE_READY 2 STATE_RUNNING 3 STATE_FINISHED 5 STATE_FAILED 6 STATE_TERMINATED 7 STATE_CLAIMED 8 STATE_EXPIRED 12 FORWARDED 101
TKIID	x		x	The identifier of the task instance.
TKTID	x	x		The identifier of the task template.
TOP_TKIID	x			The identifier of the top task instance.
USERS	x		x	The new user IDs assigned to a task or escalation work item. If the value is made available via the NEW_USER field, this may have the value null. See the field NEW_USER for a list of events to which this attribute applies.
VALID_FROM		x		Valid-from date of the task template that is related to the current event.
WORK_ITEM_REASON	x		x	The reason for the assignment of the work item. Possible values are: POTENTIAL_OWNER 1 EDITOR 2 READER 3 OWNER 4 POTENTIAL_STARTER 5 STARTER 6 ADMINISTRATOR 7 POTENTIAL_SENDER 8 ORIGINATOR 9 ESCALATION_RECEIVER 10 POTENTIAL_INSTANCE_CREATOR 11 The reason is set for all events related to work items: ESCALATION_RECEIVER is set for escalation work item related events, while the other reasons apply to task work item related events.