This is the form that opens when a Request is created or existing one opened.
.
The Request form is for users to record the details of a Request for work to be performed by the organisation. These can then be linked to the work actions that in turn are linked to Assets.
The Header section contains information about this particular Request Form.
Field |
Description |
Received Via |
How the Request is received (Email, Phone etc) |
Date |
Automatically input by System at time of creation. |
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 entity from the Organisational Hierarchy that this Request is assigned to. To ensure this system operates correctly you need to ensure that you Organisational Hierarchy’s are properly configured with Email address. |
The Details of Requestor Section contains the information about the Customer who made the Request. This is set up with the view of external Customers in mind but internal ones should be recorded here as well.
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 Customer making the Request. |
Account |
Free use text field 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 |
User definable List Field (See section on Code Editor) currently configured to record what type of person the Customer is (Resident, Councillor, Police, etc) |
The Details of Request Section records information about the actual request.
Field |
Description |
Location |
Where the problem is located. |
Action Response |
Drop list of Standard Actions that have the Request Response checkbox ticked |
Request |
A description of what the Request is about. |
Action Urgency |
User Definable Code List to record an indication of how urgent the problem is. |
Date Due |
Where you can record a specific date for which a Request should be done by. |
Request Category |
User definable List Field (See section on Code Editor) currently configured to record what type of Request (Emergency, Routine, Private) |
Customer Response |
Drop down list that can be configured to record a response given to the customer. |
Completion Date |
A date of completion of the Request can be manually entered here. |
Completed |
This box will check itself once all actions associated with this Request are completed. |
Once all appropriate fields have been entered select the Email Button to send an email to the person assigned to follow up the Request.
To examine the Actions related to a Request, select the Action Tab.