The repository already supports to go back to an old version. Check the repository attributes where it shows the version and let you choose to go back.
Why do you want to save every version as a new file if the repository can return any specified version to you?
1 of 1 people found this helpful
I think you are mixing 2 different concepts here:
- Create different versions of the same Process: currently jBPM5 doesn't support multiple versions of the same process. If you want to have a new version of a process you need to use different ids. Please read the section about process migration in jBPM5 documentation.
- Versionate process definitions: this means that process definitions (.bpmn2 files) are versioned like if they were under a version control system. If you are using web designer, you already have a version control system in Guvnor. Every time you save your process you are creating a new version in Guvnor's repository. If you want to move between versions you can use Guvnor to do so. Please refer to Guvnor's documentation for further details.
Thanks Esteban ,
Based on your reply i could related to my requirements and it was precise.
"currently jBPM5 doesn't support multiple versions of the same process. If you want to have a new version of a process you need to use different ids "
Even I have the same requirement like, my process needs all versions of the files. But how to load the files based on the version. That is multiversioning of the files with same process id.
If you have found any alternative solution to maintain multiversioning please do share
You cannot load the different versions of the same file ( with same id ). you can load all the versions only if all your versions have different id's.
ex: test.bpmn2 has 3 versions 22.214.171.124 and 1.2 where 1.0 version had the id as test1 , v1.1 as test1.1 and v1.2 as test1.2. then all the 3 id's can be loaded.
Thanks for the reply. We have the same requirement, where in the workflows keep on changing for every release and it is dificult to handle the versions.
We felt, Guvnor is not suitable option for this and started using local file system to acheive by creating multiple files with new and old process instances.
In your view is this correct or Guvnor is the best option?
The option of using Guvnor was the idea to avoid any extra changes and use the guvnor as is. Infact using the file system is a better approach with your scenario. The Guvnor uses jackrabbit as respository manager and has its config files. You can tweek it further as per your ease.