Deal+Slip+Printing

Deal Slip Printing The printing of deal slip reports is controlled via the following applications: BROWSER.PREFERENCES and VERSION. BROWSER.PREFERENCES The BROWSER.PREFERENCES application has a record for each of the users. To access the record, the user needs to select the ‘Amend preferences’ tool from the tools menu page. (See figure 70 – Selecting the BROWSER.PREFERENCES tool.

Figure 70 - Selecting the BROWSER.PREFERENCES tool BROWSER.PREFERENCES allows the user to specify the location of the deal slip printing. This can either be set to the server or to a local printer. See figure 71 – Setting the deal slip printing location. The ‘printer location’ field has the following possible values: SERVER LOCAL

Figure 71 - Setting the deal slip printing location VERSION The actual report printed, and when the report is printed, is controlled via the application VERSION. VERSION has four fields of interest with regard to deal slip printing: D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER D.SLIP.STYLE.SHEET

See figure 73 – deal slip print in VERSION.

Figure 72 – VERSION Report

Figure 73 – Deal slip print in VERSION D.SLIP.FORMAT The value(s) defined here are used to produce Deal Slips according to the function and whether the user wants to have them produced automatically or when a 'hot key' is used. Deal slips can be printed to a connected local printer or directed to a Network device. Refer to the REPORT CONTROL section of the Systems Administration User Guide for details of setting up printers. Deal slips can be linked to a function such as Input, Reversal or Authorisation and specific Deal Slips can be made to relate to those functions. Either an ENQUIRY record or a DEAL.SLIP.FORMAT record can be entered. If a valid DEAL.SLIP.FORMAT then the system will provide enrichment from the record so the user will know they have the correct record. Alternatively, an ENQUIRY record can be used to provide a Deal Slip. In this case the enrichment will inform the user that an ENQUIRY record has been selected. The user may drilldown to the related table DEAL.SLIP.FORMAT to view or select the record to use. The combination of the associated fields is used to define when the Deal Slip can be produced. To trigger them automatically you need to define: Field D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER

Content Required TELLER.SLIP.INPUT I OL

This will only print the Deal Slip 'TELLER.SLIP.INPUT' when the deal is validated at I(nput) time.

To trigger them via a 'hot key' or the Browser Deal Slip icon you need Field D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER

Content Required TELLER.SLIP.INPUT I RQ

This will only print the Deal Slip 'TELLER.SLIP.INPUT' at I(nput) time when the 'hot key' is used. Validation Rules •

Input to this field must be a valid record in either ENQUIRY or DEAL.SLIP.FORMAT files.

•

Must have values in fields D.SLIP.FUNCTION and D.SLIP.TRIGGER to produce Deal Slips

D.SLIP.FUNCTION The Deal Slips can be produced at various times according to the function (or codeword FINISH) and whether they are produced automatically or in conjunction with a 'hot key'. This functionality only works when D.SLIP.TRIGGER is set to OL. If it is set to RQ then the ‘hot key’ will always be active on the deal, but will only produce a report when the function is set to I. This differs from Desktop in that Desktop will only print the deal when a certain function is in process – the function as selected below. FUNCTIONS Valid functions are: Data I A C R D H FINISH

Description Input Authorise Copy Reverse Delete History |Restore

Where FINISH is specified, this processing is dependent on the application and may not be triggered for all applications. Validation Rules •

Valid input is I, A, C, R, D, H or FINISH.

•

Must have input in fields D.SLIP.FORMAT and D.SLIP.TRIGGER fields to be effective.

D.SLIP.TRIGGER Specifies whether a Deal Slip is produced using a 'Hot Key' or at specified points in a contracts Life Cycle. Control of how and when the Deal Slip(s) are produced is handled by the combination of the function and the trigger type. The two trigger types are: Trigger type Action OL Generate a deal slip automatically at points defined by D.SLIP.FUNCTION Generate manually using a HOT.KEY at points defined by RQ D.SLIP.FUNCTION Hot Key In Browser the 'hot key' icon can be found on the main toolbar. Validation Rules •

Must be either OL or RQ.

•

Must have input in fields D.SLIP.FORMAT and D.SLIP.FUNCTION to be effective.

D.SLIP.STYLE.SHEET Specifies a custom style sheet to use when transforming the deal slip. This field is only used when the user is printing locally (BROWSER.PREFERENCES printer location set to “LOCAL”) and automatically (VERSION deal slip trigger set to “OL”). Validation Rules Must be a valid XSL style sheet “/transforms/custom/clientEnquiry.xsl”).

