Communication Worklist Job

This job processes the Hospital Communication Worklist. It evaluates each entry and attempts to send the message. If it errors out, the message for the error will appear in the logs on the Communication Worklist so it can be corrected there. If the job itself cannot run, errors are logged on the View Logs.

Settings

The Communication Worklist uses the standard API job settings. The Active Flag means it is available to start at any time. The select server is the one on which it will run. Auto Start indicates that the job will turn on with the server; otherwise it will start running when you click on the Start Job button.

Like all API jobs, VetView strongly recommends you run this API job on a server separate from your production systems. The Communication Worklist can become very processor intensive if there are a lot of discharges in a short span of time, and having it on a dedicated server can help prevent lag for the users.

Additional Settings

Messages to Print: The Communication Worklist can also send a copy of all communications to a second email address, to have a confirmation on what the client specifically received. These can also then be printed out as PDFs and mailed if needed.

View Logs

If a communication cannot send, an error will be logged on the Communication Worklist job. These errors must be resolved on the Communication Worklist itself, but by using the Filters to narrow down errors to specific dates, it can be used as a tool in the workflow for the communication worklist to ensure that all errors are caught and corrected.

Click on the row of an error to view additional details.

Start and Stop Interface

The Communication Worklist job can be started and stopped from the main Active Interfaces and Current Status board on the Job and Interface Setup screen.

If it is actively running, Stop Interface becomes available. If it is currently stopped, Start Interface is available.

VetView Wiki

Most recent releases of VetView: Version 5.0.4 (Released 3/10/2025) and 4.2.10 Hotfix (2/28/2025)

Contents

Browser not supported