bundle has its own Product Code, it will appear
as a separate entry during activation. In our
example, all components can be activated
separately. WebDepot therefore displays all six
components as individual products (cf. the top
screenshot).
Merge: The component does not appear
as a separate product during activation. It is
activated transparently in the background as
part of the bundle. If this option is used, once
a bundle has been created, it is a permanent
package and the users can only activate it (or
deactivate it, depending on the settings) as
such. In our example, the setting for the Ultra
suite is changed to merge mode. WebDepot
now shows one bundle that the user can only
activate completely (cf. the screenshot in the
middle).
parameters. These parameters can define an
individual expiration time, a client’s name,
or the number of network licenses when the
ticket is created. These entries are not fixed
settings for the item, as they are only finally
configured when an actual ticket is created. In
our example, no such parameters are used, so
that the option is not necessary.
parameters accordingly in all components. This
makes it easier to produce tickets and remove
one possible source for human error.
Activation Mode
This option is relevant during activation, e.g