Configuration Options

Click on a parameter in the list in order to view the configuration options for the selected parameter.

• Data type

  This value is determined by the parameter definition in the database.

• Numeric scale

  Specify the number of decimal places to use for rounding (numeric values only).

• Display text

  The string that will be displayed when the user is prompted for the value at execution time.

• Default value

  A value that will be used by default when no value is supplied. Where appropriate, type a suitable default value in the edit box; otherwise, leave the box blank.

• Value is required

  When this option is enabled, a blank value will not be accepted (unless a default value has been specified)

• Input option

  This option determines the manner in which the user will be prompted for a value.

Option	Description
None	The value is set internally by the application. The user will not be asked to enter a value.
Default value	The specified default value will be used. The user will not be asked to enter a value.
Enter value	The user must type a value (or pick it from a calendar, in the case of a date field)
Pick list	The user must pick a value (or values) from a predefined pick list. Click the ellipses button to enter the SQL statement that must be executed in order to build the pick list. Where applicable, enable the multi-select option to allow the user to select more than one value.

The following SQL is designed to return a list of projects as a pick list for the @prmProject parameter.

Note the use of the [$SCHEMA]  replacement token in the body of the SQL statement. At execution time, this token will automatically be replaced by the OCRIS database schema name (usually dbo) in order to properly qualify the database object name.

Click the New toolbutton to start a new (blank) script.

Click Load to load the SQL statement from an existing text file.

Click Save to save the SQL statement to a text file.

Click Execute to check the query syntax for errors. If the query returns a result, then the syntax is sound (even if the result set is empty).

The queries are executed using the credentials of the end user; therefore, base your SQL syntax on objects for which the end user will always have the appropriate read or execute privileges