Bug 1024112 - Session "Updating Processes" has wrong information
Session "Updating Processes" has wrong information
Status: NEW
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: doc-BRMS_Business_Process_Management_Guide (Show other bugs)
BRMS 5.3.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: brms-docs@redhat.com
Radovan Synek
Dawn Eisner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-28 17:16 EDT by Alessandro Lazarotti
Modified: 2016-10-14 10:09 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alessandro Lazarotti 2013-10-28 17:16:57 EDT
The documentation has wrong information about updating process:
https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_BRMS_Platform/5/html-single/BRMS_Business_Process_Management_Guide/index.html#Updating_Processes

There is mentioned:

"The updated process must have an updated version number to distinguish it from the old process; this is necessary because the old process may still be required by an existing process instance. "

However it is not enough. To update a process is strongly recommended also update the process definition id. So, the correct sentence should be:

"The updated process must have an updated version number and a new process definition id to distinguish it from the old process; this is necessary because the old process may still be required by an existing process instance. "

I think that it will be better if included how the routine to update a process looks like, example:

----------------------
The procedure is:

1. model process with id process.v1
2. start process instance with process.v1 as id 
3. model new version of the process with id process.v2 usually as a copy of process.v1
4. when you start new process instance you’ll use process.v2 as the id
5. continue working with active instances of process.v1

With that you have clear separation between process definitions that gives you option to run different process instances with different definitions. Although there might be cases where you would like to override the definition for the active instances and thus not changing process id gives you this possibility. 
----------------------

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