Operational Manual for Logging Incidents
The Incident Logging functionality will
allow the user to send a standardized incident report to designated
staff members by email.
The incident report will automnatically include the data below as contextual information
- The data used when the incident occurred
- Institution Code and Name
- User
Name
-
Operating_system
-
Session
ID
- System Instance (Production, Test, etc)
- Program Name
- Version
- Executable program
- Source program
- Menu Option and Description
- Forms
Version
- Forms
Error (If a Forms Error was raised)
The system allows different Email Groups to be assigned to receive Incident Reports for different Subsystems
Setup:
- Define the Email Group(s) {GCS2-22} to receive the Incident Reports
- Link the Email Group(s) to the relevant Subsystems {GCS2-24}
- Link Staff Members to Email Groups {GCS2-23}.
- Ensure that the IP address of the Email Server or the Server
DNS name the of the Email Server is entered in System
Operational Definition {GCS2-11} "ST - SMTP Server" for Subsystem "GC".
- Ensure that the Unattended Mailbox address that will be used
as "From" - email address is entered in the description-field
of the External Conversion {GOPS-21} where External Body is "WEB", the External Code Type is "UTL" and the Internal Code is "Mail"
Logging an Incident.
Below is an example on how a User Reports an Incident
1. The Indicent Occur
2. Go to Help -> Logging
Incidents.
3. The Basic Incident Report is Displayed
4. The User may attach a file to the Incident Report as supporting documentation.
5. The User may upload multiple files.
Example:
click on the envelope and the following appears illustrating
that the mail has been sent
History Of Changes
Date |
System Version |
By Whom |
Job |
Description |
26-Jan-2007 |
v01.0.0.0 |
Charlene van der Schyff |
t12345 |
New manual format. |
16-Aug-2012 |
v03.0.0.0 |
Frans Pelser |
f185125 |
Remove Request Logging and Tracking System |