Menu Customization

Oracle Clinical provides functions that allow for two levels of customization. These are modifying the menus and implementing API functions.

When Oracle Clinical opens a form, it calls the wnfi procedure from the PL/SQL library. This enables you to set properties for the menu you are customizing. It can be used to update labels for the customizable options, or even to disable them. The procedure itself contains samples.

Other functions customize the Get Next and Get Previous Image options, which are workflow tasks. They allow you to proceed to the next or previous page of a multi-page document from within Oracle Clinical, when you are viewing an image of the document in conjunction with using data entry.

In rxclbcli.pll, there are five functions that are defined to allow you to add your own menu options and functionality to the Data Entry menu. The functions are named CustomPgmUnit1 through CustomPgmUnit5.

The CustomPgmUnit# functions are provided for each custom menu option as a shell. You can add functionality into the data entry system. The return value from these functions is either a null or an error message. If the function returns an error message the value of the error_type is checked, a value of 1 causes a warning message to be displayed. If the error_type's value is 2, an error message is displayed and an error is raised from the calling form.

These functions have arguments that are used to pass data into the function or return data from the function. In the tables describing the arguments the In or Out column has an I for input argument and an O for an output argument.

In the tables the Data types column shows the defined type of data for the variable. Sometimes the data type is defined to be the same as a particular column in a database table. The format that shows this is the database table name, period, column name, followed by % type. For example received_dcis.document_number%type means the data type is defined as the same type used to define the column document_number in the received_dcis table.

For more information, see:

• CustomPgmUnit1
  
• CustomPgmUnit2
  
• CustomPgmUnit3
  
• CustomPgmUnit4
  
• CustomPgmUnit5
  

CustomPgmUnit1

CustomPgmUnit1(document_number, 			nreceived_dci_id,  	nError_type)

Argument	In or Out	Data type
document_number	I	received_dcis.document_number%type
received_dci_id	I	received_dcis.received_dci_id%type
nError_type	O	number

CustomPgmUnit2

CustomPgmUnit2(ndcf_id nError_type)

Argument	In or Out	Data type
ndcf_id	I	data_clarification_forms.dcf_id%type
nError_type	O	number

CustomPgmUnit3

CustomPgmUnit3(nError_type)
nError_type       out number

Argument	In or Out	Data type
nError_type	O	number

CustomPgmUnit4

CustomPgmUnit4(nError_type)

Argument	In or Out	Data type
nError_type	O	number

CustomPgmUnit5

CustomPgmUnit5(nError_type)

Argument	In or Out	Data type
nError_type	O	number