Each time a subprocess is modified, we deploy this one but the engine database is intialized.
Is there a way to keep datas for testing purposes ?
Thanks.
First I want to remind that in Bonita a sub-process is exactly the same as a process. The only difference is that usually the sub-process actor with initiator flag is mapped to no (0) user. Doing that prevent users from starting the sub-process manually. Note that in some situation it might make sense to manually start the sub-process without running the parent process and so in this situation the actor with initiator flag is actually mapped to users.
That being said a process is identified by a name and a version. When you run a process a process instance is created (with task instances) and this instance as a reference to the process definition deployed. If you redeploy a process with the same name and version (for example by clicking again on the Studio “Run” button) it will actually disable and undeploy the previous process definition. As process and tasks instances keep a reference to the process definition they will be deleted as well. For example a task instance reference to the definition cannot be update on the new definition being deploy because the task might no longer exists in the new process definition.
So to answer your use case I think the best option is to update the version of the sub-process. This will let you deploy the two versions side by side. In your parent process, if you don’t specify a version for the sub-process it will use the latest one. That should answer your need to testing. When testing is done you might want to get back to the initial version.