Supervisor Print Release

Transcription

1 Supervisor Print Release Installation, Configuration and User Guide

2 Supervisor Print Release 2014 Monitor Business Machines Ltd The software contains proprietary information of Monitor Business Machines Ltd. It is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. Information in this document is subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Monitor Business Machines Ltd. All rights reserved. No part of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the written permission of the publisher. While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document. Monitor Business Machines Ltd. Level 3, Grafton Road, Auckland, NEW ZEALAND Published: 3/04/2014 The Monitor Logo and Supervisor are registered trademarks of Monitor Business Machines Ltd. Any other products that are referred to in this document may be either trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks.

3 Contents Introduction 1 Installation 2 Print Release Server... 2 Requirements... 2 Installation Process... 2 Print Release Server... Wizard 7 SQL Server Location... 7 SQL Instance... 9 SQL Admin User SQL Database Application SQL User Confirm Settings Print Release Stations Requirements Installation Process Configuration Print Release Server Global Options Terminal Setup options General Tab Primary Tab Card Reader Tab Card Prefix Mapping Release Station Tab Print Release Stations Configuration UI Typical configuration w... orkflow 33 Define the setup record... to use 33 Associating Pull and... Print queues 34 Defining Pull (Input)... Queues 34 Defining Print (Output)... Queues 36 Determine the station's... mode of operation 36 Set an exit PIN Security Considerations Exiting the application Disabling special Window... s key presses 37 Automatic Login Running the application... automatically Bit Bit Workflow Examples 39 Authenticating before displaying jobs Logging in using Card/Primary... Number 39 Example in an unauthenticated... environment 40 Configuring the popup Responding to the... popup 41 Configuring the release... station 42 Release Station w... orkflow 43 Contents i

4 Logging in using Primary... ID 46 Logging in using netw... ork name and passw ord 46 Authenticating when releasing jobs Configuring the release... station 47 Release Station Workflow Choosing an output printer Secondary Support Using a coin box for payment Enabling Coin Box payment Print Release configuration Connecting the coin box Troubleshooting ii Contents 57

5 Introduction Supervisor Print Release has been designed to be fully featured, but easily upgraded and maintained. To achieve this, the release station product is comprised of two separate components: 1. Print Release Server - The web-based Silverlight application. This component is the release station application. It is what you actually see and interact with on the workstation. This component is installed onto the same server as Supervisor Net. Being a web based application makes upgrades on the site simple. Regardless of how many print release workstations are on the site, a one-time upgrade on the server is all that is necessary to upgrade the version of release station running on all of the site's release stations. 2. Print Release Station - The component that is installed on each of the print release workstations. As the main server component is a web-based application, a native application 'wrapper' is required to run on the workstations. This enables the release station to interact with computer peripherals such as card readers and also enforces the security of the application by running in full screen and not allowing the end user to get to the workstation's operating system. Upgrades to this component will not usually be necessary as the main release station application is actually located on the server. Introduction 1

6 Installation A typical installation will consist of: 1. Install the print release server component 2. Configure the SPR SETUP terminal setup record 3. Install the print release station component 4. Configure the print release station component When a release station connects to Supervisor Net for the first time, it will automatically be set to use the default SPR SETUP terminal setup record. If you want this new station to be configured differently that the other stations already associated with this record, copy SPR SETUP to a new record, make the changes as required and then associate the release station with the new setup record. The changes will take effect the next time the release station is started. Ideally you would have created this different setup record before installing the release station software. If you have done this, the new setup record can be chosen in the release station configuration interface. If you add or remove pull queues from the Print Release Station's terminal record, you do not have to re-start the release station for the changes to take effect. Print Release Server Requirements IIS 6.0 or above (Windows 2003 Server).NET 4.0 Silverlight 4 If these required components (Except for IIS) are not found during the installation procedure, they will be downloaded from the Microsoft website and installed automatically. If IIS is not installed, the installation process will end and you will have to install IIS before proceeding. Installation Process Run the file Print Release Server Setup.exe on the same server as Supervisor Net. The installer will follow the normal installer procedures of allowing you to alter the default installation location, and then proceed to install the product. Once the product in installed, follow the instructions in the configuration section of this manual. 2 Installation

