Providing high quality applications has always been one of the major targets for ClassiX®. Software development is generally not only upgrading functionality. Unfortunately bug fixing is always an important part, too.
The approach of an object-oriented architecture - the ClassiX® base - aims for quality and therefore for less problems, for example with program code reusability. (The bottom line of program code reusability is unfortunately, that also program errors can be "reused".)
ClassiX®' comprehensive quality assurance prevents system errors. But withal care and accuracy, problem reports or even program crash can still occur and interfere with your work in ClassiX®.
This explains the importance of our bug management, which is part of the ClassiX® Support Model.
Problem reports though, do not always indicate problems to be solved in ClassiX®. Here some recommendation:
First detect, WHAT has happened WHEN. To describe WHAT happened, it can be helpful to create a hard copy. WHEN can be documented by describing, what has been done just before.
WHAT can be a system problem report, or also an "unexpected" result from data processed by the system. In both cases, it is important to know the reason for this situation. So please always try to immediately describe the performed steps before the "problem" occurred.
This approach might help recognize that an activity has never been done before. A "new" entry chain in a system might not be known by the system, yet and therefore cannot be processed. Here it needs to be checked, if it has been the developers' intention to support the activity at all, or if this funcitonality is simply missing in the system.
A detailed problem documentation is the best condition to receive help as fast as possible.
Please try to repeat the process at least a second time. We know from experience, that it often "suddenly just works again"!
Without a constant error repeatability, it is difficult to find the problem cause and to fix it.
Every error is annoying. Yet it is not necessarily required to stop your work. Please try to continue your work with different entry steps.
Support staff always enjoys helping with a well documented and reproducible error, since it can be fixed quickly. Reporting a valid workaround is good for everyone, since it makes it possible to continue working with the system.