Modules > Asset Management > Software License Management > Authorizing Software > Software Request Portal

The operation of the Software Request Portal is guided by several settings in the MSL, Manage Upgrades, and Catch Point (manage) screens.

The following settings are relevant to the Software Request Portal operation and are available for each MSL item. (There are other settings as well, but these are the ones used by the Software Request Portal).

G1 - Generation 1 behavior

G2 - Generation 2 behavior

Assign authorizations	G1 - If not set to Assign to Device then this title will not be available through the Software Request Portal, regardless of any of the other settings. G2 - no impact to portal.
Item is allowed to be requested (workstation or server)	If checked, the item will be presented to the end user via the Software Request Portal for possible selection based on the request type. Server request types will show any title checked for server. Workstation request types will show any title checked for workstations. The Gen 1 SRP handles only workstation requests, therefore only honors the checkbox for workstations.
Item requires approval for installation	If checked, the item will be routed to an approving official via an email approval request. The requested MSL item will not be authorized until approval is received back from the approving official. If not checked, the item will be authorized immediately upon completion of the request.
Market Price	Defines the current market price for the application. If the SLMWhatToCharge setting is set to Market Price, this will be the price shown to the requester as the price to be charged. This value is also used to decide, based on the SLMASNPriceToMarketPriceTest setting, if incoming ASN software records are to be considered valid licenses.
Price to Charge	Defines the price to charge for the application. If the SLMWhatToCharge setting is set to Charge Price, this will be the price shown to the requester as the price to be charged.
Automated Software Delivery and Installation	This section actually contains three settings, which will be labeled to agree with the Electronic Software Distribution solution (if any) you are using. The screen will usually state which settings must be populated in order to define a package for automated installation. During a request, the Software Request Portal will identify for the end user which requested packages will be sent automatically, based on these settings. For packages that do not have the proper settings populated, the end user is generally told to call the Service Desk or Help Desk for assistance in getting the approved software installed.

The following settings are relevant to the Software Request Portal operation and are available for each Upgrade item. (There are other settings as well, but these are the ones used by the Software Request Portal).

MSL application to which upgrade applies	If the user qualifies for this upgrade, the linked MSL title as defined in this setting will be displayed with the word (** Upgrade) after the title to allow the user to optionally select the upgrade.
Allow to be requested through the Software Request Portal	If not checked, the item will not be made available through the Software Request Portal and will only be handled via back end bulk purchases of upgrade licenses.
Market Price	Defines the current market price for the application. If the SLMWhatToCharge setting is set to Market Price, this will be the price shown to the requester as the price to be charged. This value is also used to decide, based on the SLMASNPriceToMarketPriceTest setting, if incoming ASN software records are to be considered valid licenses.
Price to Charge	Defines the price to charge for the application. If the SLMWhatToCharge setting is set to Charge Price, this will be the price shown to the requester as the price to be charged.
MSL title(s) required to qualify	The user must have an active authorization for one of these titles before the upgrade will be offered.

The following settings are relevant to the Software Request Portal operation and are available through the Catch Point management screen (for the catch point assigned to the portal. (There are other settings as well, but these are the ones used by the Software Request Portal).

This catchpoint fulfills the following role	Should be set to "Software Request Portal"
Allow to be requested through the Software Request Portal	If not checked, the item will not be made available through the Software Request Portal and will only be handled via back end bulk purchases of upgrade licenses.
Route any approvals required through this workflow	G1 - The workflow that has been established to handle approvals. All titles that are marked in the MSL as requiring approval will be submitted to this workflow. G2 - The workflow that has been established to handle approvals for workstation software requests. If the request is for software for a workstation, this workflow will be used.
Route special approvals through this alternate workflow	G1 - (unused). G2 - The workflow that has been established to handle approvals for server software requests. If the request is for server-based software, this workflow will be used.

The following settings are systems settings:

SLMUpgradeMinQualifyingLicense

Specifies the minimum number of available (un-marked) qualifying licenses before the option to select an upgrade is offered. For example, if this setting is currently 10, then at least 10 qualifying licenses that have not yet been marked for upgrade must exist before the user will see an option to select an upgrade for any given title (that has upgrades).

SLMRequestApproverQuery

Specifies the approver look-up that will be performed. This only applies to the G2 portal. G1 performs a cost center / organization lookup by default. Cost Center will cause the look-up to use the workflow automation approvers matrix, which is based on cost center, organization id, and/or department id to determine approver. Basically the approver is the "owner" of the business entity that is purchasing. Contact will cause the look-up to use the contacts-based hierarchy, which is based on the person doing the purchasing.

Settings

Settings