Now if you select the 'Run Flow' tab on the interface, you will see the following screen which contains the Flow Path and the Flow Cache Server name at the top. Following that, the Arguments section is completed by putting the Actions (parActions) in the Arguments box.

If you open Mask_1_Prep.cmd (C:\VIPTDM\SubsetCloneAndMaskRun\Mask\MySQL\Mask_1_Prep.cmd), you will see a command script line that contains an example set of Arguments.

To use the command script, cut and paste the relevant actions into the Arguments box. For a full list of Arguments/Parameters.

Here are the contents of the command script Mask_1_Prep.cmd:

call "C:\Program Files\Curiosity\Visual Integration Processor\VIPExecutor.exe"
-parDatabaseType="SQL Server"

The arguments are all the lines that start with 'par…' above. These are the entries that should be included in the Arguments section of the interface.

Two things to note:

  • The Argument values when put into the Arguments box do not need to be quoted.

  • The Debug option is added by ticking the Debug box in top of interface window.

The Parameters (see full list) will be set to defaults on delivery, but the user should check that these are relevant for the Masking task they are creating.

Note: It's a good idea to save your config details to avoid having to fill-in the interface details for future use.   The way to save the file is to go back to the Flow Cache Server tab screen and on the bottom of the screen there is an option to Save Config.

Back in the Run Flow tab, you will see a Create File button on the bottom. The value of this is C:\VIPExcelWork\TestAutomation\stopScheduler.txt. When you put a file name in here and select Create File, a file is created which can be used to stop the scheduler running whenever you want it to stop. The way it works is this: if you have a job running a long time and you want to stop it, you remove the file stopScheduler.txt and the job will be stopped:

If you receive errors messages in the VIP Server Controller, the Log File or Masking Report, please refer to the troubleshooting guide or contact Curiosity on