I have seen a few older entries on this community where people were requesting the ability to change the default error messages on a release station terminal. Was something like this ever implemented? If not, can this be considered as a new feature request?
I would like the ability to customize the default error messages on release terminals to make them a little less technical and a little more informative for our users. I would also like to include the contact info for our Help Desk on the errors - I don't really want our customers attempting to reach out to Pharos Support to notify them that one of our printers is jammed and cannot print, I would like to give them our contact info instead.
For example, if the printer fails an online state check, the current error is:
An internal server error occurred. No suitable printer available: Printer is reporting an Offline state.
Please contact Pharos support.
I would like to change it to something like:
This printer is offline and cannot print right now. You were not charged for your printouts, and they can be released at another print station.
We have been notified of the error and will resolve it as soon as possible. Please contact the Technology Help Desk at 412-xxx-xxxx if you need additional assistance.
While it's true that not all messages are customizable, but there are two placed you can look to see if the messages you see are configurable. First, in the Pharos Administrator tool, under Settings\Prompts, there are some messages there that are configurable. Second, as Steven English mentioned, if you have any custom scripts in place, they may be the source of the messages, and are configurable there. Otherwise, yes there are some messages that are not configurable. As others have mentioned, some of them are tell-tale signs of specific problems and help support personnel pinpoint the problem.
However, I will take your suggestion that we revisit the messages that we have, and try to make more of them configurable in the future. It is a valid point that user-facing messages should not be directing users to Pharos Support. We will review in the future versions of the product. Thank you for bringing this to the Community.
-Jeff Herald - Pharos Systems