Configuration Examples

@prmSiteType

The pick list SQL for @prmSiteType is as follows:

Note the use of the [@prmProject] replacement token in the body of the SQL statement. At execution time, this token will automatically be replaced by the project code that was selected in the previous step. In this case the token must be enclosed in single quotes, since the project code is a text literal.

Multi-select is enabled; therefore, the user will be able to select more than one site from the pick list, which is generated by the following SQL:

Note the use of the [@prmProject] and [@prmSiteType] replacement tokens in the body of the SQL statement. At execution time, these tokens will automatically be replaced by the project code and site type code that were selected in the previous steps. In this case the tokens must be enclosed in single quotes, since the codes are both text literals.

 @prmSampleGroup

In this case, a default value of  'ALPHA'  will be used for the sample group code. The user will not be prompted to enter a value for this parameter.

@prmAnalyteCode

In this case the SQL is fairly simple. Note, however, that the user is assumed to have SELECT privileges on the ErmRefAnalyte table (which should normally be the case).

@prmPairSampleGroup

The selection criteria exclude reference samples from the pick list and also ensure that the paired sample group is not the same as the original sample group.

Note that a join to the ErmRefSampleGroup reference table is used to return the description for the sample group code.

It is also possible to extend this syntax in order to include only sample rows that belong to sites that were selected in a previous step. In order to do this, we have to make use of a special function that will parse the site identifiers from the list of identifiers included in the value of parameter @prmSites. By definition, the site identifiers in this list are separated by a tilde character (~).

The SQL for this solution looks as follows: