Advice of an error in the client interface

So, what happens when an error occurs in RefTracker?

Should an application error occur in the RefTracker client interface, the client is simply advised that an error occurred (see example screen print above).  The contact details shown in this screen are controlled by Parameter 1.10-2, and the layout of this and a number of related error messages are controlled by Error templates editable using System>Utilities>Administration utilities>Template editor (text).

The text files controlling information displayed about errors in the client interface, that are editable using the Template editor (text) screen, have indicative names like:
clientProcessingProblem.htm
clientUnexpectedError.htm
system404Error.htm
systemCriticalError.htm
systemUnavailable.htm

At the same time, information about the error is saved in the Error log file (see information about viewing this file in the Utilities section earlier in this manual), and an email is automatically sent to the email address/es in parameter 1.20 – usually the Altarama support email address for your region of the world, and sometimes, also your Active System Administrator.  The email provides enough information for Altarama to diagnose the issue and start working on any fix that might be required. 

This sort of issue can be created as a result of errors indicating that a new type of hacker activity has successfully been prevented from entering RefTracker.  Altarama has considerable hacker and spammer activity prevention built in, and we can use parameter 80.100, or add a captcha to any effected Request form, to stop further emails about any new type of activity, until Altarama can add new code to stop it without error indications, should this prove necessary.