|
<< Click to Display Table of Contents >> Navigation: Modules > Asset Management > Software License Management > Authorization Analyzer (Complex license types) > AA Functions > Func50_CreateAuthorization |
Description
This function creates an authorization for the MSL title specified against either the asset or user specified. The MSL title specified can be a title on the customer's (local) MSL, or it may be a title on the Wiki Master MSL. The title may be chosen from a list (at rule design time) or you may use a tag to refer to the mslNo to be authorized (dynamically resolved at run time). When writing a master rule, you should always specify a Wiki Master title.
This function can also require an allocation on the authorization to be. In that case, you will end up with either a properly covered authorization, or no authorization at all.
Processing Notes
This function goes through the following steps to perform the requested authorization:
•Checks to see if an mslNo has been specified
•If an mslNo has not been specified via the list of titles, then checks to see if a tag has been specified. If so, the tag is resolved and translated from wiki to local (if applicable). Note that a tag will NOT override a choice from the list of titles.
•Looks up the MSL record to authorize and checks to see how it is supposed to be authorized (by Device, by User, etc)
•Checks to see if authorization already exists and is still active.
•Checks to see if the mslNo specified is a Wiki Master title. If so, traces that title down to the current customer's MSL. If no local MSL title is linked to the Wiki Master title that has been specified, an Else path is returned.
•Checks to make sure either an asset number has been supplied (if by device) or a ctNo has been supplied (if by user).
•If all checks pass, invokes an MIE web service to create an authorization (and optionally attempt
•To allocate a license to this new authorization)
•If authorization was created successfully, checks to see if allocation was required.
•If allocation was required and was not successful, harvests authorization and reports error
NOTES:
1. If asset number is sent as blank and the MSL title is set to be authorized by device, the asset under test will be used.
2. If the ctNo is sent as zero or blank and the MSL title is set to be authorized by user, the user assigned to the authorization under test will be used.
3. MSL titles set to be authorized by group are not supported by this function.
4. The new authorization will inherit the organization, department, and cost center information from the authorization under test.
5. If the title specified is a Wiki Master title, the authorization created will be for the current customer's linked MSL title (not the Wiki Master)
6. If the “Allocate License Upon Authorization” Input is checked, then you are requiring that the new authorization have a license allocated to it. Use this optional input when you only desire a new authorization with proper coverage, because when this option is used, authorizations that do not get a license properly allocated will be immediately harvested.
Inputs
Parameter |
Explanation |
mslNo |
The mslNo of the MSL title to authorize |
Asset Number |
If the MSL title is authorized by device, this parameter must resolve to the asset tag number of the device to be authorized. Supports tags as well as AA-specific tags. |
Name |
If the MSL title is authorized by user, this parameter must resolve to the primary key value (ctNo) of the user to be authorized. Supports tags as well as AA-specific tags. |
LUR |
Must resolve to a numeric value that will be used as the License Units Required for the authorization. |
mslNo (tag) |
If nothing is selected from the list of titles then this parameter is used (if specified). It is a general or AA-specific tag that resolved to a valid mslNo (either at local or wiki level). |
Enforce chain harvest (Optional) |
If selected, the authorization being created will have the chain harvest flag set. If the parent authorization (the authorization under test) is harvested, then the newly spawned authorization will be deleted also. |
Allocate License Upon Authorization (Optional) |
If selected, the authorization being created will also require allocation during creation. If the allocation fails (no license(s) required does not count as failure), then the entire process is considered a failure and the authorization is harvested to remove the possibility of erroneously creating a deficit. |
Condition for Assets in scope (overrides Asset input above) (Optional) |
This parameter is used if populated. Populate this parameter by choosing a condition for Assets from the dropdown to determine which Assets are to be authorized by this step in the Rule. If populated, this overrides the Asset Number parameter above. |
Outputs
Result |
Result Explanation |
Confidence Adjustment |
Return Value |
True |
No processing errors occurred and the request was successful. |
N |
LUR count authorized |
False |
The MIE could not be contacted to attempt the authorization or a specific Failure Error Code was received when processing |
Y |
-10 = Failure to contact MIE -100 = Required allocation of license(s) failed, Authorization was harvested. -400 = SLM Primitives Authorization attempt failed |
Else |
A processing error or other issue was encountered |
Y (except for -30, authorization exists, no confidence adjustment there) |
0 = general processing error -20 = Errors contacting the MIE -30 = Authorization already exists -301 = Authorization already exists and the LUR was changed -302 = Authorization already exists and the LUR update failed -303 = Authorization already exists, and the MSL has a rule, so no LUR change attempted. -40 = The mslNo specified is a Wiki Master title yet no local title has been linked to it. -50 = No mslNo was sent -60 = MSL title is set to be authorized by group - not supported -70 = MSL title is set to be authorized by device yet no asset number was sent -80 = MSL title is set to be authorized by user yet no ctNo was sent -90 = MSLno specified did not match a valid MSL record. |