Settings

<< Click to Display Table of Contents >>

Navigation:  Modules > Asset Management > Software License Management > Licenses > Software License Allocation > Allocation Constraint Templates >

Settings

License allocation constraint templates have the following main settings:

Setting

Definition

Description

A general description of the constraint template.

Enabled

Must be checked for template to be active.

Perpetually constrain business constraints

If checked, business level constraints (specifically organization, department, and cost center) will be honored perpetually, or until the constraint is lifted.  By default, business level constraints are only honored for first allocation, then lifted.  This is to allow business units to fully participate in the internal software market (credits/debits) concept.  If license allocation remained constrained, that would not allow the license to be "sold" to another business unit.

NOTE:  This setting applies to all business level constraints when checked.  For example, even if you do not include any cost centers in your template, if you check this setting and any individual license records are pushed to the MIE that match the contract for which this template has been assigned, then the license-level business constraint for cost center will be held perpetually.

NOTE: If this setting is on, it will not support the Internal Software Market approach (meaning the license may be "sold" to another business unit but the constraint will not allow it to be allocated.  This setting should be turned off if you wish to set up and run an Internal Software Market.

Constrain allocation to organizations

One or more organizations to which license allocation will be constrained.  If no organizations are selected, then standard constraint behavior will apply for organization (meaning if an organization is contained in the license record, it will be honored as an allocation constraint)

Constrain allocation to departments

One or more departments to which license allocation will be constrained.  If no departments are selected, then standard constraint behavior will apply for departments (meaning if a department is contained in the license record, it will be honored as an allocation constraint)

Constrain allocation to cost centers

One or more cost centers to which license allocation will be constrained.  If no cost centers are selected, then standard constraint behavior will apply for cost centers (meaning if a cost center is contained in the license record, it will be honored as an allocation constraint)

Constrain allocation to device roles

One or more roles to which license allocation will be constrained.  If no roles are selected, then standard constraint behavior will apply for roles (meaning if  one or more roles are defined in the MSL title's record, they will be honored as an allocation constraint)

Constrain allocation to environments

One or more environments to which license allocation will be constrained.  If no environments are selected, then standard constraint behavior will apply for  environments(meaning if  one or more environments are defined in the MSL title's record, they will be honored as an allocation constraint)

Constrain allocation to geographies

One or more geographies to which license allocation will be constrained.  If no geographies are selected, then standard constraint behavior will apply for geographies (meaning if a geography is contained in the license record, it will be honored as an allocation constraint)