Best way to remove user allocation (user to entitlement relation records)?

[mike_s]

Is there a proper way to remove User Allocation [alm_entitlement_user] records when a user should no longer be associated to an entitlement?

We are looking to remove these allocations when a user goes inactive. The user is not associated to a software install of the related entitlement anymore, and want to remove the User Allocation record so that the entitlement count is accurate. 

Is there an out of the box way that this should be managed? Or do we just simply deleted that record when no longer needed? I looked at the reclamation process, but that seems to be related to the Software Installations [cmdb_sam_sw_install] table, but doesn't seem to relate to the entitlement records.

[Rohit Lobo]

Mike, I don't think there is an out of the box way to delete user allocations when the user goes inactive. Yes you can delete the allocation manually. Also if you're considering the reclamation workflow to remove installs based on no usage, have you considered expanding the reclamation workflow which reclaims the installs to also find and delete any allocations for this user on entitlements?

[mike_s]

Thanks for the reply and suggestion. We did some more digging around for solutions and it does seem that you will have to just delete the records, as that is the manual process to do as well.

We are looking to see how we will handle this. For now, I think we are just going to run a cleanup once a user goes inactive to at least remove the entitlement records, to help with the compliance count, and perhaps include that into an existing workflow where it may fit.

The main goal was to just focus on the case where users go inactive, and not depend on the usage or OOB checks, which is mainly usage. For example, if a user goes inactive and by nature does not use the product over X days, it should be picked up by the current workflows and calculations. Apparently my stakeholders want to have a more immediate approach, daily if you will, to free up some entitlements for usage before waiting X does to confirm it is not being used the user.

[Community Alums]

Hi Mike,

We solved this issue using the FlowDesigner as below;