Purchase Runtime Tokens

From WinAutomation version 7 and on, with the Professional and the Professional Plus editions, you are able to license your compiled executables. You can do so, using Tokens.
Tokens can be purchased through WinAutomation’s website User Area, by selecting the “Purchase Runtime Tokens” option.


Once you do so, you will see that the available Tokens for purchasing are:
• Per machine
• Per machine with activation code


When you purchase a Token -of any kind of the above-, then in your User Area in “Your Runtime Tokens” section, you will be provided with a Compilation Id. You will also be able to view the type of the Token and information about the Total Tokens purchased, the Used and the Remaining ones.





What is the Compilation ID?


In WinAutomation console in the "Options > Settings > Exe" tab, you can find the “Compilation Id” field. Here you can paste the Compilation Id, in order to generate executables with the Token that corresponds to this Id.




Once you have filled the Compilation Id field, then you can go to the Process you wish to compile and hit the “Generate exe” option from the console’s menu in the “Processes” tab.
Note that no Token will be consumed from the compilation at this point; the Token will be consumed only when attempted to run on the target machine for the first time, as described below.


What is the activation code and how can I set it?


If you have purchased “Per machine with Activation code” Tokens, then in the User Area you will see an option “Manage Activation codes”. If you click on this option, you will be able to create new activation codes.





Here, you can set the Quantity and an optional desired prefix. The quantity can be less or equal to the total Tokens quantity that you have available for the time being. You can generate codes for all the Tokens that you currently have, or for any number of them. After setting the quantity you are able to set an optional case sensitive prefix. Click on “Generate Codes” and a list of codes will automatically be generated for you.
Every time you are compiling a process using a Token with an activation code, then the first time that the executable will run on a machine, it will prompt the user to enter the activation code before starting the execution. Once the code is correctly passed in the popup window, then you will see in the User Area that this code’s status will be “Used”, the code will be striked out and one Token will be consumed.


Why should I use the activation code?


In case that your end-user decides to move an executable on another machine, then another Token from the developer’s basket will be consumed. This may lead to situations, where a user can inadvertently or on purpose “charge” the developer with Tokens while distributing the executable without the developer’s permission.
The activation code is only known to the developer. Therefore, he will be the one passing it on the first execution of the .exe. If the same exe is moved on another machine, it will not run unless the activation code is correct.
The above being the case, the developer’s work is protected from accidental or malicious usage.


How Tokens are being consumed?


A Token WILL NOT BE CONSUMED when:

  • The machine on which the executable is about to run has WinAutomation installed AND the WinAutomation Server service is up and running.
  • In the “C:\Users\...yourusername…\AppData\Local\Softomotive\WinAutomation\Licenses” folder there is already a file created that has already licensed the executable.

A Token WILL BE CONSUMED if:

  • WinAutomation is not installed on the machine
  • WinAutomation is installed on the machine but the WinAutomation Server service is down (not running).
  • There is no file in the “C:\Users\...yourusername…\AppData\Local\Softomotive\WinAutomation\Licenses” folder that can license this executable.


Available Tokens


Per Machine – Description
Using the Per Machine method to generate compiled Processes provides the ability to run unlimited number of compiled Processes on one machine by consuming only one Token, as long as it has been exported through the same Compilation ID. The "Per Machine" Token is only assigned to a machine ID. Hence, if the machine ID changes, another Token needs to be consumed.

  1. Enter the “Per Machine” Compilation Id, found in the User Area, in the “Options > Settings > Exe” Tab of your WinAutomation console.
  2. Generate the executable, by selecting the Process and clicking on the “Generate Exe” option in the Processes Tab.
  3. Move them to the desired machine.
  4. Run it. (Also check How to run a compiled Process with multiple users)


Any executable compiled with the same Compilation Id and executed on the same machine, will not consume any other Tokens.

Per Machine with Activation code – Description
Using the Per Machine method to generate compiled Processes provides the ability to run unlimited number of compiled Processes on one machine by consuming only one Token, as long as it has been exported through the same Compilation ID. The "Per Machine" Token is only assigned to a machine ID. Hence, if the machine ID changes, another Token needs to be consumed. However, the process requires an activation code provided by the developer in order to be executed. In case the activation code is erroneous, no Tokens are being consumed and the process execution does not start. This activation code is requested only the first time a process from this developer is being executed.

  1. Enter the “Per Machine” Compilation Id, found in the User Area, in the  “Options > Settings > Exe” Tab of your WinAutomation console.
  2. Generate the executable, by selecting the Process and clicking on the “Generate Exe” option in the Processes Tab.
  3. Move them to the desired machine.
  4. Run it. (Also check How to run a compiled Process with multiple users)
  5. Enter one of the activation codes that are shown as “Available” in the User Area as described above.

Any executable compiled with the same Compilation Id and executed on above machine, will not consume another Token, nor ask for the activation code again upon running.


*NOTE: During the compilation of a Per Machine with Activation Code executable, do not forget to check the "Require Activation Code" checkbox.




*An exe cannot be converted back to a .waj file (Exported Process)