Purpose

To create Callista Connect Self Serve Applications and specify security access levels for applications

SubSystem

Callista Connect

Self Serve Application

This form is used to create Self Serve Applications and maintain the security access for each application. Through Callista Connect's Web Administrator, each institution is able to define these applications as web page content.

Each Self Serve Application is mapped to a System Self Serve Application and is assigned a Self Serve Access Code. This code defines the level of security required to access the application. Self Serve Access Codes are created in the Maintain Self Service Access form (SSFF1600).

This form can also be used to create user-defined applications. The System application USERDEF may be used when it is necessary to impose security over the entire contents of a web page (or pages), rather than only the applications within the page/s.

Security over the entire web page contents (i.e. the application, text blocks, links and other page elements) can be achieved by

• Creating a USERDEF application
• Mapping it to the target web page/s in the Maintain Self Serve Application Page form (SSFF1110) and specifying a web login page code in Maintain Self Serve Configuration (SSFF1200).

Users then see only the login page until they have successfully authenticated and gained access to the target web page containing the application and other page elements.

The web page mapping functionality in SSFF1110 can also be used to group several pages created in the Web Administrator with the one overriding Self Serve Access Code. For example: applications for several enrolment-related activities will or have been developed. These include Change Of Address, Unit Enrolment and Person Statistics. Each of these applications will normally be incorporated in three different web pages in Web Administrator. The institution may prefer these three pages and their applications to be component parts of a larger overarching application (Enrolment), with the same security and access requirements. By creating a USERDEF application called Enrolment in this form and mapping the three pages to the application in SSFF1110, all three pages in the application grouping will have the same level of access. Additionally, if necessary, access to all three can be prevented by selecting the application's Prevent Access checkbox.

The System Application USERDEF enables institutions to build their own applications and integrate them with Callista Connect.

Other features of this form:

• An Authentication Age Timeout can be set for a particular application making the application more secure. The authentication timeout set in this form for the application overrides the Age Timeout set at institution level in the Maintain Self Serve Configuration form (SSFF1200).
• A maximum selection number and a maximum display selection number can be set for Self Serve Applications. In the current release, these limits can only be set for the Self Serve Application mapped to the System Self Serve Application UOO-SELECT (Unit Offering Option Select).
• The Maximum Selection Number for the UOO-SELECT application is used to define the maximum number of unit offering options that can be retrieved in a query. If any more units are found for the query than the Maximum Selection Number, the query aborts and the student is advised to refine the unit offering option search. For example: the number could be set to 100. If a student performs a query that retrieves 100 unit offering options and the query is not yet complete the query is aborted.
• The Maximum Display Selection Number defines the number of unit offering options from the query that will be displayed on the screen at any time. For example: the Maximum Display Selection Number is set to 10. A student's query returns 37 unit offering options. These unit offering options are displayed to the student in four groups (10 + 10 + 10 + 7). Each group is displayed by selecting the NEXT or PREVIOUS options.

Transaction Logging, Receipts and Communication

An administrator must select the Log Transactions check box to ensure that transactions are logged for the context Self Serve application. When a transaction occurs in a transaction application, a log of the transaction will be created. The log includes the before and after record for any transactions.

To enable the display of a receipt for the transaction in Student Connect, the Issue Receipt checkbox must also be selected.

Data in the transactions log will be available for receipt emails set up in the Callista Communications subsystem. i.e. A Communication Template must have been set up in CORW0500 and appropriate Substitution Tags must exist in CORW0400 to input the values into the email, as per the Template.
Only the Log Transactions checkbox needs to be selected to enable the generation of receipt emails by the Communications subsystem. The Issue Receipt and Issue Email checkboxes do not have to be selected.

Note: Some applications are not able to log their details, so even though such an application may have the Log Transaction checkbox set, it will not be able to log the transaction details or generate a receipt.

For information relating to Transaction Logging refer to the 'Connect Transaction Logging' page in the latest callista release - accessed via the Callista Product Centre.
For more information regarding Receipts in Student Connect refer to Receipts (GEN2).

