ExtraView allows the System Administrator to define a process that conforms to the way the company works. It does not impose a fixed methodology on the company. The administrator can, without programming, set up rules appropriate to the company’s needs.
Each issue you submit can be moved between any number of status values that you define, with each status being visible only to the user role that is permitted to work on the individual status. For example, an Open issue may only be changed by the Engineering group, who may only mark it Fixed or Issue not found after working on it. This same Engineering group may not Close the issue since that is a state that only a different role such as Quality Control may access.
A user role is created for all people who should follow the same rules. Typically, these would fall along the lines of customers, support staff, engineering, quality assurance, managers, administrators, etc., but complete flexibility exists to define what user roles you create and how many you create.
In addition, you can program a significant amount of logic into each Add or Edit screen form within ExtraView. For example, you can set some fields to only display dependent on the contents of a specific field, or you can specify sub-layouts within the form that are conditional upon the value of a specific field.
Should you have a workflow process that cannot be accommodated within ExtraView’s standard functionality, the product can be extended with additional code written in the Java language and inserted into a “user exit” routine using ExtraView’s UserCustom Class. ExtraView was designed to make it easy to alter or add functionality within the source code, but without needing to modify the source code of the base product. In this way, your investment is protected when you update or upgrade ExtraView.
