Nov 12, 2020
03:26 AM
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
Nov 12, 2020
03:21 AM
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
Nov 12, 2020
03:16 AM
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
Oct 23, 2020
04:30 AM
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
Oct 23, 2020
04:20 AM
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
Sep 24, 2020
04:25 AM
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
Sep 03, 2020
12:15 AM
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
Aug 13, 2020
12:43 AM
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
Jul 30, 2020
01:42 AM
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
Jul 08, 2020
12:58 AM
Overview of Transfer Split functionality in LLM can found in this article .
Steps to follow when we split portion of quantity from the order line of source account to Target Account(Split done in End User Portal) is as below.
Pre-requisite:
Check if the Email type ‘Entitlement Allocation Email’ is present under the Administer -> List Email Templates.
1)Create Account and Entitle the account.
2)Allocations as seen in PP.
3)Allocation Account in EP.
Same Activation Code is seen in EP and PP.
4)Split in EP as shown below.
We use ‘Select All’ to notify all the members of the Allocation Account or use the checkbox to notify any specific members.
5)After Split in EP. We see that new Activation Code is created for quantity 59.
6) Allocations as seen in PP.
7)As we have setup the ‘Entitlement Allocation Email’ in our PP, Make sure to get an email in the members selected under Step 4 inbox with correct Activation Code after we Split from the EP end.
Note: Kindly split the count in EP if the requirement is to notify the customer ('Entitlement Allocation Email' is used when we split in EP).
Steps to follow when we split portion of quantity from the order line of source account to Target Account(Split done in Producer Portal) is found here .
... View more
Jul 02, 2020
03:57 AM
Overview of Transfer Split functionality in LLM can found in this article .
Steps to follow when we split portion of quantity from the order line of source account to Target Account(Split done in Producer Portal) is as below:
1)Create A source Account and Entitle the account (View Account -> Entitle -> Entitle Account)
2)Create a Target Account.
3)Allocation before Split:
Check for the Activation Code under Allocations (View Entitlement -> View Allocations).
We see that the Allocation is on account YT_Split1 with Activation Code : CAFE-0374-C786-CF3C and Quantity 99.
4)Split a portion of quantity to target account :
Under Allocation Details Split Some Quantity(Quantity taken as 50 in the below example) from Source Account.
After Split we see that the quantity : 50 is under Target Account with New Activation Code, quantity :49 is still under the Source Account with the original Activation Code.
Steps to follow when we split portion of quantity from the order line of source account to Target Account( Split done in End User Portal) is found here .
... View more
Jun 18, 2020
04:14 AM
This article provides an overview of the Transfer Split functionality in LLM. Different use cases with examples have been described in separate articles.
Transfer: Allow a user to transfer all the order lines, their licenses, hosts, their FNE mappings and Devices to another Account. Transfer of a full order will not change ownership of the order, it will still be owned by the original Account.
Transfer of a full order will not be allowed when there are host or device bound fulfillments that cross over to other orders (except for host id ANY/DEMO cases). Activation code upon transfer (only) can be retained – this is controlled by a property and a request has to be made to Revenera if it has to be enabled/disabled.
Split: Allow a user to allocate unfulfilled quantity to another Account (either a regular Account or an Allocation Account). This functionality is available through the UI, XML transaction, and Batch Converter templates. This is not available as a web service. Transaction logging has also been implemented. There is a new template to notify users about the split transaction.
Split can be done in both Producer as well as End user Portal.
The 'Entitlement Allocation Email Template' can be customized in Producer Portal to send out order notification emails after a split done in End User Portal. This can only be triggered from the end user portal.
The property related to Activation Code being changed/retained is applicable for Transfer of entitltements and not for Split.
Implemented for the following issuers: FlexTemplateLicenseIssuer (FLEXTMPL) - FNP certificate FNPLicenseIssuer (FNP) - FNP Trusted Storage GetMultipleKeysFromPoolIssuer (PRDCT_POOL_PER_QTY) - multiple keys from pool for product KeyFromPoolAssignedUserIssuer (PRDCT_POOL_ASN_USR) - keys from pool assigned to user FNE
The user will not be able to split of any quantity for the FlexTemplate License Style if the quantity is set as fixed (which is not very common). FNP-TS does not let you set the quantity to fixed.
It is recommended to split from end user portal because that will trigger an email. But it is also possible to split from Producer Portal.
Moving a device/host will cause an internal split. More details can be found in Moving a Device Host .
Examples of Transfer and Split orders are in the below articles:
Transfer of Entitlement from Source to Target Account : Without mappings,Splits: https://community.flexera.com/t5/FlexNet-Operations-Knowledge/Transfer-of-Entitlement-from-Source-to-Target-Account-Without/ta-p/146442
Transfer Order after splitting some off, to same target account :
https://community.flexera.com/t5/FlexNet-Operations-Knowledge/Transfer-Order-after-splitting-some-off-to-same-target-account/ta-p/156767
Transfer Order after splitting some off, to another target account:
https://community.flexera.com/t5/FlexNet-Operations-Knowledge/Transfer-Order-after-splitting-some-off-to-another-target/ta-p/158490
Split all from the source account to the target account and back: https://community.flexera.com/t5/FlexNet-Operations-Knowledge/Split-all-from-the-source-account-to-the-target-account-and-back/ta-p/149239
Split SOME from Source Account to Target Account :
https://community.flexera.com/t5/FlexNet-Operations-Knowledge/Split-SOME-from-Source-Account-to-Target-Account/ta-p/153271
... View more
Jun 10, 2020
03:34 AM
Using the split line item functionality, it is only possible to split the unfulfilled quantity on a line item.
If a partial quantity of a line item has been fulfilled and this needs to be split, then the following steps can be followed to achieve this.
1) Entitle the account :
Entitle the account on which the Device was added (View Account -> Entitle -> Entitle Account). Create an order line (View Entitlement -> Edit Entitlement -> Add Line items with all details).
2) Add a device,Assign owner and Map Add-ons:
Under Manage Hosts -> Devices -> Add Device.
Under Edit -> Assign Owner, Add the Owner Account details as seen below.
Under Add-ons -> Map Add-ons, Give the number of units to be configurred on the device.
3) Check for the Allocation Details:
View Entitlement - > View Allocation
Full quantity of the order line is allocated to the account owning the entitlement.
4)Move the Device to Other Account:
Manage Hosts -> Search Device -> Edit -> Move Device to target Account.
5) After Moving the device, we observe that an internal split has occurred on the Order Line as seen below.
- Allocations have been assigned to the account that is the new owner of the device, with different Activation Code.
- The allocation quantity will be the quantity that was fulfilled on the device.
- The remaining quantity on the original line item will reduce.
... View more
Jun 04, 2020
02:02 AM
Overview of Transfer Split functionality in LLM can found in this article .
Steps to follow when we split all from the order line of source account and back(Split done in Producer Portal) is as below:
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) - The line item is created, and an activation code is assigned
3) Create a Target Account
4) Check for the Activation Code under Allocations (View Entitlement -> View Allocations).
- The activation code is displayed with full order line quantity
- Under Allocation Details Split all from Source Account.
5) After Split we see that the whole quantity is under Target Account with New Activation Code.
- The target account has a new activation code
- The activation code on the Target Account now has the full order line quantity.
6) Split all back from Target Account to Source Account.
- The Source account has the activation code as seen in Step 4)
- The activation code on the Source Account now has the full order line quantity.
... View more
May 13, 2020
02:32 AM
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
Steps followed:
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) Under Edit Entitlement -> Transfer -> Select Target Account - The available_qty from the source certificate will now be 0 - A new certificate will be created for the target account with a new activation code ( Due to property 'ii' mentioned above) - The quantity from the source certificate will now be on the target certificate
Property to be set for the below mentioned scenario 2:
i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True
Steps followed:
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) Under Edit Entitlement -> Transfer -> Select Target Account - The available_qty from the source certificate will now be 0 - A certificate will be created for the target account Activation Code is retained ( Due to property 'ii' mentioned above) - The quantity from the source certificate will now be on the target certificate
NOTE: Follow the above mentioned steps in the same order When more than one Line Orders are present.
Step 2 gives the details to create Line Orders.
... View more
Latest posts by ythingalaya
Subject | Views | Posted |
---|---|---|
129 | Nov 12, 2020 03:26 AM | |
118 | Nov 12, 2020 03:21 AM | |
130 | Nov 12, 2020 03:16 AM | |
152 | Oct 23, 2020 04:30 AM | |
122 | Oct 23, 2020 04:20 AM | |
178 | Sep 24, 2020 04:25 AM | |
131 | Sep 03, 2020 12:15 AM | |
134 | Aug 13, 2020 12:43 AM | |
177 | Jul 30, 2020 01:42 AM | |
189 | Jul 08, 2020 12:58 AM |
Activity Feed
- Posted Split partial from third account back to second account on FlexNet Operations Knowledge Base. Nov 12, 2020 03:26 AM
- Posted Split all from Second Account to Third on FlexNet Operations Knowledge Base. Nov 12, 2020 03:21 AM
- Posted Split to another account that already has an active cert for the order line: on FlexNet Operations Knowledge Base. Nov 12, 2020 03:16 AM
- Posted Transfer order that has a server and a device and multiple mappings per host on FlexNet Operations Knowledge Base. Oct 23, 2020 04:30 AM
- Posted Transfer order that has a server and a device and multiple mappings per host on FlexNet Operations Knowledge Base. Oct 23, 2020 04:20 AM
- Posted Transfer order which takes a device with it on FlexNet Operations Knowledge Base. Sep 24, 2020 04:25 AM
- Posted Transfer order twice and then back to the originating account on FlexNet Operations Knowledge Base. Sep 03, 2020 12:15 AM
- Tagged Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:45 AM
- Tagged Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:45 AM
- Tagged Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:45 AM
- Tagged Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:45 AM
- Tagged Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:45 AM
- Tagged Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:45 AM
- Posted Transfer Order after splitting some off, to another target account on FlexNet Operations Knowledge Base. Aug 13, 2020 12:43 AM
- Posted Transfer Order after splitting some off, to same target account on FlexNet Operations Knowledge Base. Jul 30, 2020 01:42 AM
- Posted Split SOME from Source Account to Target Account - End User Portal on FlexNet Operations Knowledge Base. Jul 08, 2020 12:58 AM
- Posted Split SOME from Source Account to Target Account - Producer Portal on FlexNet Operations Knowledge Base. Jul 02, 2020 03:57 AM
- Posted Transfer Split functionality in LLM on FlexNet Operations Knowledge Base. Jun 18, 2020 04:14 AM
- Posted Moving a device/host will cause an internal split with add-ons mapped on FlexNet Operations Knowledge Base. Jun 10, 2020 03:34 AM
- Posted Split all from the source account to the target account and back on FlexNet Operations Knowledge Base. Jun 04, 2020 02:02 AM