| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Use SLA times: Enable this option to register the response and handle times desired per priority and being able to report on the reponse and handle times for all requests.
Hide option to send request to contractor: Hide the option to forwarded the request to a contractor instead of working with corrctive 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 needs to be flagged as soon as the requestor adds more information to the request. The service group which handles the request becomes aware of the additional information and can then mark the request to confirm that the requestors 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 handling requests faster and more efficient.
Check duplicate problem type: Enable this option to let the application check for duplicate (open) request with the same problem type.
Check duplicate property: Enable this option to let the application check for duplicate (open) request with the same property/building.
Check duplicate area: Enable this option to let the application check for duplicate (open) request with the same area.
Check duplicate asset: Enable this option to let the application check for duplicate (open) request with the same asset.
Service groups:
Create the desired service groups directly from the module activations ‘Servicedesk service groups’ include. At least one service Service groups:
Create the desired service groups directly from the module activation's ‘Servicedesk service groups’ include. At least one service group needs to be created to be able to start the module activation.
4.2.1 Workflow emails
...
The emails that are automatically send 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: Workflow emails
For a detailed description of the emails sent via the workflow, see: Corrective work orders in the 'Application Managers' section.
4.3 Data imports
When activating this module, some data imports become available, which can be used to quickly import relevant data into the system (as opposed to manually entering this data, which is also possible).
...
For the user manual with a more step-by-step explanation of the process itself, see: Requests module for (end)users
...
Waiting for questions to answer.
BELOW THE OLD TEXT:
To start the module activation for corrective workorders:
...