The differences between the functional_task_id, task_id, system_task_id, and system_functional_task_id

Answer

Note: The content and explanation of the performance data warehouse is available in the Performance Data Warehouse database architecture document within the product documentation. IBM Business Process Manager is the continuation of the Teamworks and WebSphere Lombardi Edition products.

Neil Kolban has some examples how to use the tables and columns in the Performance Data Warehouse. Please see page 725 of this March 2014 edition of the BPM book.

In the Performance Server, the functional_task_id and task_id are reassigned ID values, so they do not map back to the IDs that you find in the Process Server database.

In the performance server database:

• The task_id is a unique ID, which is assigned by the performance server to allow it to track the performance server "task".
  
  
• The functional_task_id is another ID that maps back to the least-specific task ID, which is generally the business process definition (BPD) instance ID.
  
  
• The .lsw_task.system_task_id maps to the most specific task ID in the process server, which is generally the actual ID of the task (.lsw_task.task_id).
  
  
• The system_task_id that start with an X represent a virtual task, or in other words, a service that is run without an associated task (workflowState=5).
  
  
• The system_task_id that end in an "a" (for example 5512a) are from an activity, or more specifically, services that were run with an associated task. These IDs should correspond back to the task ID for the process server (minus the letter a). The a stands for activity BTW.
  
  
• The system_task_id that do not have an "a" on the end are related to the BPD instance ID from the process server database.
  
  
• The .lsw_task.system_functional_task_id maps to the least-specific task ID in the process server, which is generally the BPD instance ID that started the actual task.