Error Reporting (Desktop App)

The information in this section does not meet our standards and may be of poor quality. It is still under development.

This section of ContactsLaw provides an overview about Error reporting. In the ContactsLaw,

it is inevitable that from time to time problems will come up with the software. Either because there are some faults in the software or there are some things that need to be developed in the software.

With the help of reporting errors, the CPMS are very interested in knowing about those instances in order for them to develop a mechanism whereby and to take actions to fix the errors.

The below guide will be covering about error reporting in the ContactsLaw:

1. Getting Started

• Proceed to the Me tab and click on Tasks.

• Navigate to the ribbon group and proceed to Debug.

• Click a certain report that you want to check and try to fix.

2. Paths of Error Reporting

To debug and fix the reported errors, there are two paths:

• Path 1: Proceed to ribbon group and click on Test Client Error.

• An error window will appear on your screen.

• Note: There are two points in any report where things can go wrong. First, it may be because of the implementation of the desktop application, so that means that there is a fault in the desktop application, or some unforeseen path in the desktop application before we've even attempted to communicate with the ContactsLaw service. Second, maybe something has gone wrong locally on the client computer.
• If you click Yes, an Error Report Notepad will be shown on your screen. This will allow users and clients to describe what kind of error they encountered while using the application.
• Then, click Send.

• Path 2: Select an error report. Right click and choose Properties.

• Check the property details and click Save & Close.

• Proceed to ribbon group and click on Test API Error.

• A similar error window will appear on your screen. But this time, often the end user won't be able to distinguish between a problem with the desktop application or a problem with the server. It’s just the nature of the errors that change and the users are presented with the same two options and they can submit an error report.

• Similar to Path 1, if you click Yes, an Error Report Notepad will be shown on your screen. This will allow you to describe what kind of error you encountered while using the application. Then, click Send.
• Note: There will be times the user will be presented with the option to submit their report, and sometimes they won't. Specifically, in the situations where they won’t, it is feasible that the end user might contact the CPMS for support.