Amending Version Numbers

If you try to deploy to BPM a project that contains an organization model with the same version number as an organization model that already exists, then the deployment fails.

Note: This does not apply to projects that contain other assets. For projects that contain other assets, the qualifier (which is a date/time stamp) means that each project that is deployed does have a unique version number. For example, you may deploy a project twice, the second time within seconds of the first, but each time the project would have a different date/time stamp and therefore a unique version number.

Therefore, if you want to make changes to an existing organization model and redeploy it, you must give the project that contains the organization model a new version number.

Warning: When you increase the major or minor version number (depending on whether the change is additive or destructive), the numbers you choose should be sequential. This is because a process executes against the accumulation of all deployed organization models belonging to the major version referenced in its process definition. For example, an organization model may have been deployed with version numbers, 1.1, 1.2 and 1.3. All processes that reference that organization will execute against organization model version 1.3.

You can do one of the following:

  • Increase the major version number. Change the major version number if the changes are destructive.
    Note: Name changes are regarded as destructive, because the old names have been removed.
  • Increase the minor version number. Change the minor version number if the changes are additive rather than destructive. However, process definitions that reference the organization model also reference the major version number of the organization model. This means that if you have changed the major version number of an organization model then, if you want your process definitions to execute against the new organization model, you must change the major version number of the projects that reference the new organization model so that their major version numbers match.

Note that:

  • A process executes against the accumulation of all deployed organization models belonging to the major version referenced in its process definition. This means that if only the organization model’s minor version has changed, you do not have to change the version numbers of the processes that execute against it.
  • Processes that do not need to use the new organization model do not have to have their major version number changed but can continue to execute against the previous version of the organization model.