This is the form that opens when a Request is created or edited.
Here you record the details of a Request reported to your organisation, which on investigation, can be attached to one or more Works Actions that are in turn, linked to an Asset.
The Header section of the Request Form contains identification data about the Request.
|
Field |
Description |
|
Received Via |
A Picklist for how the Request is received (Email, Phone etc.) A Code Editor, System List, which you can modify the names of, to suit your organisation. See Codes for more details. |
|
Date |
Defaults to the date and time of the new Request Form opns. Can be changed. |
|
Received By |
Currently logged on user. |
|
Reference ID |
Unique Sequential number generated by Conquest. |
|
Document Reference |
Free use text field that could be used to record File numbers or something similar. |
|
Organisation Unit |
The Organisational Unit that this Request is assigned to and to which an email is sent, so ensure that your Organisational Hierarchy is properly configured with email addresses. |
|
|
|
Use the Details of Requestor section, for details about the Customer who made the Request, whether they are external or internal.
|
Field |
Description |
|
Request by, First Name and Last Name |
The Full name of the Requestor. Last Name must be input, as a minimum. |
|
Address, Suburb, Postcode |
The Street Address of the Customer making the Request. |
|
Account |
Free text field, which could be used to record a file number or account number of the customer making the request. |
|
Phone and Fax numbers |
Contact numbers of the Customer. |
|
Email Address |
The email contact details of the requestor. |
|
Requestor Type |
A Picklist to record what type of person the Customer is; Resident, Councilor, Police, etc. A Code Editor, System List, which you can modify the names of, to suit your organisation. See Codes for more details. |
|
|
|
Use the Details of Request Section, to record information about the actual Request.
|
Field |
Description |
|
Location |
Where the problem is located. |
|
Action Response |
A Picklist of Standard Actions that have been defined as Request Responses. A Code Editor, System List, which you can modify the names of, to suit your organisation. See Codes for more details. |
|
Request |
What the Request is about; often a problem with a service. |
|
Action Urgency |
A Picklist to record an indication of how urgent the problem is. A Code Editor, System List, which you can modify the names of, to suit your organisation. See Codes for more details. |
|
Date Due |
Where you can record a specific date for which this Request should be done by. |
|
Request Category |
A Picklist to record the type of Request (Emergency, Routine, Private). A Code Editor, System List, which you can modify the names of, to suit your organisation. See Codes for more details. |
|
Customer Response |
A Picklist list to record a response given to the customer. A Code Editor, System List, which you can modify the names of, to suit your organisation. See Codes for more details. |
|
Completion Date |
A date of completion for the Request will be set, when all the Actions related to it are Completed, or you can manually enter it. |
|
Completed |
This Checkbox is ticked, when all of the Actions related to the Request are Completed. |
|
|
|
When you have put all the details in and saved, click the Send Email Task to send the Request to the Organisational Unit assigned to it.
Use the Action Tab to see the Actions related to a Request. See Action Tab for details.