Local Agent Variables
A set of activities called "Local Agent Variables" allow to create, update, retrieve and delete local variables. Such variables are then stored within the Windows registry of the local computer (inside a dedicated registry, under a dedicated key).
For a given project, up to 100 variables can be created.
For a given local agent, up to 100 shared variables can be created.
What is the use case for Local Agent Variables?
Local agent variables are variables that are partly persisted (half-life) within the local computer. While Automation variables are defined for the whole life of the automation execution, each time the automation starts the variables are reset. Local variables aim to keep a state between the start of the same automation within the same project or beyond the project. For instance, let's say that you want to count the number of times the automation starts. First, you need to create a local variable called "myAutomationCounter". Then you will increment the variable each time the automation starts. In the end, you can retrieve the values.
What kind of information can be stored?
We strongly advise not to store personal or password-related information. Also, a variable is not meant to store a huge amount of information. Please use a file instead to store a large amount of information. To know more about the size limits for the various registry elements, see Registry Element Size Limits
It is also important to note that misusing the Windows registry can lead to workstation stability problems.
Scope of Local Agent Variables
If the variables that are not "protected" are "shared" within the local agent, you must check within your automation whether these variables are compliant with the rest of the automation flow. You can leverage cipher/decipher before storing the content if needed.