L3 - Default The task definition key is tightly coupled to the process definition the task belongs to, i.e. it always references the activity id in that process definition (guaranteed by Javadoc in Task#getTaskDefinitionKey). Migration should therefore update that key.
Impact: If a task is migrated to another activity id, the task form cannot be resolved after migration and there is no API to correct that. In tasklist, the task can only be completed by using a generic form.
Note:
Updating the task definition key is also required to resolve task listeners correctly.
This is the controller panel for Smart Panels app
[CAM-6125] Migrating a user task should update the task definition key
| Labels | New: Migration |
| Labels | Original: Migration | New: EasyPick Migration |
| Fix Version/s | New: 7.5.0 [ 14091 ] |
| Assignee | New: Thorben Lindhauer [ thorben.lindhauer ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Description |
Original:
The task definition key is tightly coupled to the process definition the task belongs to, i.e. it always references the activity id in that process definition (guaranteed by Javadoc in Task#getTaskDefinitionKey). Migration should therefore update that key. Impact: If a task is migrated to another activity id, the task form cannot be resolved after migration and there is no API to correct that. |
New:
The task definition key is tightly coupled to the process definition the task belongs to, i.e. it always references the activity id in that process definition (guaranteed by Javadoc in Task#getTaskDefinitionKey). Migration should therefore update that key. Impact: If a task is migrated to another activity id, the task form cannot be resolved after migration and there is no API to correct that. In tasklist, the task can only be completed by using a generic form. |
| Description |
Original:
The task definition key is tightly coupled to the process definition the task belongs to, i.e. it always references the activity id in that process definition (guaranteed by Javadoc in Task#getTaskDefinitionKey). Migration should therefore update that key. Impact: If a task is migrated to another activity id, the task form cannot be resolved after migration and there is no API to correct that. In tasklist, the task can only be completed by using a generic form. |
New:
The task definition key is tightly coupled to the process definition the task belongs to, i.e. it always references the activity id in that process definition (guaranteed by Javadoc in Task#getTaskDefinitionKey). Migration should therefore update that key. Impact: If a task is migrated to another activity id, the task form cannot be resolved after migration and there is no API to correct that. In tasklist, the task can only be completed by using a generic form. Note: Updating the task definition key is also required to resolve task listeners correctly. |
| Assignee | Original: Thorben Lindhauer [ thorben.lindhauer ] | New: Sebastian Menski [ sebastian.menski ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Remaining Estimate | New: 0 minutes [ 0 ] | |
| Original Estimate | New: 0 minutes [ 0 ] |
| Status | Original: Resolved [ 5 ] | New: In Test [ 10004 ] |