Hello,
We have detected in production environment a mistake in a flow condition. In our testing environment, we have not been able to migrate the running instances using the flowable API, because of the process to migrate has parallel flows inside subprocess and some flows are deleted, so we are trying to use the DynamicBpmnService to change the sequence flow condition dinamically.
After calling changeSequenceFlowCondition and saveProcessDefinitionInfo methods, we can see one record in ACT_PROCDEF_INFO table and its corresponding record in ACT_GE_BYTEARRAY (that contains the new condition as BYTES_), but the existing instances that take the flow, still evaluating the old condition. We get the same result after restart the application or with new process instances.
What we are doing wrong?
Any help will be appreciated