Deploy new process definition in runtime

Mart · March 11, 2020, 12:22pm

Hi everyone, i wanna deploy new process definition on runtime, without redeploy or reboot application. For that i use flowable API methods:

repository/deployments - to download new process definition
then i start process and after that i get exception - no process definition found from key (something like that)
why it is not working ?
I am trying to use next endpoint to try fix it -
runtime/process-instances/{instanceId}/migrate
but it is not helps
P.S i am sorry if i mixed up topic

maratkalibek · March 11, 2020, 3:48pm

I think you should do in that way:

Deploy new version POST repository/deployments. Here is doc - https://flowable.com/open-source/docs/bpmn/ch15-REST/#create-a-new-deployment
Start process with key.

runtime/process-instances/{instanceId}/migrate is used to migrate process instances to new version.

Mart · March 12, 2020, 6:11am

I am trying to do like that, but i don’t know how to use this ‘runtime/process-instances/{instanceId}/migrate’ endpoint, can anyone show example of json request for migrate old process on new process definition instance ?

PHH · March 12, 2020, 7:20am

Maybe unit tests may give you some hints:

github.com

flowable/flowable-engine/blob/80915c89ddd779ac3a1f8bcc19a6e49028893256/modules/flowable-engine/src/test/java/org/flowable/engine/test/api/runtime/migration/ProcessInstanceMigrationDocumentTest.java

/* Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

package org.flowable.engine.test.api.runtime.migration;

import static org.assertj.core.api.Assertions.assertThat;
import static org.assertj.core.api.Assertions.assertThatThrownBy;

import java.util.Arrays;
import java.util.Collections;

This file has been truncated. show original

The json is built dynamically in that example but may help you.

Cheers
Paul.

Mart · March 12, 2020, 8:11am

Thanks for that, i found file in tests - https://github.com/flowable/flowable-engine/blob/80915c89ddd779ac3a1f8bcc19a6e49028893256/modules/flowable-engine/src/test/resources/org/flowable/engine/test/api/runtime/migration/completeProcessInstanceMigrationDocument.json ,
but then i’m trying to migrate on new process definition i get next exception: Migration Activity mapping missing for activity definition id: ‘reviewTask’ or its MI Parent
What thats mean ?
I am sorry maybe need to do new topic for discuss about that ?

joram · March 14, 2020, 3:24pm

The exception means you haven’t mapped an activity that should have been mapped in the migration Document.

Mart · March 16, 2020, 10:59am

thanks, will try to understand how it works. Can i read about that somewhere(about mapping exception and how to fix it) ?

joram · March 25, 2020, 7:59am

No, the documentation doesn’t describe that. Best luck is to attach the source code and put a breakpoint on that particular exception, then you will see why the problem arises.

Topic		Replies	Views
REST API for process Instance Migration Flowable Engine	1	180	December 12, 2023
Process Version handling Flowable Engine	1	1174	January 25, 2018
Migrating User to New Deployed Version Flowable Engine	11	1939	August 21, 2017
Unable to get the process defination and unable to start it using api Flowable Engine	1	962	February 25, 2019
Is there any way to add flow element to the process definition on a distributed application Flowable Engine	1	335	November 16, 2020

Deploy new process definition in runtime

Related Topics