...
Automatic duplicate checks can be enabled, when a request is submitted. If, for instance, a problem occurred in the main hall, where all employees pass by, it could be that more than one user creates a request with the same problem type, same building and same area. For example, if If the service group receives 10 requests about the same issue, the first request is assigned to a service group responsible person. The other 9 requests are can be marked as a duplicate of the first request. The service group responsible now only has to follow up and handle the first request, instead of handling all 10 requests individually. After the first request is handled, the other duplicate automatically follow and are automatically handled.
...
The duplicate check is only executed for open requests. Already closed requests with the same problem type, the same building, and the same area, for example, are not taken into account.
Duplicate checks can be enabled via the ‘Module settings' → 'Requests’ tab.:
...
If a request is submitted, the system will automatically determine if there are any open requests that could be potential duplicates (based on the settings). If this is the case, the first task for the service group employee will be to determine if the request is indeed a duplicate (and if so, link it to the original request) or indicate that the request is not a duplicate and pick up the request as usual.
| Info |
|---|
The enabled settings are evaluated together to determine possible duplicates for a new request. E.g. if duplicate check is enabled for problemtype and property, only open requests with both the same problemtype and the same property are used as potential duplicates. |
1.5 Preferred suppliers
With Via the use of preferred suppliers, requests (or work orders) can automatically be assigned to the a preferred supplier based on the role specified in the problem type. More For more information about preferred supplier suppliers see: Preferred suppliers.
1.6 Corrective work orders
...