Help files

Tokens

Compiling your Processes so that to be executed on other machines is a very important feature of WinAutomation.

From WinAutomation version 7 and later, you are able to license your compiled executables. You can do so using Tokens.

There are two ways with which you may license your compiled Processes. For these two ways, you can purchase run-time tokens through our User Area.

In the screen-shot below you can see the purchased tokens and their status. Clicking the "Add Tokens" button, you can purchase new tokens.

generateexe-userarea.png

After each purchase of tokens, you are being provided with a Compilation ID which should be filled in the respective field of WinAutomation Console > Options > Setting > Exe tab.

In case the target machine already has the same version of WinAutomation or later installed running under a valid license, there will be no tokens consumed for that particular execution.

  • Per Machine

Using the Per Machine method to generate your compiled Processes, you have the ability to run as many compiled Processes as you wish on one machine consuming only one token as long as it has been exported through the same developer's WinAutomation.

  • Per Machine with an activation code

Using the Per Machine method to generate your compiled Processes, you have the ability to run as many compiled Processes as you wish on one machine consuming only one token as long as it has been exported through the same developer's WinAutomation. However, the process requires an activation code provided from 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.

NOTES:

  • In case the target machine already has the same WinAutomation version or later installed running under a valid license, it is very important to make sure that the “WinAutomation Service” is running so that no token is being consumed.

  • In case a user re-installs Windows on his machine, it is being identified as a new machine. As a result, a new executable would have been consumed.

  • An executable compiled without a Compilation ID, will only run on a machine with the same WinAutomation version or later installed and the service running.

  • In case a process re-compiles after a change or edit, there will be no second token consumed. Please note, that copying a process or saving a process as, creates a new process in which case a second run, would consume one more token. The same applies when one exports and imports a process in a database.