Red Hat Bugzilla – Bug 983661
No alert if you create a process definition which already exists
Last modified: 2014-08-06 16:13:03 EDT
Description of problem:
Application does not react if user try to create a process definition which already exist. It just rewrite the last state of process definition (delete all changes and process is empty)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. go to project authoring (jbpm-playground, Evaluation)
2. create new BPMN2 process definition "evaluation (already exist)
open "Evaluation" process and delete last changes. Until it the process is empty
Alert about conflict (Same behaviour as for DRL file)
There is difference in using git users. Designer use "admin", DRL use "sona" (I log into business-central as user "sona")
Created attachment 772308 [details]
Commit in GIT for DRL
Created attachment 772309 [details]
Commit in GIT for BPMN2
I'm reassigning this to Michael Anstis, because this validation must be performed at VFS or Asset Wizzard level, not in the BPM side at all.
fixed in designer master and 6.0.x branches
Verified for ER4.
An alert "File "git://uf-playground/myProject/src/main/resources/org/group/myproject/hello.bpmn2" already exists." is shown (as expected).