7 During the installation process, you can choose to install the files to a different location or select next for the recommended location. Installation 3

8 Select the location within the Start Menu folder. Click next to continue. Tick the following additional tasks to allow the wizard to automatically configure Firewall settings, Server and SQL Connection settings. It is recommended that Configure Windows Firewall and Configure SQL Connection both be ticked. 4 Installation

9 By ticking Configure Windows Firewall, the wizard will automatically create the firewall security of Inbound and Outbound rules for window firewall with the Print Release software. Installation 5

10 Confirmation of all the location selections will be displayed. Click Install to proceed with the install or Back to change any selection. 6 Installation

11 Print Release Server Wizard The Print Release configuration wizard walks you the SQL admin user set up and database connection. SQL Server Location Choose the server that SQL Server is installed on. Note that for this to work, the firewall on the SQL Server must be configured correctly, the SQL browser service should be running, and SQL Server configured to allow incoming connections. This Server SQL Server is on the same server as the Web Print Server component. Installation 7

12 On another sever in the same domain If this option is chosen, connection to SQL Server via Trusted Authentication as well as SQL Authentication will be possible. On another server in a different domain If this option is chosen, only connection to SQL Server SQL Authentication will be possible. 8 Installation

13 SQL Instance The wizard will automatically populate the name of the Server into the field if the same server was selected earlier. If SQL Server is on another server, select the correct server from the drop down box. If for some reason your server and instance is not detected, type the value in manually. Installation 9

14 Click Next to continue. SQL Admin User You will then be prompted to choose an account to perform maintenance. This account will be used by the wizard to connect to SQL server and perform any updates necessary, such as creation of accounts and adding the correct permissions to those accounts. This is not the account used by the application during normal operation. That account is chosen later on. Trusted Authentication - The account currently logged into the PC will be used to connect to SQL Server. If this option is used, you have to ensure that your current login has 'DB Owner' rights to the SupervisorNet database. This option will appear grayed out if you selected On another server in a different domain in the SQL Server Location step earlier on. 10 Installation

15 SQL Username/ Password - This allows you to use an existing SQL account Username and Password for maintenance access. This account must have 'DB Owner' rights to the SupervisorNet database. The wizard will then validate the credentials before proceeding. Installation 11

16 SQL Database Select the desired database from the drop down menu. Then click Next to continue. Application SQL User This is the account that will be used by the application during normal operation. As this is a web application, the account used will be determined by the configuration of the application in IIS. The wizard will by default use the IIS APPPOOL account for the application pool. Trusted Authentication - Will automatically configure SQL Server to grant access to the IIS APPOOL\Supervisor AppPool Net4 account (If installed on the same server as SQL Server), or the domain\machine$ account if SQL is on a separate server in the same domain. This option will appear grayed out if you selected On another server in a different domain in the SQL Server Location step earlier on. 12 Installation

17 SQL Username/ Password - This allows you to enter a SQL account Username and Password. If the account does not already exist, the wizard will give you the option of creating it. Installation 13

18 When prompted re-enter the new SQL user password then click OK. The wizard will automatically create this user account in SQL with the correct permissions. Confirm Settings At the completion of the wizard steps a confirmation will be displayed showing the Server, Database and User that Print Release will connect to SQL. Example of Trusted Authentication Example of SQL Username/ Password 14 Installation

19 If correct, click on Finish. If you wish to modify any of the details click Back. Print Release Stations Requirements Windows XP (or newer) operating system.net 4.0 Silverlight 4 Screen resolution of at least 1280x1024 Installation Process Run the file Print Release Station Setup.exe on the release station workstation. The installer will follow the normal installer procedures of allowing you to alter the default installation location, and then proceed to install the product. Once the product in installed, follow the instructions in the configuration section of this manual. Installation 15

