Colleague batch processes should be run in the process handler to free up user sessions for other activities. Executing batch processes in the process handler allows administrators to capture more detailed information about what processes are executing in Colleague to assist in troubleshooting performance issues. If the results of a process (e.g. a report) need to be obtained, those results can be emailed to the operator by changing the peripheral configuration settings for the output device to email. The output can also be sent to a hold directory. Their are several options for sending output to a hold directory.
Public allows the output to be sent to the public _HOLD_ directory where anyone can access the output.
Private will send the output to a private hold directory named in the following format: HOLD.PRIVATE.<operator id>. These files can be downloaded using FLDL.
Shared will send the output to a shared directory that can be configured so that a department can share access to output files. These shared folders would need to be configured prior to executing the process.
On the peripheral configuration screen, the Banner field can be used to name the file that is save to the hold directory. This is useful if files are sent to a shared location so that operators' individual output can be more easily identified. The recommended format for the Banner field would be <mnemonic>_<operator id>_<datestamp>. An example would be BILL_WIT0217684_2025_06_19. The screenshot below indicates where the Banner and Security options for output can be configured on the peripheral device screen.
A process is scheduled in the background by entering Yes in the field Execute in Background mode. Next select E-Envision Process Handler for the Execution Type. The default once those options have been selected is to execute the process in the process handler one time.
