Variables, as the name suggests, are in contrast to constants (values that remain unchanged). The purpose of using variables is to employ a value that can change based on different scenarios during a process.

Particularly for values that need to be reused, using variables not only enhances the flexibility of the workflow but also reduces the maintenance costs in the long run.

For example, data used multiple times in a process would require multiple times of modifications if not using variables. However, by using variables, we only need to modify the variable value. Then all the commands where the variable is used will update their parameters accordingly.

There are 2 different types of variables in Octoparse RPA: custom variables and flow variables.

Custom variables refer to variables added manually by users themselves.

Currently, Octoparse RPA supports the following 6 types of custom variables:

Please note that we can only choose from 3 types of variables: string, number, and boolean when using the Set Variable command. Whereas, we can choose from 6 types of variables mentioned earlier when customizing variables in the asset area. Besides, we can also set default values for variables and add variable descriptions.

You might also notice that there is a switch button on top to Set as startup parameter for the app you build. By enabling it, a window will pop up for you to fill out the parameter if you run it from the Console page - My Apps as shown in the screenshot below.

However, it will not pop up if you run it from the Editor page.

Startup parameters can be used in scenarios where users need to fill in specific parameters. For example, if you need to input a username and password, you can set it as an app startup parameter in the custom variables. This way, a pop-up window will appear for the user to fill in the login credentials after running the app, hence eliminating the need to fill in the username and password in the Editor page and allowing multiple username and password combinations.

Used for single-line message input into a text box.

Used for multi-line message input into a text box.

Used to select a specific local file.

Used to select a specific local folder.

Used for setting up a dropdown box for selection.

Used for selecting a date to avoid improper date formatting.

Used for selecting a time to avoid improper time formatting.

Used for entering a password where input is hidden by black dots to prevent the display of the actual password contents.

For tasks that have checked the option Set as startup parameter for the app you build, the "Run parameter settings" pop-up will appear each time you run the task. Fill in the parameters as required in the pop-up window and then click "Run app."