Configured Stored Procedures

This section assumes a basic understanding of SQL syntax

User interface objects (UI objects) usually rely on one or more stored procedures to provide the data content required by the application.

A stored procedure usually requires predefined parameters for which values must be supplied at execution time. These parameter values are used to specify the selection criteria on which data retrieval is based.

To maximise flexibility, OCRIS allows these stored procedures and associated parameters to be customised to suit user requirements. The name and definition of any required stored procedure can be changed at the data administrators discretion, provided that the result set returned by the stored procedure meets the compulsory data content requirements (i.e., returns the required columns) and that the name of the stored procedure has the required prefix, viz  "uspUI".

Data content requirements vary from one UI object to the next. To ensure that customised stored procedures meet the minimum requirements, please refer to the implementation example provided in the OCRIS standard database.

Click Add item to add a new configuration, or Properties to modify an exisiting one.

The following discussion is based on a specific example of a stored procedure that has been configured for a paired sample QC chart. (Individual implementations may vary.)