Below is a listing of the options available along with a brief description of each.
For additional information on these options, please refer to our Tutorial Movies or click on the individual option names.
Option Name |
Function |
This option determines how often your work request numbers are reset. You can choose to reset your numbers each Month, Year, Day, or Never. |
|
This option allows you to enter the numerical value to which your work request numbers will be reset. The default starting number is 1. This is only applied when the work order numbers are reset based on the interval defined in the previous option. Note: We do not recommend using any number greater than 1. |
|
This "Yes" or "No" option deals with the interaction between the Customer module and WO Request module. If "Yes" is selected, this option will automatically carry over customer contact and address data to the WO Request Customer tab. The system will search for data that matches the phone number entered and fill out the remaining customer data fields in the WO Request module. This helps speed data entry. If "No" is selected, several functions are affected. First, the request will no longer pull in any previous requests on that same phone number. Second, this turns off the list of open requests for a particular phone number when adding a new request. Finally, the ability to pull customer data from the customer module will be turned off as well. Note: If "No" is selected, you can still search for customers based on phone number by using F8 in the phone number field. The F8 key only works in the first phone number field on the first tab of the WO Request module. It is not used for the phone number fields at the bottom of the screen. |
|
This "Yes" or "No" option deals with the interaction between the Customer module and WO Request module. If "Yes" is selected, this option will automatically carry over customer data to the WO Request Customer tab. The system will search for data that matches the contact information entered and fill out the remaining customer data fields in the WO Request module. This helps speed data entry. If "No" is selected, the request will not pull in any previous requests on that same contact information. Note: If "No" is selected, you can still search for customers based on contact information using the F8 key. |
|
This "Yes" or "No" option deals with the interaction between the Customer module and WO Request module. If "Yes" is selected, this option will carry over customer contact data to the WO Request Customer tab. The system will search for data that matches the account number entered and fill out the remaining customer data fields in the WO Request module. This helps speed data entry. If "No" is selected, the request will not pull in any previous requests on that same account number. Note: If "No" is selected, you can still search for customers based on account information using the F8 key. |
|
This is a "Yes" or "No" option. When this option is selected and a new WO Request is created, the system will prompt you to update the customer database if the customer data entered does not match existing records. If you select "Yes", the system will automatically update the Customer database with the new information entered in the request form. This option does not apply if the Eden Customer Database Integration option is turned on. |
|
Look for Requests by Request Phone Only |
This is a "Yes" or "No" option. If selected, this option will search for duplicate requests using only the request phone number. This option helps prevent duplicate prompts during data entry. |
Search for Customers by Parcel Number |
This "Yes" or "No" option deals with the interaction between the Customer module and WO Request module. If "Yes" is selected, this option will carry over customer contact data to the WO Request Customer tab. The system will search for data that matches the parcel number entered and fill out the remaining customer data fields in the WO Request module. This helps speed data entry. If "No" is selected, the request will not pull in any previous requests on that same parcel number. Note: If "No" is selected, you can still search for customers based on parcel number using the F8 key. |
Auto Update Request Status when WO Complete |
This is a "Yes" or "No" option. When selected it will automatically update status in the WO Request module when all work orders associated with the request are completed. This option will also update the "on hold" and "canceled" statuses in work order requests if all work orders associated with the request have these statuses. |
This is a "Yes" or "No" option that helps track duplicate requests. For example, if fifteen people call to report the same pothole problem, you can use this option to help consolidate the records. This particular option tracks duplicate requests using category codes. By using the F3 key, you can see a list of potential duplicates and determine if they deal with the same problem. If so, you can select a record and your duplicate request will be merged into the previous record. Your caller's information will be logged in the Requesters tab and the duplicate request will be eliminated. Thus, you will have only one record per problem with multiple individuals listed as requesters. For additional information on the F3 function, please see the Work Requests help guide. |
|
This is a "Yes" or "No" option that helps track duplicate requests. For example, if fifteen people call to report the same pothole problem, you can use this option to help consolidate the records. This particular option tracks duplicate requests using address blocks. By using the F3 key, you can see a list of potential duplicates and determine if they deal with the same problem. If so, you can select a record and your duplicate request will be merged into the previous record. Your caller's information will be logged in the Requesters tab and the duplicate request will be eliminated. Thus, you will have only one record per problem with multiple individuals listed as requesters. For additional information on the F3 function, please see the Work Requests help guide. |
|
This option allows you to set a numerical value indicating the address block range. This option works in conjunction with the Find Duplicate Request by Address Block option. |
|
This is a "Yes" or "No" option that helps track duplicate requests. For example, if fifteen people call to report the same pothole problem, you can use this option to help consolidate the records. This particular option tracks duplicate requests using a date range. By using the F3 key, you can see a list of potential duplicates and determine if they deal with the same problem. If so, you can select a record and your duplicate request will be merged into the previous record. Your caller's information will be logged in the Requesters tab and the duplicate request will be eliminated. Thus, you will have only one record per problem with multiple individuals listed as requesters. For additional information on the F3 function, please see the Work Requests help guide. |
|
This option allows you to set a numerical value indicating the date range. This option works in conjunction with the Find Duplicate Request by Date Range option. |
|
Disable Street Validation for Citizen Requests |
This "Yes" or "No" option allows you to configure the Citizen Web Requests in the Web application to accept Street Locations that are not in the Street Name List. This option will be turned off by default. Note: If a Work Order is created from a Request with an unvalidated street, the address will be moved to the General Location field of the Work Order. |
Automatically fill Home Phone# from Phone# |
If this option is set to true, the data from the Phone Number field will be carried over to the Home Phone Number field. |
Automatically Assign Meter # on Create WO |
If this option is set to true and the request is a meter install request, the request module will search the meter location inventory module and find the correct meter to attach to the request before the work order is created. |
Prevent WO Creation on Meter Installs if Meter # not present |
If this option is set to true and the meter location number is not specified, the request module WILL allow a work order to be created. |
Meter Install Problem Code |
This is necessary for the requests module to know which requests are meter install requests. |
Automatically Create a meter Location for Meter Install if one does not exist |
This option works in conjunction with the "Automatically assign Meter # on create WO." If a meter is not found in the meter location module for the request location address, the system will create a new meter location using the request location address. |
Prefix For New Meter Numbers |
If this option is populate, the specified prefix will be placed before the record autonumber when a new meter location record is created. |
Use Combined Contact Address |
|
Always Refresh Request after Creating a Work Order |
This automatically refreshes the Request record after a work order is created from a request. This forces the request to display the work order on the Tracking Tab. |
Special F7 Lookup Functionality |
When this option is turned on and users use the F7 button in the Location Address field will open up a tool to search for requests with the same address based on a set of criteria. When this is turned off it will just search for all requests at the given addres. |
Automatically Search for Existing Request |
If the Special F7 Lookup Functionality is set to Y turning this on causes the functionality to happen without clicking F7. |
Require Building Number for Updating or Adding Customer Address |
When this option is turned on any new request that would create a new record in the Customer Address module will only create the customer address record if the building number part of the Address field is filled out. |
Disable Request overdue notifications |
This stops all request overdue notifications from being sent out. |
Use Category Level Security |
This option allows administrators to control what types of requests each employee can see and edit based on work category. Requests that do not have a defined Category are editable by all users. Example: Sewer employees need full access to sewer records, but do not need full access to water records. In the Employee module and admin can setup the Category Level Security for the user. The admin can specify which security level each user has access to (Add/Edit/Delete, Edit Only, View Only, etc.) for each work category. within specific work classifications (categories). Note: Each employee will need a Login ID defined in the Employee Setup module if security is turned on. Note: For additional information on how this security setting works, consult the Category Level Security topic in the Work Flow Setup, Employee module. |