Self Serve Application block

• Self Serve Application
• Description
• System Self Serve Delivery Type (LOV)
• System Self Serve Application (LOV)
• Self Serve Access Code (LOV)
• Authentication Age Time Out
  Setting a timeout requires the user to re-authenticate for secure applications after the specified elapsed time from the previous authentication. For example: If the timeout is set as 00:01:00, users will be required to re-authenticate when navigating to the application one minute after previously being authenticated.
• Prevent Access checkbox
  When this is selected, it prevents user authentication and access to the application. When selected, a message must also be created in the Prevent Access Message field, to provide users with an explanation of the application's inaccessibility. The checkbox is primarily for emergency use. For example: there may be a system problem that necessitates taking the application offline.
• Prevent Access Message
• Maximum Selection Number
• Maximum Display Selection Number
  
  
• Log Transaction checkbox
• Issue Receipt checkbox
• Issue Email checkbox
• Receipt Transaction Email (LOV)
• Override ESAPI Validator Name
• Override ESAPI Validator Error Number

Navigation Buttons

Selecting the System Self Serve Application button navigates to SSFF1120 (Maintain System Self Serve Applications) where the template for the application can be updated by the user.

Selecting the WEB Page Mapping navigates to SSFF1110 to allow a web page or pages to be mapped to a Self Serve Application (see above explanation). Only USERDEF applications are used for this purpose.

Rules/Notes:

Some System Self Serve Applications may need to be mapped to more than one Self Serve Application, depending on which applications the institution wishes to include in the suite of Self-Enrolment Applications. Refer to the PERSON-INQ and ENR-STEPS System Self Serve Applications for further details.

A Self Serve Application with dependent application pages cannot be inserted into a web page in the Web Administrator. That is, it cannot also be used to define the content of a page.

If the Authentication Age Timeout is set to zero, users must re-authenticate each time a secure application is selected.

Authentication Age Timeout must be less than or equal to the system configuration Key Age Timeout (if it exists).

If the Prevent Access checkbox is selected, a Prevent Access Message must be recorded.

The Maximum Selection Number and the Maximum Display Selection Number can only be set for the UOO-SELECT application.

Note:
In order for Add Units and Unit Search Display drop down to work in Shopping Cart you must ensure the Maximum Display Selection Number corresponds to one of the pre-defined display values - 4, 6, 10, 14 or 18. These values come from UOO-SELECT.sssa.html and can be changed by overriding that template.

The Maximum Selection Number cannot be less than the Maximum Display Selection Number.

The lamp EXISTS AS WEB ELEMENT is displayed at the top right of the block, if the context application has been defined as a web element in the Maintain Application page of the Web Administrator.

Applications defined as web elements cannot be mapped to web pages in SSFF1110.

Validations include:

• The 'RECEIPT' application cannot be a transaction application
• You cannot set the Issue Email checkbox, Issue Receipt checkbox or Receipt Transaction Email when the Log Transaction checkbox is not set
• Only an open Email Type can be recorded for the Receipt Transaction Email
• Cannot set the Receipt Transaction Email when the Issue Email checkbox is not set
• The Receipt Transaction Email must be set when the Issue Email checkbox is set
• The System Self Serve Delivery Type must be WEB when the Override ESAPI Validator Name is set.

For more information regarding the ESAPI Validator refer to the 'Configuring ESAPI Validation for Callista Connect' wiki page in the Callista Product Centre.

If invalid characters are detected by the Override ESAPI Validator, then the error defined by the Override ESAPI Validator Error Number is generated.

To create a Self Serve Application:

Record an institution defined Self Serve Application name and description for the Self Serve Application.

Select a System Self Serve Application from the LOV.

Select a System Self Serve Delivery Type..

Define the application's level of security by selecting a Self Serve Access Code form the LOV. Self Serve Access Codes are defined in SSFF1600.