Solution: This can be achieved by substituting a variable in the License Model, Vendor String attribute.   Details on the variable used: The variable for achieving this is "mappedQuantity". Syntax -  MappedQty:{mappedQuantity} to get the consumed/mapped count.   NOTE: This Vendor String attribute(Left of the screenshot) will be part of the 'Features' response of the License Server in REST API calls as seen in the screenshot attached(Right of the screenshot).       Similarly, you can use EntitlementLineItem.partNumber, EntitlementLineItem.productName,license_type to get the details of the Part number assigned to a Line Item, the product mapped to the Line Item, and the License Type mapped to it. ... View more

Symptoms: When clicked on any "Device" we see the error stating: "notFoundEntity". Flexnet.log shows: 2021-08-09 16:58:28,400 [default task-57] ERROR (fnofacade) [ADMN] Dao Error : BaseProductDAOImpl 2021-08-09 16:58:28,400 [default task-57] ERROR (lfs) [ADMN] notFoundEntity Diagnosis: This is a data issue where LFS is using the base_product_id which is removed on the FNO side. All the devices which don't have BASE_PRODUCT_ID set in LFS_HOST table are getting the BASE_PRODUCT_ID from LFS_HOST_TYPE. Find the base_product_id here. But that BASE_PRODUCT_ID is removed in the FNO database (EMB_BASE_PRODUCT table) causing the error message 'NotFoundEntity' for all of the devices that have this base_product_id. Solution: Remove this base_product_id from the LFS_HOST_TYPE table: update lfs_host_type set base_product_id=null where base_product_id='<ID>' ... View more

Overview of Transfer Split functionality in LLM can found in this  article  .   TransferSplitEnabled = true TransferSplitEnabled.TransferOrderActivationCodeToTarget = true   1)Create Order for Account1     2)View allocation   3)Split some to Account 2   4) create server for Account 1 and allocate some qty on that server, don't generate (now the available count will be set in the cert from account-1)   5)License is not generated, the available count is deducted from the total count that is being assigned to the Add-on:   6)Move the quantity back from Account 2 to Account1. Hence the Activation code of Account 2 is on Account 1 after the transfer.   7)The Addon-s have to be re-mapped on the Server, as the Activation ID present previously is not associated to any entitlement after the transfer: ... View more

What is a pool license? The pool licenses are basically a list of codes that are loaded into the system. When entitlement is created it pulls one of the codes from the pool and associates it with the order. Therefore, you can't manually assign a pool license code. Check for the License Group used on the Catalog/Product if it is pool-type license. When does the Converter template doesn't update License Codes? While uploading the converter template, we manually change the license codes/parameters. As per design and definition, assigning a pool license code is not possible due to which converter template doesn't update License Codes. ... View more

Get the associated Activation Code from the Reporter/ from the customer. Goto System -> Transaction History  Entity type -> Line Item -> Entity ID is the Activation Code of the corresponding Entitlement.   ... View more

The export of web service keys for Bulk Entitlement takes the number of keys that are displayed by default on the web service keys page.   To modify this limit goto,  Configure -> User Interface -> Records per Page -> The number per page you want to see example 1000 -> Save. Refresh the Web services key page, now you see 1000 keys are displayed.   To export them, Select All -> Export -> Selected Items.   The XML will now contain 1000 keys after the configuration changes are done as above.   NOTE: This will paginate all the other pages too and not just the web register keys page. ... View more

Overview of Transfer Split functionality in LLM can found in this  article  . 1)Allocation in Third Account (YT_Split3_t)     2)Split Partial from third Account to second Account(YT_Split2_t): Since the certificate of the second account now has status cancelled, the application should create a new certificate for the second account (YT_Split2_t) with a new activation code The certificate from the third account should keep its own activation code Eg : We split quantity 30 from Third Account (YT_Split3_t) to Second Account (YT_Split2_t) New Activation Code is seen for Account YT_Split2_t       NOTE :  Do this Action in EP if you want an email to be sent to the customer. ... View more

Overview of Transfer Split functionality in LLM can found in this  article  .  1)Before the Split: Split some (Quantity 20) from the source account to the Second account(YT_Split2_t). We see that the quantity 20 is under Second Account with the new Activation Code. The activation code of the original owner(YT_Split2) remains unchanged.   2) After splitting the remaining quantity, we see that the whole quantity is under Target Account which is the second Account with the Activation Code retained. The available_qty from the source certificate will now be 0 The quantity from the source certificate will now be on the target certificate       3)Create a third Account   4) Now Split All from Second Account to third Account The Third/Target Account(YT_Split3_t) will get its own Certificate for its share of the Order Line and its own activation code. The activation code of the original owner remains but the certificate status will go to cancel Check the quantities     NOTE :  Do this Action in EP if you want an email to be sent to the customer. ... View more

