Download GECO User Guide.

GECO User Manual 1.E
Figure 133: Anomalies Form ready to introduce a new Anomaly by cloning an existing record
C. Fill in the new record.
In the Anomalies Form, the mandatory fields that must be filled in are the following ones:

Code. The Anomaly code is automatically generated by the application and can not
be modified.

Sub-subject. Indicate which subsystem (or group inside the organization) is
affected by the Anomaly. This is a text field and the maximum length of this field is
20 characters.

Initiator. Identify the person that is creating the Anomaly. In the combo box, all
persons in the organization that have been previously introduced as Users in the
application (see section 14) can be selected.

Starting date. Indicate the date when the Anomaly is being created. This is a date
field with the following format: dd-mm-yyyy, where dd: day, mm: month and
yyyy: year.

Anomaly date. Indicate the date when the Anomaly has occurred. This is a date
field with the following format: dd-mm-yyyy, where dd: day, mm: month and
yyyy: year.

Severity combo box. Select the Anomaly severity (i.e., the effect level that the
occurrence of the anomaly has had in the system) that among the options offered in
the Severity combo box, which includes the following ones:
o
High
o
Medium
125