1. create a process model with a human task, put a value in the "SLA Due Date" field,
2. Update the process version and save as V1.
3. Edit the process model and save it as V2.
4. Instantiate a process with V1, and check the active timers from processes using REST API:
curl -X GET "http://localhost:8080/kie-server/services/rest/server/admin/containers/evaluation_1.0.0-SNAPSHOT/processes/instances/1/timers" -H "accept: application/json"
{
"timer-instance": [
{
"name": "[SLA]Self Evaluation",
"id": 1,
"timer-id": 0,
"activation-time":
{ "java.util.Date": 1692683323467 }
,
"last-fire-time": null,
"next-fire-time":
{ "java.util.Date": 1692683443467 }
,
"delay": 120000,
"period": 0,
"repeat-limit": -1,
"process-instance-id": 4,
"session-id": 2
}
]
}
5. Migrate this process instance from V1-->V2 using kie-server REST API:
curl -X PUT "http://localhost:8080/kie-server/services/rest/server/admin/containers/evaluation_1.0.0-SNAPSHOT/processes/instances/1?targetContainerId=evaluation_1.0.1-SNAPSHOT&targetProcessId=TestMigrationProject.TestProcess" -H "accept: application/json" -H "content-type: application/json" -d "{ }"
6. Timer instance from V2 process after migration
curl -X GET "http://localhost:8080/kie-server/services/rest/server/admin/containers/evaluation_1.1.1-SNAPSHOT/processes/instances/1/timers" -H "accept: application/json"
{
"timer-instance": [
{ "name": null, "id": 0, "timer-id": 0, "activation-time": null, "last-fire-time": null, "next-fire-time": null, "delay": 0, "period": 0, "repeat-limit": 0, "process-instance-id": 0, "session-id": 0 }
]
}
Similar issue is reported in Jira https://issues.redhat.com/browse/RHPAM-4312 and its fixed in RHPAM 7.13.1 but issue is reoccurring in 7.13.3 release
Bug
Major
