Add service records page

After assigning the ticket to the service engineer, this service engineer can either accept the ticket or reject it. If the service engineer accepts the ticket, he'll start serving the customer, and he'll have to open a service record to submit his result of his assigned ticket.

The result after serving the ticket could be either solved or not solved, if the ticket was not solved the service engineer will have to add a reason for that.

This page will contain the following:

1-Ticket number search field: The admin can search for the ticket using its number here.

2-The search button: this button will execute the searching for the ticket in the database.

3-Result list: the searching result will be displayed on this list, if there were no result then the ticket does not exist.

4-View ticket button: by pressing this button a new page will be displayed to view all the ticket information, these information will be not editable.

The ticket view page is displayed after the admin presses on the view ticket button in the open service record page, here the admin can view all the ticket information but they will not be editable.

This page will contain the following:

1. Ticket information form: this form will contain the full information of the assigned ticket.

1. Back button: by pressing this button you'll be returned to the add service record page.

5-Add service record: u00a0after pressing on this button a new page will be displayed to add a service record to the assigned ticket.

After pressing add service record button the next page will be displayed, where the admin needs to fill some information about the service record and the result of it.

This page will contain the followings:

1. Record number field: the record number is an auto incremental number that's auto filled from the database directly, it defines the number of service records made before, and it will not be editable.
2. Ticket number field: this field will be auto filled and cannot be edited, it will contain the ticket number chosen.
3. Record date: the record date is auto filled and it's usually taking from the current date, the admin can edit it depending on the date the service record was made on.
4. Time in field: is the time when the service engineer arrived to the customer to service them.
5. Time out field: is the time when the service engineer finishes and leaves the customer place after serving him.
6. Trip time field: is the time from assigning the ticket to the time of opening the service record.
7. Solution drop down menu: this menu will have two options, one of them is repair, and the other one is replace, these solutions are the actions which the service engineer made to fix the ticket.
8. Fault field: this filed contains the content which needs to be repaired or replaced.
9. Service location drop down list: this list will contain the type of service was provided in the record, if it was on site service, or a workshop service.
10. Engineer name drop down list: this menu will contain the service engineers whom this ticket are assigned to, the admin needs to select one of these service engineers to add the service record.
11. Actual fault drop down list: this list will contain the contents of the same sub product file, the admin can choose one of these contents to be the actual fault in case the fault was found in other content than the selected.
12. Actual fault serial drop down list: after choosing the actual fault, this list will be filled with the serial numbers for the content selected in the actual fault, the admin will have to choose one of these serail numbers to add the service record.
13. Overtime expenses field: this field registers the service cost in the overtime for this ticket.
14. Overtime hours field: this field registers the overtime hours spent during this record for this ticket.
15. Transportation expenses field: this field registers the transportation costs on the service engineers to get the ticket location.
16. Repair note field: this field will contain the repair note for the content.
17. Add record button: this button will add the service record with the previously entered information.
18. Back button: press it in order to return to the previous page.
19. Contents list: this list will appear when the solution for the service record is replace only, and the admin here will have to enter what content was replaced and other information.
20. Delete button: this button removes the entered contents from the list.
21. Add button: this button adds a new row of contents to the list, in case the replacement was for multiple contents and not only one.
22. Contents drop down list: this list will contain the contents for the same sub-product for the ticket, the admin selects what contents were replaced from the list.
23. New S/N drop down list: the admin selects the new content S/N from this list.
24. New version field: this field will contain the version of the new inserted content.
25. Old S/N field: the admin enters the old S/N of the replaced content here.
26. Old version field: this field will contain the old version of the replaced content.