Overview of Transfer Split functionality in LLM can found in this  article  . 1)Entitle the Source Account (View Account -> Entitle -> Entitle Account) 2)Create an order line (View Entitlement -> Edit Entitlement -> Add Line items with all details)    - Certificate from the source account will keep its activation code and will remain ACTIVE                     3) Create a Target Account      4) Make sure to check no mappings, splits are active on the source account        5)Check for the Activation Code under Allocations ( View Entitlement -> View Allocations).          Under Allocation Details before Split.   6)Before the Complete Split: Split some(Quantity 20) from the source account to the target account(YT_Split2_t). We see that the quantity 20 is under Target Account with the new Activation Code. The activation code of the original owner(YT_Split2) remains unchanged.     7) After splitting the remaining quantity, we see that the whole quantity is under Target Account with the Activation Code retained. The available_qty from the source certificate will now be 0 The quantity from the source certificate will now be on the target certificate              NOTE : Do this Action in EP if you want an email to be sent to the customer.   ... View more

Overview of Transfer Split functionality in LLM can found in this article . Scenario One is mentioned here .   Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create order lines in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA7 for all the line items.     3) Create Target Account:   4) Create new Device and map full quantity from line 1 and partial quantity from line 2, generate the response.     5) Create new Server and map full qty from line 3 and partial qty from line 4, don't generate the response   6)Transfer the Order: We see that allocations are moved from YT_SA7 to YT_TA7. Activation Code remains the same due to the property mentioned in ii)     7) After Transfer of Entitlements, we see that the Device which was under YT_SA7 is under YT_TA7(Target Account) The device should be moved to the target account The device should still have the same licenses on it after the transfer       😎 After Transfer of Entitlements, we see that the Server which was under YT_SA7 is under YT_TA7(Target Account) The Server should be moved to the target account The Server should still have the same licenses on it after the transfer           9) To confirm the certificates are right generate the license on the server after the transfer order, and make sure the license gets generated.         ... View more

Overview of Transfer Split functionality in LLM can found in this article . Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create order line in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA7 for all the line items.       3) Create Target Account :     4) Create new Device and map full quantity from line 1 and partial quantity from line 2, generate the response.     5) Create new Server and map full qty from line 3 and partial qty from line 4, don't generate the response     6)Transfer the Order: We see that allocations are moved from YT_SA7 to YT_TA7. Activation Code changes due to the property mentioned in ii)     7) After Transfer of Entitlements, we see that the Device which was under YT_SA7 is under YT_TA7(Target Account) The device should be moved to the target account The device should have the licenses with different Activation Codes due to property ii) on it after the transfer       8 ) After Transfer of Entitlements, we see that the Server which was under YT_SA7 is under YT_TA7(Target Account) The Server should be moved to the target account The Server should have the licenses with different Activation Codes due to property ii) on it after the transfer             9) To confirm the certificates are right generate the license on the server after the transfer order, and make sure the license gets generated.     Scenario 2 is mentioned here  .       ... View more

Overview of Transfer Split functionality in LLM can found in this article . Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create order line in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_S1 for both the line items.       3) Create Target Account :     4) Create Device, Map Add-ons from the order created above and Generate the File:     5)Transfer the Order: We see that allocations are moved from YT_S1 to YT_T1. Activation Code changes due to the property mentioned in ii)     6) After Transfer of Entitlements, we see that the Device which was under YT_S1 is under YT_T1(Target Account) The device should be moved to the target account The device should still have the same licenses on it after the transfer       7) Remove Add-ons from the Device. The removal of the add-ons should put the available count back on the right order. Removed add-ons with units 5 under Activation Code 2994-5452-0145-88D9 and 7 under CB45-4D8C-6D2E-519D. Remaining 3 under Activation Code CB45-4D8C-6D2E-519D is still mapped to the device. The remaining quantity 17 are available back on the right line item when we try to re-map the add-ons.                     Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_S1 for both the line items.     3) Create Target Account:   4) Create Device, Map Add-ons from the order created above and Generate the File:       5)Transfer the Order: We see that allocations are moved from YT_S1 to YT_T1. Activation Code remains same due to the property mentioned in ii)       6) After Transfer of Entitlements, we see that the Device which was under YT_S1 is under YT_T1(Target Account) The device should be moved to the target account The device should still have the same licenses on it after the transfer     7) Remove Add-ons from the Device. The removal of the add-ons should put the available count back on the right order. Removed add-ons with units 5 under Activation Code 21A5-376D-59EA-08F0and 7 under 9B4D-E517-D6AC-04C1 Remaining 3 under Activation Code 9B4D-E517-D6AC-04C1 is still mapped to the device. The remaining quantity 17 are available back on the right line item when we try to re-map the add-ons.         ... View more

