Managing Changes to Deployed Cartridges

You cannot deploy modified versions of existing deployed cartridges with the same name and version - Design Studio always increments the version number by default. However, if you have small changes to make that do not include changes to the order template or data dictionary, you can override the existing cartridge.

For larger changes to a cartridge, including introducing new tasks, changing data types, or adding new orders, you should deploy a new version of the cartridge. Otherwise, you might encounter errors such as missing or extra nodes when running orders.

If orders are originating in an upstream system, they won't automatically be routed to the new cartridge. Upstream systems must be modified so that new orders specifically target the new version of the cartridge.

OSM performance can be impacted if you have many versions of a cartridge deployed at the same time. For example, you might experience slower Worklist response time. Factors which contribute to possible performance issues when you have multiple cartridge versions include the number of versions, the design complexity of your cartridges including the number of tasks in your orders, the number of OSM users, your hardware and so on.