Get Tokens

From WinAutomation version 7 and on, with the Professional and the Professional Plus editions, you are able to license your compiled executable files through the use of Tokens.


Tokens can be purchased through the WinAutomation website, in the 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, you will be provided with a Compilation ID, which will be visible in your User Area in the “Your Runtime Tokens” section. You will also be able to view the type of the available Tokens, and information about the Total Tokens purchased, and how many have been used/are available.



What is the Compilation ID?


In the 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 executable files which will correspond to the Tokens with that specific ID.



Once you have filled the Compilation ID field, then you can select the Process you wish to compile and hit the “Generate Exe” button from the Console 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 you attempt to run the executable file 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, you should be able to see the “Manage Activation Codes” option. By clicking 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 than or equal to the total amount of Tokens that are available. You may generate codes for all the Tokens that you currently own, or for any number of them. After setting the quantity, you may also set an optional (case-sensitive) prefix. Click on “Generate Codes” and a list of codes will automatically be generated for you.


The first time a WinAutomation process (compiled using an activation code) is executed on a specific machine, it will prompt the user to enter the activation code before starting the execution. Once the code is correctly entered in the popup window, the code’s status will be set to “Used”, the code will be struck out and one Token will be consumed. All these changes can be monitored in the User Area.



Why should I use the activation code?



In case your end-user decides to run an executable on another machine, another Token will be consumed from the developer’s account. This may lead to situations where a user can, inadvertently or purposefully, use up the developer's Tokens by distributing the executable without the developer’s permission.


The activation code is only known to the developer. Therefore, they pass it on to the end user on the first execution. If the same executable file is moved to another machine, it will not run unless the activation code is correct.

In this way, the developer’s work is protected from accidental or malicious usage.



When are Tokens consumed?


A Token WILL BE CONSUMED if:

  • WinAutomation is not installed on the machine ==OR== WinAutomation Server service is not running ==OR== the license is expired

=AND=

  • There is no file in the “C:\Users\...yourusername…\AppData\Local\Softomotive\WinAutomation\Licenses” folder that can license this executable. Note that this file is unique for each Compilation ID - if you compile a Process with another Compilation ID, another file will be created and another Token will be consumed.


Available Token Types


Per Machine:


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 using 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 in the “Options > Settings > Exe” Tab of your WinAutomation Console.
  2. Generate the executable file, by selecting the Process and clicking on the “Generate Exe” button in the Processes Tab.
  3. Move the file to the target machine.
  4. Run it.

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:


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 using 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 will be consumed and the process execution will not start. This activation code is requested only the first time a process from this developer is executed.

  1. Enter the “Per Machine” Compilation ID in the “Options > Settings > Exe” Tab of your WinAutomation Console.
  2. Generate the executable file, by selecting the Process and clicking on the “Generate Exe” button in the Processes Tab.
  3. Move the file to the target machine.
  4. Run it.
  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 execution.


Also check How to run a compiled Process with multiple users



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




2nd Note: An exe cannot be converted back to a .waj file (Exported Process)



Technical Support

In order for Softomotive Support to know if the Machine ID of your machine has been modified or not and handle the situation accordingly, follow the steps below, before running your compiled Process for the first time:

  • Open Windows Powershell
  • Run the commands

                (Get-WmiObject Win32_ComputerSystemProduct).UUID

                (Get-WmiObject Win32_OperatingSystem).SerialNumber