--
You received this message because you are subscribed to the Google Groups "jBPM Usage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-usage+unsubscribe@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-usage/c49ca2ef-9732-4cf1-8cba-588ea3abc3b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Then I call programmatically the REST API to create an instance of the newly created process definition. The result would have been the same if generated from the jbpm-console :
The URL called is http://localhost:8080/kie-server/services/rest/server/containers/project-name-jbpm_1.0.3/processes/src.ValidationCustomerProcess/instances/ where project-name-jbpm_1.0.3 is the name of the process definition and src.ValidationCustomerProcess is the name of the business process of the project.
We can see that the BPMN shown in the diagram tab of the process instance does not reflect the modifications occured in the version 1.3. All the instances have this diagram (and when it is executed, the modifications are really not taken into account) and it seems fair because it only copies the diagram of the diagram definition from it's generated. But how am I supposed to create a new process definition that owns the latest modification, which step did I miss ?
Or is it not possible from the jbpm-console to do it at all ? That would be a huge restraint imho.