Intelligent error handling

The new InterAKT way of handling errors offers a more user friendly approach to what was so far a programmer's worst nightmare.

1. Errors are detected per form fields or generic per page.
   · You can either have general errors that apply to an entire form
   
   
   
   · Or specific error messages that are displayed on a certain field, inside the form to help you locate the error faster.
   
   
                                       
2. Customize errors
   · Use CSS design to customize your error messages. Give different colors and insert HTML tags to better display your messages for maximum effect.
3. Split between Development Mode and Production Mode. Detailed error handling in Development and simple, easy to understand errors in Production. The split will offer developers a choice for different error depth at different development moments.
   
   
                                             
4. Error logging – Create your own error log for the project. Choose between a file log or having the errors sent by e-mail to the address of your choice when in production.
   
   
                                         
5. Knowledge base for developer errors
   · InterAKT is maintaining a knowledge base for development errors in which instant help is offered through technical notes written by our support staff:
   
   
   
   · Once you get an error on page just press the Online Error Troubleshooter link and receive an advice regarding your error.
   
   
   
   Note: The Online Troubleshooting system does not work if you have pop-up blockers enabled in your browser. Please disable pop-blockers, then click the Refresh button to reload the page.
6. Local Server Configuration sent to the knowledge base
   · Once you press the Online Error Troubleshooter link your local server configuration is sent to the InterAKT Knowledge base. This will ensure that InterAKT specialists can duplicate your settings and try to get the same error, then propose a solution that molds perfectly into your structure.
   
   
                                  
7. tNG execution trace
   · For experienced developers, the error will present the exact execution trace and show the step where the trace has been broken. It will detail before and after triggers, any other elements of the transaction and specify where the problem occurred.