Example of Creating Multiple Upgrade Kits of the Same Type

If you must distribute multiple custom files to different directories, then create an upgrade kit for each destination directory. Set the values of the Minimum Old Version and Maximum Old Version settings of the upgrade kits so that they create an unbroken sequence.

The following example uses the Customer Revision upgrade kit type (component type). The same logic can be used for other types of upgrade kits when you must distribute multiple upgrade kits of the same type.

Create the first upgrade kit (Upgrade Kit 1) in the usual manner. For example, set Minimum Old Version and Maximum Old Version to the null value, and set New Version to 1.

For the next upgrade kit, set Minimum Old Version to 1, Maximum Old Version to 1, New Version to 2, and so on.

If you have to skip a version number for some reason, then set the Minimum Old Version and Maximum Old Version values appropriately. Always set the value of Minimum Old Version to match the value of New Version for the previous active upgrade kit.

In this example, you need three upgrade kits, but Upgrade Kit 2 was skipped and replaced, because it contained one wrong file. The version information would be as shown in Table 7-4.

Table 7-4 Example of Version Settings for Multiple Upgrade Kits with One Skipped Upgrade Kit

Upgrade Kit	Minimum Old Version	Maximum Old Version	New Version
Upgrade Kit 1	Null	Null	1
Upgrade Kit 2 (This upgrade kit contains one wrong file, was never activated, and should be skipped.)	1	1	2
Upgrade Kit 3 (This upgrade kit replaces Upgrade Kit 2.)	1	2	3
Upgrade Kit 4	3	3	4

For more information about the version numbers used by Siebel Anywhere, see "About Siebel Anywhere Version Settings".