Quercus User Guide<>

Embedded forms

Standalone and embedded forms

The Quercus Classic Interface consists of a number of Oracle data entry forms.

You can run Quercus Classic Interface in two modes:

in standalone mode as a Java application which runs outside the browser

in embedded mode as an application that runs within the Quercus browser interface

The appearance of the two modes is shown below.

The Quercus Classic Interface running in ‘traditional’ mode as a standalone Java application

The Quercus Classic Interface embedded within the Quercus Menu browser interface

Who should use Quercus Classic Interface in standalone mode?

Expert users who perform a wide range of tasks using the Quercus Classic Interface

Users who prefer to keep the Quercus Classic Interface open for the duration of a Quercus session

Who should use Quercus Classic Interface in embedded mode?

Occasional users of the Classic Interface — who use it for a limited number of tasks

Users who usually perform the same task in Classic Interface and who use a limited number of menu options

Selecting standalone or embedded modes

Whether forms display in standalone or embedded mode is determined by the following parameter settings:

Parameter

Description

FORMS.INTEGRATION_ENABLED

This determines whether or not the Quercus Menu Classic Interface will run in standalone or embedded mode.

FORMS.INTEGRATION_ENABLED = TRUE — will run in embedded mode

FORMS.INTEGRATION_ENABLED = FALSE — will run in standalone mode

FORMS.LAUNCH_URL

The URL used to launch Quercus Menu Classic Interface.

If the application is hosted on a different server to the Quercus installation you must enter the full URL (beginning http://)

The URL syntax is shown below:

http://<hostname>:<port>/forms/frmservlet?config=#CONFIG#&userid=#KEY_NAME#/#KEY_SECRET#@<database>

This is the standard URL to launch the Classic Interface application with the following substitution strings:

#CONFIG#

#KEY_NAME#

#KEY_SECRET#

For this to work individual users must enter their Classic Interface username and password in the MyProfile section in Quercus.

Example URL

http://cit-test11g-as:8090/forms/frmservlet?config=quercusplus&userid=#KEY_NAME#/#KEY_SECRET#@srslive

FORMS.SSO_ENABLED

This determines whether or not single sign-on is enabled for Quercus Menu Classic Interface. If single sign-on is enabled you can enter your sign-on credentials (user name and password) for forms using the SET CLASSIC CREDENTIALS option accessible through the My Profile link. Once you have done this, you will not have to re-enter your credentials each time you launch Classic Interface.

FORMS.SSO_ENABLED = TRUE — single sign-on is enabled

FORMS.SSO_ENABLED = FALSE — single sign-on is not enabled

To change the forms parameter settings

Note: you must have the correct administrator-level permissions in order to access Control Centre and change the parameters.

1Login to Quercus with administrator permissions and select Control Centre Set-up.

2Select Parameters.

3In the Namespace pick-list select Any or Quercus Menu.

4In the Search field type forms.

The FORMS.INTEGRATION_ENABLED, FORMS.LAUNCH_URL and FORMS.SSO_ENABLED parameters are listed.

5Choose the parameter you want to change and click the corresponding Edit icon .

The Edit Parameter screen opens.

6Change the Value to the desired setting and click Save.

Standalone forms

In standalone mode Quercus Classic Interface is launched by clicking the Classic Interface button on the Home screen.

This starts a Java application which runs independently — in a different window — from the browser application used to launch it.

So if you close down your browser session Quercus Menu Classic Interface continues to run.

Because Classic Interface and the browser session are independent they will not interfere with each other. Tasks you perform in the browser will not suspend or close your Classic Interface session.

In standalone mode you can update the same records from either the Classic Interface or from the browser. If you do this, clicking Save (Classic Interface) or OK (browser interface) will write the associated screen of data to the database. Neither application (Classic Interface or browser) prevents the other from writing to the database.

Embedded forms

In embedded mode Quercus Menu Classic Interface is (also) launched by clicking the Classic Interface button on the Home screen.

This opens the Quercus Classic Interface interface embedded within the Home tab of Quercus Menu.

The full Quercus Menu Classic Interface functionality is available to you. Access to individual forms is dependent upon the access permissions level associated with your user profile.

Warning: the Quercus Classic Interface session initiated in this way will last only as long as the Home tab retains focus within the Quercus Menu application. This means that if you click another tab within Quercus Menu (such as Students or Courses) the Classic Interface session will end. If you have modified the data within a form and you have not saved the form, you will lose the changes.

Note: if you change browser tabs (as opposed to the Quercus Menu tabs) or move focus away from the browser to another application the Classic Interface session will not end.

Single sign-on to Classic Interface

You can configure Quercus Menu so that you do not need to enter your username and password each time you open Classic Interface — this is known as single sign-on.

To enable single sign-on

1Change the FORMS.SSO_ENABLED parameter to TRUE (see To change the forms parameter settings),

2Click the My Profile link at the top of the screen.

3In the TASKS links on the right of the screen click SET CLASSIC CREDENTIALS.

4Enter your user name and password for Classic Interface and click Save.