<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Software License Management > Licenses > Upgrades > How Upgrades are handled by Consolidate > Bulk Authorizations

Consolidate handles extending upgrade pricing when using the Bulk Authorize screen.  The following rules are followed:

1.Since Bulk Authorize mimics the behavior of the Software Request Portal, only upgrade titles that have been marked as being allowed to be selected by the Software Request Portal will be honored.  Otherwise, full pricing will be used.

2.The asset number presented for authorization of the upgrade title must currently be authorized for one of the qualifying titles.  (This is usually one or more earlier versions and is set up via the Manage Upgrades screen.)

3.There must be greater than or equal to SLMUpgradeMinQualifyingLicense (which is a system setting) qualifying licenses available that have not been marked to be used to satisfy a previous upgrade request.

In addition. Consolidate will remove the current authorization for the underlying eligible title.  For example, if the upgrade is for Visio 2007 and the eligible title is Visio 2003, then the current authorization for Visio 2003 will be removed.  When the authorization is removed, a package will be staged to be sent to de-install the existing eligible title (if a package has been configured).  If a package to de-install the old title has not been configured, then it is important to ensure the old package is physically removed (if not done automatically by the installation of the upgrade).

NOTE:  When the authorization is removed for the underlying eligible title, the transaction is called an UPGRADEHARVEST.  An upgrade harvest will not stage a credit, since the underlying license to the eligible title must be sacrificed for the upgrade (leaving nothing of value to be eligible for a credit).

NOTE:  Bulk Authorize does not check upgrade constraints (if any have been defined).  There is essentially nothing to check at the time of Bulk Authorize since the upgrade licenses are typically purchased after the Bulk Authorize event.  Therefore, it is up to the purchaser of the upgrade licenses to ensure the proper constraints are met so that the purchased upgrades will properly clear the MIE's logic and be used.