| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
For more information about these modules see:
...
Use SLA times: Enable this option to register the response and handle times desired per priority and be able to report on the response and handle times for all requests.
Hide option to send request to contractor: Hide the option to forward the request to a contractor instead of working with corrective work orders. Forwarding requests to a contractor can be used if the customer does not use corrective work orders for this purpose.
Auto close request after workdays: After a request is handled, the requestor can check if the request is handled accordingly. If the requestor does not review the request, the request is automatically closed after X days.
Set update done by requestor flag: Enable this option if the requests need to be flagged as soon as the requestor adds more information to the request. The service group that handles the request becomes aware of the additional information and can then mark the request to confirm that the requestor's update is seen.
Use preferred suppliers: Enable this option to register preferred suppliers in general, per building, per area, and/or per asset, and let the application automatically assign the preferred supplier to the corrective work orders.
Use Knowledge base: Enable this option to use a knowledge base in requests, where users can add knowledge base items to help other users handle requests faster and more efficiently.
Check duplicate problem type: Enable this option to let the application check for duplicate (open) requests with the same problem type.
Check duplicate propertybuilding: Enable this option to let the application check for duplicate (open) requests with the same property/ building.
Check duplicate area: Enable this option to let the application check for duplicate (open) requests with the same area.
Check duplicate asset: Enable this option to let the application check for duplicate (open) requests with the same asset.
...
The emails that are automatically sent via the workflow (e.g., the confirmation email to the requestor after the new request is submitted) are also generated and shown in the include on the module activation after the module activation is started. If the customer does not want to use one or more workflow emails, the emails can directly be deleted from the overview. For more information on workflow emails: Standard Workflow emails
For a detailed description of the emails sent via the workflow, see: Requests module in the 'Application Managers' section.
...
For some modules, other (master data) modules might be of importance, in order to be able to fully use this module.
For Requests, the Master data modules ‘Properties ‘Buildings and areas’ and ‘Assets' are often relevant therefore the following system groups could also need to be assigned to users (If not already done in the past), to be able to create and edit the relevant master data objects.
Reference | Name | Description | License needed |
|---|---|---|---|
GOB-G007 | Edit properties buildings and areas | Group gives create and edit rights on properties buildings and areas | Full user |
GOB-G008 | Edit assets | Group gives create and edit rights on assets | Full user |
...
For the user manual with a more step-by-step explanation of the process itself, see: Requests module for (end)users
...