Process difinition ID doesnt contain process name for few is it will give any issue

process difinition ID doesnt contain process name for few is it will give any issue.

please see below two porcesses, one having process id but another dont have id even we kept it
Please let me know if it will create any issue.

process difinition ID doesnt contain process name for few is it will give any issue.

Please help me why it is adding for one and not adding for another one.

When I try to skip the activities it is saying no process deployed with definition id. (is it because of the above issue). please help me. Thanks in advance.

url using to skip (I kept the engine name as pom): http://localhost:61144/engine-rest/engine/pom/modification/execute

{
“processDefinitionId” : “9e068824-b72e-11ed-a4a5-a44cc853afb7”,
“instructions”: [
{
“type”: “startAfterActivity”,
“activityId”: “Gateway_1acrzti”
},
{
“type”: “cancel”,
“activityId”: “PFFOE-ReceiveHCommitted”,
“cancelCurrentActiveActivityInstances” : true
}
],
“processInstanceIds”: [
“8b0fbd53-b729-11ed-a739-0050569694ac”
],
“processInstanceQuery”: {
“processDefinitionId”: “9e068824-b72e-11ed-a4a5-a44cc853afb7”
},
“skipCustomListeners”: true,
“annotation”: “Modified to resolve an error.”
}

getting: below error:

Skip service is not working only for this (which definition id don’t have process id name), other processes are working fine(which are having process id in deployment definition id ) with skip command…

Thanks,
Venkaiah.

Hello @venky1982 ,

you could remove this constraint from your code logic and use the fields id and key completely separate.

The reason is that the behaviour comes from an IdProvider which is configurable to the engine.

This means that the assumption that each process definition id contains the key is not valid.

Jonathan

Thank you @jonathan.lukas

1 Like