20 During the installation process, you can choose to install the files to a different location or select next for the recommended location. 16 Installation

21 Select the location within the Start Menu folder. Click next to continue. It is recommended that Configure Windows Firewall be ticked to allow the wizard to automatically configure Firewall settings. Installation 17

22 Confirmation of all the location selections will be displayed. Click Install to proceed with the install or Back to change any selection. 18 Installation

23 Installation 19

24 Configuration The configuration parameters for the application are held in four different areas: Options Component Globally defined options, not restricted All to individual release stations IIS Application Configuration Options relevant (or common) to groups of release stations Print release server Terminal setup records, accessed using Supervisor Administrator Options specific to individual workstations, such as interface information Print release station Print Release Station configuration UI - located on each of the print release stations Input queues and output queues Print release specific to individual release stations station 20 Location Configuration Print Release Station Terminal Record

25 Print Release Server Global Options To access the global options, open up the Internet Information Services Manager console on the Supervisor Net server. The options are: Name BackgroundImage Default Value Description Path and filename of image to use for the background of the application. This image replaces the default background. The image will be re-sized, but a resolution of 1280 x 1024 is recommended for best quality. The path specified must be relative to the website location, i.e. images/background.png or website/background.png. A filename relative to the server won t work e.g. c:\mbm\image.png - as the running web pages won t have access to this file. Configuration 21

26 Pay attention to the application's font locations and colours, as these are currently not configurable ClientValidationEnabled true Reserved setting - do not alter SupervisorPort The port used by the application to communicate with Supervisor Net. This should be left at the default value SupervisorServer localhost The server that is running Supervisor Net. This setting is reserved for future purposes, as a remote instance of Supervisor Net is not yet supported UnobtrusiveJavaScriptEnab true led Reserved setting - do not alter Terminal Setup options The majority of configuration items for the release stations are obtained from their associated terminal setup record in Supervisor Net. There is one default record called SPR SETUP supplied with Supervisor Net. A record is determined to be a print release station configuration record by it's Model (in the general tab) being set to Print Release Station. When the model is set to Print Release Station, only those tabs and options relevant to print release stations are displayed. Any terminal associated with this terminal setup record will use these configuration parameters. 22 Configuration

27 General Tab Option Description Type A unique identifier for the setup record. If you are creating a new record, this can be anything you like Description A description of the setup record for reporting purposes. Keeping this the same among different print release setup records enables you to sort and group by this field Model The model determines which options are shown in the setup record. For a print release station this should be set to Print Release Station Session Duration The period of inactivity before the release station will automatically return to the initial page. If a user was logged in, they will be logged out again after this period of time Configuration 23

28 Primary Tab 24 Option Description Hide Number Entry Any details entered into a primary validation dialog will be hidden with dots Configuration

29 Card Reader Tab Option Description Enable Keyboard Entry Enables the on-screen keyboard for primary validation in touchscreen mode. If the keyboard is disabled, it will still appear for other prompts such as PIN number entry and secondary validation Use Auto Suffix If set, this number will be appended to any card swipe at the release station. This enables the release station to always debit a particular account for prints. Used in a situation where a user may have multiple accounts for different purposes Enable PIN at Validation If the user has a PIN set on their account, they will be prompted for it at validation. If this option is disabled, the user will never be prompted for a PIN Start Character The release station will start reading the card number after detecting this start character. If this field is blank, the entire string is read from a card. For a keyboard emulation card reader, this character would normally be a semi-colon ( ; ) This character may at times be an equals sign ( = ). An equals sign on a track 2 magnetic stripe is designated as a field separator. Therefore a card number of = would mean that the second field (after the = sign) is the value End Character The release station will stop reading characters from a card swipe when this character is detected. If this field is left blank, the release station will read in all characters to the end of the card number string. For a keyboard emulation card reader, this character would normally be a question mark (? ) Get Username from Extracts the user's login name from the discretionary data field on a Track 1 Discretionary magnetic stripe's track 1. The user is then logged into the release Data station and only their jobs are shown Card Prefix Mapping Enables the detection of multiple card prefixes in order to apply differing card number lengths and offsets based upon those prefixes. Configuration 25

30 See the next topic for more information. 26 Configuration

31 Card Prefix Mapping The Card Prefix Mapping dialog enables you to alter the way that the card number is interpreted based upon the prefix of that card. An example of this would be: For a card number of , and defining the Prefix as : With an Offset of 7 and a Length of 6, the number read by the release station would be The Offset is always applied first, followed by the Length. The card prefix mapping control enables you to list several card prefixes and apply different criteria for each card matching that prefix. It also allows you to edit and delete existing configurations. The following example shows the control with three different card matches: Configuration 27

32 Release Station Tab Option Description Show jobs Determines when the list of print jobs is displayed to the user. The possible options are: After Primary Validation - The user must authenticate against Supervisor Net before any jobs will be displayed. The Supervisor Net field used for validation is specified in the next option (Validate By) Always - Jobs will always be displayed. As the user releases a print job, they will be prompted for credentials (As determined by the next option, Validate By) After Username / Password - The user must enter their network name and password. If this value is chosen, all jobs matching that network account will be displayed and a Supervisor Net validation prompt will be displayed when they go to release any jobs. This second validation step uses the next option to determine how the user will be authenticated against a Supervisor Net account After User Entered ID - The user enters the ID that they assigned using the print popup client when printing the job at the workstation. All jobs with this ID are displayed to the user and they are prompted for their Supervisor Net credentials when they release their selected jobs After Job Owner Entry - The user enters the print job owner. All jobs associated with that owner will then be displayed and they are prompted for their Supervisor Net credentials when they release their selected jobs Validate By Determines what credentials are going to be used to match the user to an account in Supervisor Net. The options are: Username / Password - The user must enter their network name and password. These credentials are then matched against the Primary ID field in Supervisor Net to find the user's account Primary Number - The number entered is matched against a Primary Number in Supervisor Net 28 Configuration

33 Primary ID - The number entered is matched against the Primary ID field in Supervisor Net. This option is typically used in an environment where casual user tickets are being used Group By Displays an initial list of items to the user to choose from before then displaying the list of jobs associated with that object. A common use for this is to Show Jobs - Always and then set this option to Work station. This will then display a list of all the workstations to the user in a public use environment, and they can then choose the workstation they printed from and see all jobs associated with that workstation. The options are: None - Don't display this grouping list Workstation - Show a list of workstations that the print jobs have been printed from Username - Show a list of the logged in usernames that generated the print jobs Printer - Display a list of printers that the jobs are being held against Allow User to Delete Jobs If this option is un-ticked, the Delete button will not be displayed in the release station, so users can't delete each other's jobs Show Only the User's Jobs When enabled, only jobs belonging to the logged in user will be displayed. This option is grayed out if Show Jobs is set to Always Show Jobs Processed by the Popup If the client application is being run on the workstations (to enter secondary codes or to pre-validate the user, etc), then only jobs where the popup has been responded to will appear in the release station Show Jobs Not Processed by the Popup If the client application is being run on the workstations (to enter secondary codes or to pre-validate the user, etc), then only jobs where the popup has not been responded to will appear in the release station Print Jobs Grid Columns A complete list of available columns for the main print jobs page in the release station. Columns can be hidden and re-ordered to maximise the ability to customise a site Logout After Release The option to automatically log a user out after releasing their print jobs. Release A complete list of available columns for the confirmation page in the release Confirmation Grid station (The page that displays the total amount of the selected jobs, and a Columns message asking whether the user would like to proceed). Columns can be hidden and re-ordered to maximise the ability to customise a site Configuration 29

34 Print Release Stations Configuration UI When the Test button is clicked, the connection between the release station and the server is tested, and further options become available: 30 Configuration

35 A configuration user interface is installed on each of the print release stations. It is found in the following location in the Windows Start menu: Option Description Server URL The IP / Host name of the server running the print release station server component. Normally, you only need to edit the IP or Host name of the server. The rest of the URL is pre-defined by the print release station server component's installation package Terminal ID The terminal ID of the release station, as automatically created in the Supervisor Net terminal database when the release station connects for the first time Name The name of the terminal. It can be altered through this UI, and the changes will be reflected in the terminal record in Supervisor Net Setup Type The setup record (Configuration parameters) that the release station will use. These should be created ahead of time Queues... Define the print queues that the release station will look for jobs in, and queues where the jobs will be moved to when they are released Run Defines the operation mode of the release station: Full Screen - The release station will 'lock' down the workstation and run in full screen mode. This is typical of a publicly used release station In a Window - The release station will run as a standard application in a window. Ideal if being used by a staff member, i.e. a teacher in a classroom. The application can be closed by clicking the X in the top right hand corner of the window Using Determines whether or not a touchscreen is being used as the interface to the Touchscre user. If it is, the buttons and lines on the grid are enlarged. If a mouse and en keyboard are being used, the data grid sizes are smaller so can fit more on each page Hide Mouse Cursor If a touchscreen is being used, it is sometimes preferable to turn the mouse cursor off Exit First If the application is running in full screen mode, it is exited by clicking in two Click different areas of the screen. i.e. if first click is top left, and second click is bottom right, the user must click once in the top left of the screen and once in the bottom right of the screen to display the PIN number entry dialog. Once the PIN has been entered, the application will exit. Exit Second Click Defines the second location on the screen that the operator must click to display the exit PIN screen Set Pin... Sets the exit PIN. The PIN must be entered after clicking the two different areas of the screen. If the PIN is left blank, the application will exit without prompting for a Configuration 31

36 PIN Enable Serial Reader Enables the connection of a serial card reader. Not to be confused with a keyboard emulation card reader which doesn't need configuring in this UI Port The COM port that the serial reader is connected to Baud Rate The BAUD rate of the serial card reader. See the reader's manual for details Parity The parity (even or odd) for the card reader. See the reader's manual for details Stop Bits The number of stop bits for the card reader. See the reader's manual for details Data Bits The number of data bits for the card reader. See the reader's manual for details Pay By 32 Selects the job payment method. The user can either pay using funds from a Supervisor Net account, or cash via a connected coin box. Only one payment method is possible per release station, therefore please refer to the section later in this manual if you are configuring coin box as the payment method to ensure that it is set up correctly. Configuration

37 Typical configuration workflow The release station has been designed to be installed and configured as quickly as possible, with the least possible steps. Define the setup record to use 1. After the release station software has been installed onto the workstation, open the release station configuration UI. 2. Click the Test button to connect the release station to the server for the first time. 3. At this point, a new terminal record is created in Supervisor Net's terminal database, and the ID of this terminal is now displayed in the area below: Configuration 33

38 4. Use the Setup Type drop-down box to choose the setup record to use for this release station. Only release station setup records will be displayed in this list: Associating Pull and Print queues Each release station must be configured to search for jobs belonging to the user in one or many different print queues. Defining Pull (Input) Queues 1. Click the Queues button: 2. Tick the boxes in the Pull Queue column corresponding to the desired print queue: 34 Configuration

39 The release station will now look in these queues for jobs belonging to the user. Configuration 35

40 Defining Print (Output) Queues Repeat the same process as defining Pull Queues, but this time for the Print Queues. If you do not define any print queues, the system will simply resume the jobs in the queues they were found when the user releases the job. If more than one print queue is defined, the user will be asked for which printer they would like to output the print job to when they release their job(s). This is useful in an environment where one print release station serves multiple printers in the same room: Determine the station's mode of operation Will the release station be running in a window on the user's workstation, or will it be running on a public use workstation, shared by many people? Is the workstation running a touchscreen? If it is, you will probably also want to hide the mouse cursor. Set an exit PIN Don't forget to set an Exit PIN. If this device is running in a public use environment, you don't want users accidentally or maliciously ending up outside the application and able to tamper with the operating system. Security Considerations Special consideration should be given to the security of the workstation if it is being operated in a public use environment. 36 Configuration

41 Exiting the application A PIN number should be set for exiting the application. See the topic in Configuration UI for more information on setting the PIN. Disabling special Windows key presses In a public use environment, the print release station will run full screen. It is recommended to run these stations with a touch screen, as it vastly limits what users can do to the PC. Attention should also be paid to disabling USB and keyboard ports on the PC, so that someone can't simply plug their own keyboard in. For situations where a keyboard and mouse are used, or for added protection on a touch screen system, it is recommended to disable the following 'special keypresses' using the local machine policy: CTRL-ESC ALT-TAB ALT-F4 CTRL-ALT-DEL Windows Button Automatic Login It is ideal for the release station PC to log in automatically if it is re-started for any reason (including power outages, etc). This is achieved in different ways depending on the operating system. As an example, here are the steps to achieve this on Windows 7: 1. Press the Windows key + R on your keyboard to launch the Run dialog box. 2. Type regedit and hit enter to open the Registry Editor 3. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\ 4. Set AutoAdminLogon = 1 (create a string variable if it doesn't exist) 5. Set DefaultUserName = your username (create a string variable if it doesn't exist) 6. Set DefaultPassword = your password (create a string variable if it doesn't exist) For the UserName and DefaultPassword, enter the credentials of the rights-limited account that the station will be logged in as. Running the application automatically If the workstation logs in automatically if restarted, you will want the release station application to start as soon as Windows logs in. This is achieved by adding a registry value. The registry value differs depending on whether the operating system is 32bit or 64 bit. 32 Bit 1. Press the Windows key + R on your keyboard to launch the Run dialog box. 2. Type regedit and hit enter to open the Registry Editor 3. Then browse to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run 4. Add a new string value called 'Supervisor Release Station' Configuration 37

42 5. Set the value of this string to "C:\Program Files(x86)\Monitor Business Machines\Print Release Station\ReleaseStationApp.exe" 64 Bit 1. Press the Windows key + R on your keyboard to launch the Run dialog box. 2. Type regedit and hit enter to open the Registry Editor 3. Then browse to HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run 4. Add a new string value called 'Supervisor Release Station' 5. Set the value of this string to "C:\Program Files(x86)\Monitor Business Machines\Print Release Station\ReleaseStationApp.exe" 38 Configuration

43 Workflow Examples Authenticating before displaying jobs This is the most common method of using a print release station. The user must log in before they see any jobs. Usually they then only see their own jobs, however this behaviour can be controlled by enabling or disabling the option Show only the User's Jobs, which is located in the Release Station tab of the terminal setup record: A common reason to disable this option is so that someone can release jobs on other's behalf - such as a teacher releasing jobs for students in a classroom. Logging in using Card/Primary Number The most common method of authenticating at a release station is by swiping a magnetic stripe or bar-coded card. These card numbers are stored in Supervisor Net's Primary Number field. If users are logging into their workstations using unique login names, the process is very straightforward. Their jobs are printed to the queue with their login name as the print job's owner. When they authenticate at the release station, only their jobs are listed. There are situations however when generic logins are used for public use PCs. In this situation you have the choice of: 1. Displaying all user's jobs at the release station and validating the user against the Supervisor Net database as they release a print job from the list. This method is easy but suffers from security and privacy limitations. Users can print or delete other user's jobs. 2. Pre-validating the user on the workstation so that the job ownership is changed to them. When they log into the release station, they only see their own jobs. This method requires more configuration and deployment, but is secure and private for the users. The following example demonstrates how to configure the environment for the second option. Workflow Examples 39

44 Example in an unauthenticated environment In this example, Supervisor Print Release is being used in a public library environment. Most public libraries have workstations that are logged in using a generic library login; therefore any job submitted to a print queue from this workstation will have the generic login as the print job's owner. As the job owner can no longer be used to differentiate between user's print jobs, another independent identifier must therefore be used. This example demonstrates how to configure the popup to allow the user to enter a unique identifier against their print jobs (via the print popup client) so that when they go to the release station, they can enter this unique identifier and see only the jobs they have printed. They will be prompted for their Supervisor Net credentials once they have selected their jobs and chosen to print them. Configuring the popup In the print client configuration, set the option Look Up Account to By User Entered ID. Choose an appropriate option from the section called Persist User Entered Data. This will determine how long the popup will remember their ID. The next time the popup triggers, they won't have to enter their ID again, if it has been persisted. This will have to be set according to how the public use PCs are used. If they are logged out each time a user is finished, the 40 Workflow Examples

45 option Until Logoff would be appropriate. If the PCs are constantly logged in, Never or For x minutes would be more appropriate. Responding to the popup When the user prints a job, the popup triggers and asks them to enter an ID for their job. This ID can be anything they want and is not associated with a record in Supervisor Net. It can be thought of as a password for their job. After entering their job Id, the user is then shown the confirmation page: Workflow Examples 41

46 When the user clicks OK, the job remains paused in the print queue with their ID recorded against it. Configuring the release station Configure the release station (in the station's associated Terminal Setup record) as demonstrated below: 42 Workflow Examples

47 In this configuration: 1. The user must enter their print job ID before they get to see any print jobs at the release station 2. They will be authenticating by swiping their library card (Primary Number) 3. Only jobs where they have have entered a job ID using the popup will be displayed Release Station workflow 1. The user enters their job ID (that they previously set at the print popup) at the release station. 2. The job is chosen from the list, and the user clicks Print. Note that only their job(s) are displayed. Workflow Examples 43

48 3. The user is asked for their Supervisor Net credentials 4. The user confirms that they want to proceed with the print job. 44 Workflow Examples

49 5. The user walks to the printer and collects their job. Workflow Examples 45

50 Logging in using Primary ID It is possible for the user to type in a value stored in the Primary ID field. This is most common when users are logging in using their network login credentials, but not validating against the network - the validation only occurs against the Supervisor Net user database. Under this circumstance, they will use either a keyboard attached to the workstation, or Touchscreen Mode will be enabled, and an on-screen keyboard will be made available for them to use: Logging in using network name and password It is possible for the user to log into the release station using their network login credentials. When they enter their name and password, these details are authenticated against the network. If the network replies that the credentials are correct, the username is then matched to a record in Supervisor Net by searching the Primary ID fields of the Supervisor Net database. If a user is found, they are logged into the release station. As with logging in by ID, a keyboard attached to the workstation may be used, or the application can be put into Touchscreen Mode and the on-screen keyboard used. To enable the on-screen keyboard in Touchscreen Mode, the option Enable Keyboard Entry in the Card Reader tab of the Terminal Setup Record must be ticked. Authenticating when releasing jobs In some public use environments it is not practical for the users to log into the release station before seeing the list of jobs. This is common in a situation where all users are logged into the workstations using generic login names and for whatever reasons, the popup application cannot be run on the workstations. 46 Workflow Examples

51 Configuring the release station In this configuration: 1. Jobs are always displayed to the user before they authenticate 2. Users are not allowed to delete jobs. It's annoying when users delete each others jobs, and tends to create administrative overhead. It's best to just automatically delete jobs from the queue every few hours 3. Jobs are displayed regardless of whether or not the user has responded to a popup. In this environment it's highly unlikely that they have 4. A good tip is to display the username in the grid, and log each of the public PCs in under a different username. This makes finding the jobs a lot easier for the user Workflow Examples 47

52 Release Station Workflow 1. The user chooses their job from the list displayed in the grid. In this example, each of the PCs are logged in using a unique generic login. The grid has been sorted by the Username field which contains the PC names. 48 Workflow Examples

53 2. A job is highlighted and the user clicks Print. The application will now prompt for the user's Supervisor Net credentials. In this example the user is swiping a barcoded card. Workflow Examples 49

54 3. The confirmation screen is then displayed. This sums up the total cost to the user so that they can decide whether or not to proceed. Note that their account balance is displayed in the background. Choosing an output printer If the release station is located in a room with several printers, it is possible to configure the release station to prompt the user for the desired output device as part of the workflow. To configure this, tick the printers that you want to appear as choices for the user to the Print Queues list in the release station's configuration UI: 50 Workflow Examples

55 You are also able to perform this step server-side in the release station's terminal record, in the Print Release tab. The user will now be asked for the desired output device before the confirmation screen is displayed: Workflow Examples 51

56 Note that the final price of the job is calculated based upon the Pricing Model associated with the chosen output device. The final price to the user may therefore differ depending upon which output device they select. Secondary Support If the release station is used in an environment where departmental (or some other) codes are used, it will automatically prompt the user for their code based upon the standard 'Prompt for Secondary' setting in their Primary Record. This is particularly useful in a school situation where the teachers are releasing the jobs (Which are printed as part of the curriculum) on behalf of the students and billing the costs back to a department. 1. The secondary prompt is displayed to the user after they choose the print job from the main screen and click Print 52 Workflow Examples

57 2. The user can then search for a code by Number, Name or Recently Used. Recently Used displays the user's last 6 used accounts. Workflow Examples 53

58 3. If the Search button is clicked without entering any partial search string, all codes that the user has access to will be displayed. The user then chooses a code from the list and clicks OK. Only those codes that the user has been granted access to (Using Supervisor Net's permit table functionality) will be displayed in this list. Using a coin box for payment It is possible to connect a coin box to the release station so that the users pay for their print jobs using cash, rather than using a Supervisor Net account. The currently supported coin box is the SEM 9900 or 9500 (or compatible) Coin Tower. 54 Workflow Examples

59 In this mode of operation, it is not possible to debit a Supervisor Net account, therefore the system has to be set up in such a way that Supervisor Net accounts are not referenced during the user's interaction with the product. Enabling Coin Box payment On the print release computer, open the Configure Print Release Station UI. Alter the setting Pay By to Coin Box. Set the Com Port and Baud Rate according to which port you have plugged the coin box into on the computer and what speed the coin box had been configured to communicate at. Print Release configuration The print release terminal setup needs to be configured in such a way that the user is not asked any questions relating to a Supervisor Net account, as payment by this method is not possible when the release station is configured to use a coin box. Workflow Examples 55

60 In Supervisor Administrator, open the terminal setup record called SPR SETUP. 1. Set the option Show Jobs to Always, After Job Owner Entry or After User Entered Job ID. None of these options make reference to a Supervisor Net account. (The options in Validate By are ignored when a coin box is fitted) 2. It is usual to ensure that both options under the heading For Popup Queues are enabled. This may however vary depending on your circumstance. 3. Turn off any grid columns that refer to Supervisor Net database fields. Connecting the coin box Using a standard serial interface cable, connect the coin tower to the computer. 56 Workflow Examples

61 Troubleshooting Diagnostic information can be found in the product's log files. If the information in the log files doesn't seem to shed light on the issue, they can be passed on to Monitor for further analysis. All log files are written to the server into the C:\mbm\ReleaseStation\logs folder. You will notice that each day a new date-stamped sub-folder is created, e.g will be the log files for 19th July There is one log written for the server application (Application.log) and one log per release station (ABxx.log). The name of the individual release station log matches a terminal record in the Supervisor Net terminal database. There are no logs written to the local release station computers. This makes it easy when collecting diagnostic information for several devices on a single site. Troubleshooting 57

62 Monitor Business Machines Wireless House, Grafton Road, Auckland, New Zealand. Phone: Web: