What causes Camunda process definition IDs to be built and managed differently?


#1

We are seeing different formats for our ProcessDefinitionIDs between processes - sometimes just a GUID 69b50396-6256-11e8-9121-0242ac11001c and sometimes a concatenation of name:version:GUID CA-instruction-process:2:ca360213-618d-11e8-b470-0242ac11001b. We also see different versioning after deployment - with the concatenated id, the deployment number gets incremented in certain cases.

Deploying via REST to the same Camunda instance using the same deployment script, so I’m assuming there’s something different in the BPMN file configiration, but I can’t see it. The files are too big and too different to meaningfully post hear, but does anyone know what to look for or able to point me to documentation which may help? I haven’t found any mention of this in the online docs so far.


#2

We have found the cause of this difference - if the BPMN process id attribute is too long (mine was 32 chars, I’m not sure what the limit is) it seems the engine reverts to just allocating a GUID as the process definition id; if it has space, it concatenates other related/useful info.

This is a bit opaque and it’s not clear to me whether there is any other impact, I assume not. It did cause us some in a development environment we are building for embedded forms.

I changed mine from:

<bpmn:process id="Finswitch_Transaction_Automation" name="Finswitch Transaction Automation" isExecutable="true" camunda:versionTag="0.2">

to:

<bpmn:process id="Finswitch_Tx" name="Finswitch Transaction Automation" isExecutable="true" camunda:versionTag="0.2">

#3

Recently had the same issue resolve in same way as Ettery


#4

Hi,

the beavior is coded here: https://github.com/camunda/camunda-bpm-platform/blob/00cb6645c2b82a8be0bc20af1f10df0fe546b4ea/engine/src/main/java/org/camunda/bpm/engine/impl/AbstractDefinitionDeployer.java#L333-L348

I would always treat the definitionId as a random (unique) number. You can use a ProcessDefinitionQuery to find a process definition in the runtime database.

Cheers, Ingo


#5

I was referring from https://docs.camunda.org/manual/latest/user-guide/spring-boot-integration/configuration/#camunda-engine-properties
I will try your suggestion now


#6

Works perfectly, thanks you have saved hours of time
processes.xml (569 Bytes)

Updated processes.xml attached