Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1167610

Summary: Process definition is not updated when new version of project is deployed
Product: [Retired] JBoss BPMS Platform 6 Reporter: Lyle Wang <lywang>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: medium Docs Contact:
Priority: high    
Version: 6.0.3CC: kverlaen, mbaluch
Target Milestone: ER4   
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:01:42 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:
Attachments:
Description Flags
both processes are available even though they have both id and version exactly the same none

Description Lyle Wang 2014-11-25 07:14:27 UTC 
Description of problem:

In business-central, if the process definition is updated (withouth modifying the version of process), and build/deploy the project with a new version ID, the process definition in "Process Management / Process Definitions" page will not be updated.


Version-Release number of selected component (if applicable):
business-central


How reproducible:
always


Steps to Reproduce:
1. Open business-central and create a new project, add a business process, setup "version" field in process to "1", build/deploy the project with version id "1.0"

2. Open "Deploy / Deployments" page, the deployment 1.0 is listed. Open "Process Management / Process Definitions" page, process ver.1 is listed. Checking the process definition detail, its "Deployment" is version 1.0

3. Update the content of the process, but don't update the "version" field of the process.  Build/deploy the project with version id "2.0". 

4. Open "Deploy / Deployments" page, the deployment 1.0 and 2.0 are both listed. Open "Process Management / Process Definitions" page, only one process ver.1 is listed. Checking the process definition detail, its "Deployment" is still version 1.0. The other "process ver.1"(updated) from "project 2.0" is missing here.



Actual results:
The updated process (published with project 2.0) is not reflected in  "Process Management / Process Definitions" page.


Expected results:
If two projects (1.0 and 2.0) contain a process def. with the same name and same version, we expect to see some warning message on the screen during "build / deploy";
Alternatively, the process def. from version 2.0 deployment (LATEST) is expected in "Process Management / Process Definitions" page, rather than the one from the old version of deployment.


Additional info:
Comment 2 Zuzana Krejčová 2014-11-25 07:59:52 UTC 
Probably a duplicate of bug 1008918.
Comment 3 Maciej Swiderski 2014-11-25 18:47:44 UTC 
this has already been fixed in master and 6.2.x (which will become 6.1 product) with this commit:

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/4179cbdefe37be5c452cfc59e7d1e8794c0d0ef0

6.2.x:
https://github.com/droolsjbpm/jbpm/commit/d586c1bcbf8efc7de10d955a535fffa50c5c0c9a

see attached screenshot
Comment 4 Maciej Swiderski 2014-11-25 18:48:35 UTC 
Created attachment 961346 [details]
both processes are available even though they have both id and version exactly the same
Comment 5 Lyle Wang 2014-11-26 00:36:36 UTC 
Thanks Maciej, that screenshot helps to make things clear and it looks perfect :)
Comment 6 Zuzana Krejčová 2014-11-26 08:02:48 UTC 
*** Bug 1008918 has been marked as a duplicate of this bug. ***
Comment 7 Pavel Kralik 2015-01-12 16:36:53 UTC 
BPMS 6.1.0.ER3: "Process Management / Process Definitions" page, only one process version 1 is listed.
Comment 10 Kris Verlaenen 2015-01-27 14:21:23 UTC 
This is as expected.  The version column is displaying the version property of the process.  Since you didn't update the version in the process after doing changes, it will still be 1.0.  Note that the version property of a process is user-controlled: they can decide when to update a version (this is not done automatically) and what to call them.  They can have multiple processes have the same version (if the process did not change between different project versions, or if they believe the changes for example were minor, not require bumping the version).  Note that the project id is correctly showing the updated project id (as you can't have two projects with the same groupid - artefactid - version).
Comment 11 Pavel Kralik 2015-02-06 18:26:36 UTC 
BPMS 6.1.0.ER4