resident

on

the

web

server

(e.g.

DEAL.SLIP.PRINTING examples The following five examples detail how deal slip printing occurs in Browser: •

Automatic, Local printing

•

Automatic, Local printing, Custom stylesheet

•

Automatic, printing at server

•

Hot key, Local printing

•

Hot key, printing at the server.

Automatic, Local printing For Automatic, Local printing, the user would change the print location field in the users BROWSER.PREFERENCES record to LOCAL. The four critical fields in version are set as follows: Field D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER D.SLIP.STYLE.SHEET

Content Required TELLER.SLIP.INPUT I OL

On committing a deal with the function I, a deal slip will automatically be printed. This will display the report generated along with the user’s local print selection screen, which will enable the user to print the report to a local printer. See Figure 74, 75 and 76 – Automatic, Local printing.

Figure 74 - Automatic, Local printing – transaction complete screen

Figure 75 - Automatic, Local printing – deal slip report

Figure 76 - Automatic, Local printing – local print screen Automatic, Local printing, Custom Stylesheet For Automatic, Local printing, with a custom stylesheet the user would change the print location field in the users BROWSER.PREFERENCES record to LOCAL. The four critical fields in version are set as follows: Field D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER D.SLIP.STYLE.SHEET

Content Required TELLER.SLIP.INPUT I OL /transforms/custom/clientEnquiry.xsl

On committing a deal with the function I, a deal slip will automatically be printed. This will display the report generated as transformed using the custom stylesheet along with the user’s local print selection screen which will enable the user to print the report to a local printer. See Figure 77, 78 and 79 – Automatic, Local printing.

Figure 77 - Automatic, Local printing – transaction complete screen

Figure 78 - Automatic, Local printing – deal slip report

Figure 79 - Automatic, Local printing – local print screen Automatic, printing at server For Automatic, printing at server, the user would change the print location field in the users BROWSER.PREFERENCES record to SERVER. The VERSION record would stay the same. On submitting the deal, the deal slip will be printed automatically. The user will then receive a transaction complete message with the ID of the deal slip generated on the server. See Figure 80 - Automatic, printing at server

Figure 80 - Automatic, printing at server Hot key, local printing For Hot key, local printing, the user would change the print location field in the users BROWSER.PREFERENCES record to LOCAL. The four critical fields in version are set as follows: Field D.SLIP.FORMAT D.SLIP.FUNCTION D.SLIP.TRIGGER D.SLIP.STYLE.SHEET

Content Required TELLER.SLIP.INPUT I RQ

At present, hot key, local printing only works for the function I so set the field D.SLIP.FUNCTION to I. When the user clicks on the print deal slip icon (Hot key), a request is sent to the server. If the trigger is set to OL in the VERSION record, then this icon will be disabled.

Figure 81 – Hot Key, Local Printing When the trigger is set to RQ, then the deal slip print icon will be available at all times within this version record. When the deal slip print icon is selected, a request will be sent to the server to generate a report. The function passed down to the server is always I. The report will then be returned along with a print screen for printing to the local printer. See figures 78 and 79 - Automatic, Local printing. This will be similar for Hot keys. Hot key, printing at server For Hot key, printing at server, the user would change the print location field in the users BROWSER.PREFERENCES record to SERVER. The VERSION record would stay the same as above. At present, hot key, printing at the server only works for the function I – so set the field D.SLIP.FUNCTION to I. On clicking the deal slip-printing icon, a request will be sent to the server to generate a report. A confirmation of the report generation will then be sent back to the user and displayed in a new window. See figure 82 - Hot key, printing at server.

Figure 82 - Hot key, printing at server Custom Printing Custom Printing takes advantage of the custom style sheet and custom java script functionality. The custom style sheet functionality enables the user to specify the name of a style sheet to use to transform the XML response from the server. The name of the style sheet is set up in the java script document custom.js. Custom.js enables the user to write their own java script functions. These functions can then be linked to buttons via the application BROWSER.TOOLS, which in turn can be added to a BROWSER.TOOLBAR record. CUSTOM STYLE SHEETS The client has the ability to design their own custom style sheets. These will be used to transform specific resultant XML documents. Proprietary style sheets should be placed in the following XSL directory on the web server: •

transforms/custom/test.xsl

The reference to this style sheet would then be set in the java script document, custom.js.