Notifications

31 views

Description

When allocations are created on the entitlements, in addition to entering the Allocated To, the customer can also select the Software Model. Typically, the Software Model selected on the allocation is the same as the software model of the entitlement. If there are downgrades on the entitlement, the value can be different.

We have seen cases where the allocation's software model doesn't point to the entitlement's software model or any of its downgrades. This will result in the allocation not being used during reconciliation.

This can be reproduced if customers are entering allocations for 2 different software models at the same time.

Steps to Reproduce

 

  1. Enter allocations for 2 different software models at the same time.
  2. Verify in allocations (alm_entitlement_asset) if the software model field is actually pointed to the right software model. When the software model is incorrect the reconciliation result would not consider it as allocated.

Workaround

There are two options to fix the allocations:

 

  1. Delete the incorrect allocations and create them again
  2. The following example script can be used to correct the allocations (TEST):

 

======================================================================= 
var grr = new GlideRecord('alm_entitlement'); 

// 'a3f60692db6cdf00b5ffa2364b96195e' is the sys_id of the right Software Model


grr.addQuery('licensed_by.model', 'a3f60692db6cdf00b5ffa2364b96195e'); 
grr.addQuery('allocated_model', '!=', 'a3f60692db6cdf00b5ffa2364b96195e'); 
grr.setValue('allocated_model', 'a3f60692db6cdf00b5ffa2364b96195e'); 
grr.setWorkflow(false); 
grr.updateMultiple(); 
gs.log(grr.getRowCount()); 
======================================================================= 
NOTE: this is only a Sample script, please make sure you have understood the script and made according changes before applying to your instance! 
======================================================================= 

 


Related Problem: PRB1326884

Seen In

Kingston

Intended Fix Version

New York

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2019-05-21 11:41:41
Published:2019-03-08