Visual Integrator Preferences

Behavior for Runs

Preference	Description
Enable input limit for runs	True enables the input limit when running scripts. False disables the input limit when running scripts (default).
Enable output limit for runs	True enables the output limit when running scripts. False disables the output limit when running scripts (default).
Input limit for runs	Limits the number of input lines to the specified number when running tasks (Run > Run Task). Default is 100. This limit is not applied when running the script (Run > Run Script)
Output limit for runs	Limits the number of output lines to the specified number when running scripts. Default is 1000.
Run Diver after Builder object	True launches ProDiver with the Model created by a Builder output object (default). False does not launch ProDiver.
Run Diver after cBase object	True launches ProDiver with the cBase created by a cBase output object (default). False does not launch ProDiver.
Show Results in Table Viewer after run	True loads the result of a run with a text file output in a new table viewer tab. False does not load the result of a run (default).

Behavior for Tests

Preference	Description
Enable input limit for testing	True enables the input limit when testing scripts. False disables the input limit when testing scripts (default).
Default maximum number of columns shown in the Data View grid	Limits the number of columns displayed in the Data View grid after a test or run is executed. Default is 100.
Include Execute and SQL process objects in test	True includes Execute and SQL process objects when testing scripts. False does not include these objects when testing scripts (default).
Include previous tasks in test	True includes previous tasks when testing scripts (default). Use this when your current task depends on data generated by the previous task and you want to generate that data each time you test. False does not include previous tasks when testing scripts.
Input limit for testing	Limits the number of input lines to the specified number when testing scripts. Default is 100.
Output limit for testing and view data file	The number of output lines of a test or a viewed data file is limited to the specified number. Default is 1000.
Qual string for test input	The specified test will be applied to filter the input when running tests. You must supply the Qual expression. For example, MyColumn = 1, which filters rows in input objects where this column is defined. See Qual Process Object.
Reset limits and Qual string when closing script	True resets test limits and Qual string to default values after closing the script. False does not reset these after closing the script (default).

Functionality

Preference	Description
Automatically make paths relative to the script file	True sets any paths to a file relative to the script location (default). False sets paths to the absolute file location.
Default value for Join.Auto_Sort property	True sets the Auto_Sort attribute to true when you add a new Join object. False sets the Auto_Sort attribute to false when you add a new Join object (default).
Enable audit logging in Integrator scripts (fallback)	True turns on basic audit logging of VI scripts for the logged in Workbench user and displays a table in the script's properties panel when no objects are selected in the task flow panel. See VI Audit Logging. False turns off the audit logging for the logged in Workbench user. NOTE: You can also set this feature at the project level to capture a log of other users who edited the script (Tools > Project Settings > Version Control).
Enable word wrapping when saving script	True enables word wrap (default). False disables word wrap.
File encoding for new objects	Specifies the encoding method used when creating new input objects. Choices are: auto (default) ascii gb18030 latin1 utf-8 unicode unicode-be unicode-le
File encoding when opening scripts	Specifies the encoding method used when opening a script. This attribute can also be used to change an existing script’s encoding, by opening the script in one format (such as, Force ANSI) and changing to the other format (such as, Force UTF8) before saving the script. Autodetect—When writing, write as UTF8. When reading, try to read as UTF8. If that fails, use the current ANSI encoding of the system. Recommended setting except for Scandinavian countries (default). Force UTF8—Use UTF8 encoding. Force ANSI—Use ANSI encoding. Recommended setting for Scandinavian (Danish, Norwegian, Swedish) countries.
File type defaults to Column Headers	True sets file_type for new objects to column_header (default). False sets file types to standard.
Force presence of UID and PWD in SQL connect_string	True only attempts to establish remote connection when the username and password are set in the connection string in the SQL object. This prevents multiple attempts to connect to a remote server when the credentials are not set. In some cases, the connection to a remote server is blocked when multiple connection attempts are made (default). False always attempts to establish a remote connection.
ODBC connection timeout for fetching available tables and schemas (in seconds)	Specifies amount of time, in seconds, spent fetching tables and schemas from an ODBC database before timing out. Default is 15 seconds.

Interface

Preference	Description
Show tooltips in the calc string edit box	True displays tooltips in the definitions grid of the Calc object (default). False hides tooltips.
Show tooltips on the task canvas	True displays tooltips in the Task Flow (default). False hides tooltips.
Sort calc functions by category	True sorts calc functions by category in Calc objects (default). False sorts calc functions alphabetically.
Sort data flow alphabetically	True sorts data columns alphabetically. False sorts data columns in order of appearance in the input files and in order of definition in consecutive objects (default).
Warn for objects with no notes	True makes having a note (comment) a requirement for each object, which turns on the red bar across the top of the object to show that it is incomplete when lacking a note. False does not require each object to have notes (default).

Misc

Preference	Description
Add a suffix based on a regular expression applied on the taskname	True applies a suffix to objects based on the task name. False does not apply a suffix to objects (default). Adding a suffix based on the task name is useful for searching logs. Task names are case sensitive.
Regular expression used on the taskname to set as suffix on the node name	Define a regular expression to generate the suffix. For example: (s[0-9]{3})-(t[0-9]{3}) There is no limit to the complexity of the pattern.
Separator used between the custom node and the suffix based on the taskname	Enter a character to use between the generated name and the custom suffix—hyphen (-) is suggested.

Preference

Description

Add a suffix based on a regular expression applied on the taskname

True applies a suffix to objects based on the task name.

False does not apply a suffix to objects (default).

Adding a suffix based on the task name is useful for searching logs. Task names are case sensitive.

Regular expression used on the taskname to set as suffix on the node name

Define a regular expression to generate the suffix. For example:

(s[0-9]{3})-(t[0-9]{3})

There is no limit to the complexity of the pattern.

Separator used between the custom node and the suffix based on the taskname

Enter a character to use between the generated name and the custom suffix—hyphen (-) is suggested.

Example use of setting a suffix with a regular expression

Create a script named: s010-sales.int.
Create a new task named: s010-t020 Prepare data.
Set Add a suffix. based on a regular expression applied on a taskname preference to True (Tools > Preferences > Visual Integrator > Misc).
Define a regular expression such as (s[0-9]{3})-(t[0-9]{3}) and set a separator—hyphen (-) is suggested.

In this example, the regular expression expects a task name starting with the letter s, followed by three numbers between zero and nine, followed by a hyphen (-), followed by the letter t, followed by three numbers between zero and nine.
Create a new Filein object.

Note the name is Filein-1-FIN-s010-t020 instead of the normal Filein-1-FIN.

If you change the task name to s010-t025, then all objects in the task created after setting this preference are automatically renamed to that suffix.

If you change the regular expression in the VI preferences to (..*), then the entire task name becomes the suffix. For example, Filein-1-FIN-s010-t020 Prepare data instead of the normal Filein-1-FIN.