Open topic with navigation

TIBCO Business Studio™ - BPM Edition 5.4.0

# BOM Versioning

Versioning of the BOM is maintained in TIBCO BPM Enterprise, and it follows version semantics, that is, it has major and minor versions. This depends on whether the new version of the BOM is compatible with the currently deployed version of the BOM or not.

When you create a new version of a BOM in the Business Studio:

1. If this new version is compatible with the existing version of the BOM, you can deploy the new minor version of the same BOM without any problem. So, if the current version of the BOM is 1.0.0, you can create, and deploy a new minor version, say, 1.1.0.
   1. This minor version must have the following compatibility constraints.
      - Though existing attributes cannot be deleted, new attributes can be added to the BOM.
      - The data type of the existing attributes cannot be changed.
      - Decrease in length for existing attribute is not supported.
      Note: In case the new version created has any change that is not in agreement with the above specified compatibility constraints, the new version is incompatible with the existing version of the BOM, and while deploying in TIBCO BPM Enterprise gives an error.
   2. When a new minor version of BOM is deployed to TIBCO BPM Enterprise, the existing minor version of the BOM is automatically undeployed.
      Note: At any given point in time, the latest minor version exists in the system.
2. As mentioned earlier, if the new version is incompatible with the existing version of the BOM, you might get an error while deploying the new version in BPM Enterprise. In such a case, you must increment the major component of the BOM's version number in Studio. For this, go to Properties > Lifecycle. Click Increment Major Version and then, click Apply and Close. When this new major version of the BOM is deployed to TIBCO BPM Enterprise, the new version of the process application uses the new major version of the BOM.

So, if the current deployed version of the BOM is 1.1.0, and you deploy version 2.0.0, the 1.1.0 version of that BOM moves into the "Undeploying" state, and stays in the "Undeploying" state until there are outstanding 1.1.0 cases present in the system, or any process application referring to this BOM. Once there are no active cases for BOM 1.1.0 and all the referring process applications are also undeployed, the 1.1.0 gets completely undeployed.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO Business Studio™ - BPM Edition

Copyright © 2015-2023. Cloud Software Group, Inc. All Rights Reserved.