Bug 917949

Summary: Improve support for process versioning
Product: [Retired] JBoss BPMS Platform 6 Reporter: Martin Weiler <mweiler>
Component: jBPM DesignerAssignee: Kris Verlaenen <kverlaen>
Status: CLOSED EOL QA Contact: Kirill Gaevskii <kgaevski>
Severity: medium Docs Contact: Dawn Eisner <deisner>
Priority: medium    
Version: 6.0.0CC: kverlaen, paradhya, rrajasek
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: In BRMS 5, the process id had to be manually changed to create a new version of a process to validate the version attribute. Consequence: When a process is created, the version id of that process is not validated and needs to be automated. Fix: With the new Mavenized build and deploy approach, the support for versioning has improved significantly. Result: Process versioning is now automatically validated every time a process is updated or created.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:13:31 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Weiler 2013-03-05 07:39:07 UTC
Description of problem:
In BRMS 5, it is necessary to manually change the process id to create a new version of a process, as the process version attribute is not validated.

This bugzilla is a platform issue for https://issues.jboss.org/browse/JBPM-3758 and raised with the intent to get the handling of the version attribute improved.

Comment 1 Kris Verlaenen 2013-06-09 22:37:41 UTC
With the new mavenized build and deploy approach, the support for versioning has improved significantly.  As a result, it would need to be verified that the current implementation does indeed solve the requested issues.  Engineering believes the recent improvements in this area do solve the limitations mentioned in the linked JIRA.

Comment 3 Kris Verlaenen 2013-09-24 13:32:23 UTC
Since there has been no comments, marking this as devel_ack-.

Comment 4 JBoss JIRA Server 2013-10-02 16:12:54 UTC
Kris Verlaenen <kris.verlaenen> updated the status of jira JBPM-3758 to Resolved

Comment 5 Kanchan Desai 2013-10-13 12:26:27 UTC
Hi Marek,

Doc Text has been added. Can you please review the CCFR.