ITBM Worker/Planner Definition based Count Incorrect -


Description

Reviewed the DEFN1003811 script, the problem was that it was not accounting for the sys_id of the ITBM Worker Capacity product. It only had the User Product sys id. Adding the correct one into the script does the trick.

@Dileep Singireddy the sys ID for these three products will need to be added to DEFN1003811 to exclude the Worker subscriptions:

IT Business Management - Worker v2
Service Strategy - Worker
IT Business Management - Worker

Steps to Reproduce

1) Ensure the worker license SKU's the instance is subscribed are below

IT Business Management - Worker v2
Service Strategy - Worker
IT Business Management - Worker

2) After upgrading to Paris patch 3 or later, Check the planner license count is showing high number

Workaround

1) Ensure the worker license SKU's the instance is subscribed are below

IT Business Management - Worker v2
Service Strategy - Worker
IT Business Management - Worker
I2 IT Business Management - Worker v2


2) Open usageanalytics_count_cfg record for definition ID DEFN1003811

3) Modify the line 34 in the script as below

Original:

licenseDetailGr.addEncodedQuery('start_date<=javascript:gs.endOfToday()^end_date>=javascript:gs.beginningOfToday()^license_idIN38618f3edb653a000576fb371d9619e9,d64a5883db80fb00d8ccf5771d961941,561f7a72db653a000576fb371d961940,90a5c372dbea50108ae42b69139619dd');

After Modification:

licenseDetailGr.addEncodedQuery('start_date<=javascript:gs.endOfToday()^end_date>=javascript:gs.beginningOfToday()^license_idIN38618f3edb653a000576fb371d9619e9,d64a5883db80fb00d8ccf5771d961941,561f7a72db653a000576fb371d961940,90a5c372dbea50108ae42b69139619dd,22316babdb65e8107e2243c813961977,b9f02f6bdb65e8107e2243c8139619c9,eaa22bafdb65e8107e2243c8139619f2');

4) Verify that the license count is corrected, by executing the definition. Also, do note that, this count will get updated in subscriptions table, only after the scheduled Job runs next time.

Note : After updating the script, please remember to set the "replace_on_upgrade = true" for the corresponding definition record in sys_update_xml table, so that customer gets the latest updated script upon next upgrade.


Related Problem: PRB1463049