Overview of Transfer Split functionality in LLM can found in this article .   Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.         2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA6 for both the line items.       3) Create 2 Target Accounts :         4) Transfer from source to target account 1 (YT_TA6) : Due to the Property (ii) mentioned above, when we transfer from source to target account, New Activation Code is created on the Target Account 1(YT_TA6)       5)Transfer Order  from Target account 1 (YT_TA6) to target account 2 (YT_TA61):  Due to the Property (ii) mentioned above when we transfer from Target Account 1 to Target Account 2, New Activation Code is created on the Target Account 2(YT_TA61)         6) Transfer From Target Account 2 to Source Account: All allocations are owned by the source account. Activation code is the same in source account as seen in Step 2.       Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA6 for both the line items.     3) Create 2 Target Accounts:         4) Transfer from source to target account 1 (YT_TA6) : - Due to the Property (ii) mentioned above when we transfer from source(YT_SA6) to target account, Activation Code is retained on the Target Account 1(YT_TA6)         5)Transfer Order  from Target account 1 (YT_TA6) to target account 2 (YT_TA61):  Due to the Property (ii) mentioned above when we transfer from Target Account 1 to Target Account 2, Activation Code is retained on the Target Account 2(YT_TA61)         6) Transfer From Target Account 2 to Source Account: All allocations are owned by the source account. Activation code is the retained in source account as due to the Property (ii) mentioned above.       ... View more

Overview of Transfer Split functionality in LLM can found in this article .   Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.     2)Allocation before Split: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA4 for both the line items.       3) Create 2 Target Accounts :       4)Split a portion of quantity from One Line Item to target account 1 (YT_TA4) : Under Allocation Details Split Some Quantity(Quantity taken as 45 in the below example) from Source Account under Line Item 1. After Split we see that the quantity : 45 is under Target Account 1 with New Activation Code, and remaining quantity of 45 for this line item is under the Source Account with the original Activation Code. The second line item remains unchanged, with quantity of 10, still having the original Activation Code.         5)Transfer Order to target account 2 (YT_TA41): As you can see from the screenshot,  When we transfer from Source to Target Account 2, new Activation Code is generated for both the Line Items that belonged to the source account, due to the property (ii) mentioned above. Allocation of 45 for Line Item 1(Allocated through Split in Step 4) continues to remain for Target Account 1(YT_TA4) with Activation Code at the time of Split.         Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.     2)Allocation before Split: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA4 for both the line items.     3) Create 2 Target Accounts:     4)Split a portion of quantity from One Line Item to target account 1 : Under Allocation Details Split Some Quantity(Quantity taken as 50 in the below example) from Source Account under Line Item 1. After Split we see that the quantity : 50 is under Target Account 1 with New Activation Code, and remaining quantity of 40 for this line item is under the Source Account with the original Activation Code. The second line item remains unchanged, with quantity of 10, still having the original Activation Code.         5)Transfer it to target account 2 (YT_TA41): As you can see from the screenshot,  When we transfer from Source to Target Account 2, Activation Code is retained for both the Line Items that belonged to the source account, due to the property (ii) mentioned above. Allocation of 50 for Line Item 1(Allocated through Split in Step 4) continues to remain for Target Account 1(YT_TA4) with Activation Code at the time of Split.           ... View more

Overview of Transfer Split functionality in LLM can found in this  article  .   Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.       2)Allocation before Split: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA3 for both the line items.   3) Create Target Account :   4)Split a portion of quantity from One Line Item to target account : Under Allocation Details Split Some Quantity(Quantity taken as 9 in the below example) from Source Account under Line Item 1. After Split we see that the quantity : 9 is under Target Account with New Activation Code, quantity :21 and 20 of the respective line items are under the Source Account with the original Activation Code.   5)Transfer it to target account : When we transfer from Source to Target Account, for one line item it retains the Activation Code that was created during split in Step 4. The second line item is transferred, and a new Activation Code is generated due to the property (ii) mentioned above.   6)Transfer back to the original owner: Both the order lines get the Activation Code as mentioned in Step 1 when we transfer from Target to Source.       Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.   2)Allocation before Split: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA3 for both the line items.   3) Create Target Account: 4)Split a portion of quantity from One Line Item to target account : Under Allocation Details Split Some Quantity(Quantity taken as 9 in the below example) from Source Account under Line Item 1. After Split we see that the quantity : 9 is under Target Account with New Activation Code, quantity :21 and 20 of the respective line items are under the Source Account with the original Activation Code.   5)Transfer it to target account : When we transfer from Source to Target Account, for one line item where was already split (quantity 9) in Step 4, Activation Code is retained for the entire line item. The second line item is transferred, and it retains Activation Code from Source Account due to the property (ii) mentioned under Scenario 2.   6)Transfer back to original Account: Activation Code is retained after transferring back the allocations from Target to Source as property (ii) is defined under Scenario 2.         Irrespective of the property, transferring the entitlement back to the "original" source account will retain the activation of on the original source account           ... View more