Receipt Application

This is a generic application that is embedded in the template of all existing Connect update Applications (Student, Staff, Agent, etc) as long as that application generates a Transaction ID. Otherwise, a receipt will not appear. Clients using the Callista Connect Developers Kit are able to embed this application in their own update applications.

When a successful update occurs within a transaction application, the details of the transaction are logged. Logging the transaction creates a Transaction ID.

This Transaction ID is available to the application that is in context (the logged application).

If the application has the 'Issue Receipt' check box set in Maintain Self Serve Applications (SSFF1100), then the embedded Receipt application is activated and uses the Transaction ID. This is achieved by using the CCEMBED logic.

The parameters that are passed to the CCEMBED call to the RECEIPT application include:

p_transaction_id (The transaction ID generated from logging the parameters of the host application)
p_connect_url (The URL of the Connect server host, obtained via Javascript from the context URL of the page)
p_no_email_ind (This should normally be set to ‘Y’, unless the call to the application is coming from within an email tag substitution function (where we are substituting the BODY tag), in which case it should be set to ‘N’ to prevent an endless loop - see next illustration).

how an endless loop can occur

The transaction ID is used to identify the logged values and is passed to the receipt application as a CCEMBED attribute. The logged values are used in the Receipt Template to build the receipt. Once the receipt is built it is displayed to the application user.

To the user of the Connect Application, it appears within the page that they are reviewing. It appears after the user clicks on the Submit button.

The application template initially only contains basic examples of receipt templates. It is up to system administrators to customise this template to allow for more complex and application specific template formats.

Examples of Receipt Applications

An example of a screen prior to a transaction:

receipt prior to transaction

After the transaction (with generic formatted receipt):

receipt after the transaction

After the transaction (on the eCAF Application page):

receipt for ecaf

After the transaction (on the SUA-UPD Application page):

receipt on SUA UPD page

After the transaction (on the GOVT-STATS Application page):

receipt on GOVT-STATS page

After the transaction (on SUSA-ENR Application page):

receipt on SUSA-ENR page

After the transaction (on the GRDCER Application page):

receipt on GRDCER page

After the transaction (on the SCA-UPD Application page):

receipt on SCA-UPD page

Field Source

Field Source	Field Type	Format	Comments
SSTL.TRANSACTION_ID	Display Field	Number(10)
SSTL..TRANSACTION_TIMESTAMP	Display Field	Date and Time
SSTL.SELF_SERVE_APPLICATION	Display Field	Varchar(10)
SSTL.EMAIL_ISSUED_IND	Hidden Field	Varchar(1)
SSTL.EMAIL_ISSUED_ADDRESS	Display Field	Varchar(500)
SSTD.PARAMETER_SEQUENCE	Hidden Field	Number(10)
SSTD.PROMPT	Display Field	Varchar(100)	This actually an array of Prompts for the parameters that were logged
SSTD.OLD_VALUE	Display Field	Varchar(1000)	This actually an array of Old Values for the parameters that were logged
SSTD.NEW_VALUE	Display Field	Varchar(1000)	This actually an array of New Values for the parameters that were logged
DECODE(SSTD.NEW_VALUE,SSTD.OLD_VALUE,’Y’,’N’)	Hidden Field	Varchar(1)	This field is intended to tell us if the logged value has changed between the old and new value

Last Modified on 23 April, 2007 1:33 PM

History Information

Release Information	Project	Changes to Document
10.0.0.0.0.0	1225 - Connect Transaction Management	New Document