SEC_SQLI or Secure SQL Internal VARA objects retrieve values from the Automation Engine database in a secure manner. The difference between SQLI (SQL Internal) and SEC_SQLI VARA objects is that with SEC_SQLI variables can always be inserted in the SQL statements regardless of the VAR_SECURITY_LEVEL setting in the UC_SYSTEM_SETTINGS - Systemwide Settings variable. To include variables in the SQL, you need to use bind parameters. In doing so, you cannot compose SQL statements, and this protects the database from the risk of an SQL injection.

As in SQLI VARA objects, the variable values in SEC_SQLI are directly retrieved from the Automation Engine database. This means that you do not need a database Agent.

For technical reasons, the system cannot check whether only SELECT commands are used in the variable SQL.

Important Considerations

When using SEC_SQLI VARA objects take the following into account:


Defining SEC_SQLI VARA Objects

A SEC_SQLI VARA object definition is made up of the following pages:

Defining the Variables Page

  1. In the Variable Settings section, specify the following:

    • Type

      Read-only, always SQL - internal

    • SQL Server / Oracle / DB2 / PostgreSQL Statement

      Statements used to select specific database entries that serve as variable values. You have two options:

      • Type your statement in the input field
      • Click the icon to open the cell editor and enter your SQL statement

      Maximum length: 4096 characters.

      Important! Variables that are directly specified in SQL are replaced. To include variables, use bind parameters.

  2. In the Bind Parameters section, you insert variable values within SQL statements. You can use variable or VARA object names as bind parameters with any values of your choice. If a variable or VARA object does not exist, no values are replaced but the variable or VARA object name is used. This can cause an error when the variable or VARA object is resolved.

    You can enter the following type of variables and VARA objects:

    • Script variables
    • Object variables
    • Predefined variables
    • Predefined and user-defined VARA objects

    Each line in the table represents one bind parameter.

    Supported Data Types and Input Formats

    • Date: yyyy-mm-dd
    • Time: hh:mm:ss
    • Timestamp: yyyy-mm-dd hh:mm:ss
    • String: any string
    • Boolean: possible values: 0 / 1 or true / false
    • Number: no thousand separator, a decimal point as a decimal separator


    • Only the field types and formats previously listed are supported
    • Data types are not converted (no conversion from timestamp to date)
    • Inserting an invalid value causes an error when the SQL commands are processed
    • The VAR_SECURITY_LEVEL variable does not impose any limitations
    • In the SQL statements, you must use a "?" character at every location where the replaced value of a bind parameter should be inserted. A bind parameter must exist for each "?". Ensure that you maintain the correct order (table).
    • You cannot use bind parameters multiple times
  3. Define the Data Types and Formatting.
  4. Define the Script Access.
  5. If you are logged in to Client 0, an additional section is available. For more information, see Client 0 VARA Objects in Other Clients.
  6. To run a command, select it and click Preview. The statements are executed and their results displayed. The preview function serves to check for potential errors in the database statements (for example, it the data type of the VARA object and of the database do not match).


    The following SQL statement is entered in the SQL Server Statement field. The values of the bind variables replace the "?" characters.

    select ah_name as ObjectName,ah_timestamp1 as ActivationTime,ah_timestamp2 as StartTime,ah_timestamp4 as EndTime from ah

    where ah_client = ?

    and ah_otype = ?

    and ah_deleteflag = ?

    and ah_hostdst = ?

    order by ah_name asc

  7. Save your changes.

See also: