Reports produced by the Process Server print to the server's default printer or to a specific printer:
Printing to the server's default printer. When a process is submitted to the queue either by using the Submit Process to Queue screen or by selecting the Submit to Queue function under Options in the menu bar in a Costpoint function, you have the option of linking the process to a specific Printer ID. If you do not tie the process to a Printer ID, it will be printed to the default printer of the Process Server
Printing to a specific printer. To link a process to a specific printer, enter the Printer ID when you submit the job to the queue. Printer IDs are established in the Maintain Printer IDs screen. When you log in to the Process Server, you indicate which printers are tied to the various Printer IDs. Only currently attached printers for the user logging into the server will be available.
In the System Settings screen in Costpoint System Administration, you can indicate whether or not you wish to save the process history. In the same screen you can also indicate whether or not you want to print a history report after each process is executed on the server. If you chose to print the history report after each process, it will be directed to the same printer as the process.
The Process History Report lists the start time, the end time, and the date of the process and each function in the process. If a function fails for some reason, appropriate error messages are also printed. Reports should be reviewed to make sure that the process completes without errors because remedial action needs to be taken if any process fails.
If you save the history in the System Settings screen, you can use the Print/Purge Process History screen to print the history of a process any time after the process is run. You can use the same screen to purge process history. Because the process history is stored in your database, you should purge this information often.
Remember that more than one server can service a queue. If you expect a lot of queue entries at one time, or if a lot of queue entries are submitted to start at the same time at night, you can start up as many servers as you want to execute all the queue entries in a timely manner. However, remember that each additional server puts more workload on your database server. Make sure your database server can handle the workload. The normal mode of operation is to leave all queues and servers active. However, you can temporarily logout of a server at any time.
By entering a shutdown time and reconnect time when you log in to the Process Server, you can stop the server's database polling for an interval of time. The database polling could interfere with sensitive database operations. The shutdown and reconnect time help you to reduce the number of times you need to logout of the server.
The Process Server can be used in a single-user environment. At first glance, it may appear that the Process Server is meant for multi-user environments, but Costpoint users who have single-user environments can take advantage of many the features of the Process Server. This can be done whether the environment is on a network with a Core license limit of one user, or on a stand-alone Windows workstation with Windows, the database, and the Costpoint software installed on the hard disk of the workstation.
To run the Process Server in a single-user environment, do the following:
Create a queue. You can create as many queues as you want, but you must create at least one. If you are starting to use the Process Server for the first time, just create one to get a feel for how it works.
During the day, submit queue entries. They can be set to execute immediately, because no server is currently running, or they can be set to execute at a later time (such as midnight). You can submit entries either from Costpoint Process Management, or with the Submit to Queue option, or both.
At a time when there is no need for interactive Costpoint work (such as data entry), exit from Costpoint as a normal user and start the Process Server on the workstation. At the profile screen, enter the name of a queue that has entries that have been submitted and are waiting to execute. The Process Server will start to execute the entries.
Shut down the server when it is finished. When the server finishes executing an entry, or when it has no more entries to execute, the Costpoint Process Server status screen will appear. Select the Stop pushbutton to shut down the server.
Resume regular usage. After shutting down the server, you can log into Costpoint and resume interactive usage.
You can use the Process Server most efficiently if you use Costpoint interactively during the day and submit entries to the queue to be executed at night. At the end of the day, start the Process Server to execute queue entries during the night. The next morning, shut down the server and resume interactive usage.