Should reclamation candidates be automatically closed when an allocation has been added?

[Claire Ashdown1]

Hello!

I am trying to understand the intending functionality of the SAM - Updating Existing Reclamation Candidates scheduled job, particularly for reclamation candidates created using the "Remove Unlicensed Installs" remediation option from the License Workbench. When those reclamation candidates are created, they have a justification of "Unallocated". When the software install going away for the device/user, the reclamation candidate task record is automatically closed when the SAM - Updating Existing Reclamation Candidates job runs. However, I would also expect the reclamation candidate task record to be automatically closed if an allocation is created so that the actual justification of "Unallocated" is resolved. It doesn't look like that is happening though. Should it be happening, or is that not expected functionality? Asking before I go submit an Idea to the Idea portal.

A use case for this is, if we notify users via the reclamation candidate process that they shouldn't have a software installed because they aren't allocated, but they can request to keep it by submitting the request for the software, that is the best way of resolving the Unallocated justification situation, by making them allocated. Just having them approve via the approval email in the reclamation workflow doesn't actually fix the unallocated software issue. 

Many thanks for any information about whether having the reclamation candidate close automatically when the user is no longer unallocated is expected OOB functionality or not.