Bug 1327924

Summary: [GSS] (6.3.z) Build & Deploy fails due to duplicate ProcessID after copying business process
Product: [Retired] JBoss BPMS Platform 6 Reporter: Hiroko Miura <hmiura>
Component: Business CentralAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: alazarot, hmiura, kverlaen, lpetrovi, manstis, smcgowan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1327896 Environment:
Last Closed: 2020-03-27 19:35:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1327896    
Bug Blocks:    

Description Hiroko Miura 2016-04-18 01:55:51 UTC 
+++ This bug was initially created as a clone of Bug #1327896 +++

Description of problem:

In process designer of business central, there is 'Copy' button
which can create new business process by copying existing one.
When copying it, new asset name needs to input but the contents of existing
business process is completely copied from existing one without any change.

Therefore, ProcessID in copied business process is same with existing one
so build fails with the error like the following if it is not changed by hand.  

---
Process with same id already exists: project1.testProcess
---

The other editors, such as GuidedDecisionTableEditor and GuidedRuleEditor, implements CopyHelper interface to update the rule name upon copying, please implement it in process designer as well.

Version-Release number of selected component (if applicable):
6.2.x


How reproducible:
copy existing business process and then perform 'Build & Deploy'.

Steps to Reproduce:
1. in process designer, copy existing business process by clicking Copy button
2. save copied business process and then perform  Build & Deploy
3.

Actual results:
build fails with the error "Process with same id already exists:..."

Expected results:
build succeed.


Additional info: