What are Best Practices for Entitlements?

[mrcorbeaux]

Looking for thoughts/opinions on best practices for Entitlements on Software Models.
Is it best to create a new Entitlement when new licenses are purchased? Or just update the Purchased Rights on the existing one?
Example: 10 licenses are purchased under one contract and 5 more are purchased later.

Should there be 1 Entitlement of 15? Or two separate ones?

The problem with multiples is that the SAM Pro Source Request feature (screenshot) will only block a duplicate allocation if the user selects the SW Entitlement record that the user has an existing allocation. Selecting one of the others allows the allocation.
This duplicate request scenario is rare but it does happen.

[Engelica Adalia]

@mrcorbeaux I think it's easier to identify and report if the entitlements are created separately. In some cases, you may want to identify it (e.g. if you purchase perpetual licenses but were only entitled for a certain version based on purchase date). 

SAM Pro source request feature will only search for duplicate allocation on the selected entitlement, so it is possible to assign duplicate license to a user or a device if it was assigned/allocated to another block of entitlement. A work around is to search the user or device under the User Allocations (Assigned to) or Device Allocations (Allocated to) table first - see if there's any licenses assigned before fulfilling the source request task. 

Hope this helps! Please mark the answer as correct and/or helpful based on impact.

[mrcorbeaux]

I'm going to try a different approach.
On the Source Request UI page once the user clicks Allocate then there is a pop-up where user must click OK (image). The page then returns to the sc_request record.

Do you know if its possible to instead direct it back to the sc_task page that sits on the REQ record (the one with the Source Request UI Action)?