Bug 1327896 - [GSS] Build & Deploy fails due to duplicate ProcessID after copying business process
Summary: [GSS] Build & Deploy fails due to duplicate ProcessID after copying business ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks: 1327924
TreeView+ depends on / blocked
 
Reported: 2016-04-17 16:04 UTC by Hiroko Miura
Modified: 2020-03-27 19:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1327924 (view as bug list)
Environment:
Last Closed: 2020-03-27 19:10:28 UTC
Type: Enhancement


Attachments (Terms of Use)

Description Hiroko Miura 2016-04-17 16:04:22 UTC
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:


Note You need to log in before you can comment on or make changes to this bug.