Versioning of procedure when importing using swutil IMPORTLIB using an xpdl file
book
Article ID: KB0079251
calendar_today
Updated On:
Products
Versions
TIBCO iProcess Engine (Oracle)
-
TIBCO iProcess Engine (DB2)
-
Description
If prior to importing a procedure using an xpdl file there is no version with 0.0 in the system, the new imported procedure will have version 0.0.
For Example, consider the below 2 scenarios for IMMEDIAT procedure:
Scenario 1: Procedure IMMEDIAT has 3 versions in the system and no version with 0.0
Version PROCEDURE Status 1.0 IMMEDIAT Withdrawn 1.1 IMMEDIAT Withdrawn 1.2 IMMEDIAT Released
In this case, if the IMMEDIAT xpdl procedure file is imported, the new imported version will be 0.0
Result:
Version PROCEDURE Status 0.0 IMMEDIAT Released 1.0 IMMEDIAT Withdrawn 1.1 IMMEDIAT Withdrawn 1.2 IMMEDIAT Withdrawn
Scenario 2: Procedure IMMEDIAT has 3 versions in the system and one of the version is 0.0
Version PROCEDURE Status 0.0 IMMEDIAT Withdrawn 1.0 IMMEDIAT Withdrawn 1.1 IMMEDIAT Released
In this case, if the IMMEDIAT xpdl procedure file is imported, the new imported version will be 1.2
Result:
Version PROCEDURE Status 0.0 IMMEDIAT Withdrawn 1.0 IMMEDIAT Withdrawn 1.1 IMMEDIAT Withdrawn 1.2 IMMEDIAT Released
Issue/Introduction
Versioning of procedure when importing using swutil IMPORTLIB using an xpdl file
Environment
All supported TIBCO iProcess Engine versions.
Resolution
xpdl files do not contain the existing version, they never have. Below is an example of the import of an xpdl file.
Command used ********************************************************************* $ swutil IMPORTLIB iProcesstestImmediateRelease.xpdl '\' -deglnrmiiuuoav +cz XPDL will be imported.
Translate xpdl to xfr, this may take some time. Please waite... Checking Procedure 'IMMEDIAT':
An 'Unreleased'/'Incomplete' procedure already exists; so importing this unreleased version as 'Withdrawn'