ware vendor . The user has no way of preventing or skipping them . If there is a conflict in the sequence ( e . g . other licenses not activating or deactivating after a license has been withdrawn ), only the actions initiated by the vendor are executed . This differs somewhat from the current process which would have terminated completely and returned an error message in such instances .
No need to worry if you have made a mistake or if you have to cancel a transaction : You can simply withdraw the license , and you can rest assured that it will actually be taken away from the user at the next possible point .
Replacing Licenses Withdrawing licenses might not be enough . We may want to replace a license for many reasons , be there a typo in the licensing conditions , a revised order , or a change in the actual product that we want existing clients to benefit from as well . This could be done by “ selling ” an update or upgrade for free , but this comes at a price that we might only realize later on : When the licenses are transferred at some later point in time ( i . e . moved from one CmContainer to another ), all original licenses and all of their updates first need to be returned to CodeMeter License Central and then downloaded into the new CmContainer . This makes for unnecessarily complicated calculations , and the user needs to know all applicable ticket numbers . The data on the tickets will also become more complex every time and might cause utter confusion for everybody involved .
The basic idea is to replace the old license with a new one . As soon as the old license has been replaced , it will disappear from the ticket . It remains in the sales and activation history , but it is gone for good from the ticket .
This works by withdrawing the old license according to the same rules and the same processes used for regular license withdrawals . If the license in question is currently available in CodeMeter License Central , it is simply replaced with a new one on the same ticket . If it is currently with the user , it will be withdrawn and a new license activated at the next possible opportunity . The only difference concerns the return of the old license in this process : The new license is not activated directly , but rather made available again for activation on the ticket after the reprogramming .
As with license withdrawals , the user has no way of preventing the license replacement . He might not even notice it , if he only activated another license .
The ability to withdraw and replace licenses adds two more powerful tools to support software vendors ‘ business processes even more accurately and effectively in CodeMeter License Central .
9