MIGRATION_FRONT view
Use this predefined Business Process Choreographer database view to query where the process instance was in its navigation when it was migrated to the new version of the process template. The migration front represents the activities that were either active or just completed when the migration occurred.
| Column name | Type | Comments |
|---|---|---|
| PIID | ID | The process instance ID. |
| SOURCE_PTID | ID | The ID of the process template that is associated with the process instance before migration. |
| TARGET_PTID | ID | The ID of the process template that is associated with the process instance after migration. |
| AIID | ID | The ID of an activity that was part of the process navigation front when the process was migrated. The migration front consists of the last activity reached by the process navigation on each parallel branch when the process was migrated. |
| SOURCE_ATID | ID | The ID of the activity template before migration. |
| TARGET_ATID | ID | The ID of the activity template after migration. If the activity was completed before the process instance was migrated, the activity template ID does not change. |
| MIGRATION_TIME | Timestamp | The time that the process instance was migrated. |
| STATE | Integer | The state of the activity when
the process instance was migrated. Possible values are: STATE_READY (2) |
| SUBSTATE | Integer | The
substate of the activity when the process instance was migrated. Possible
values are:
SUB_STATE_NONE (0) |
| STOP_REASON | Integer | The reason why the activity
stopped. Possible values are:
STOP_REASON_UNSPECIFIED (1) |