To the D-Tools Development Team,

We would like to request an enhancement to the service order cloning functionality within the D-Tools mobile application. This feature would provide more flexibility and efficiency for our field technicians.

Current Situation

Currently, when cloning a service order in the app, the process duplicates all information from the original order. This is useful for identical follow-up tasks, but it's inefficient for creating a new, different order for the same client. This forces our technicians to spend valuable time manually deleting site items, notes, and other information that doesn't apply to the new service order.

Proposed Enhancement

We propose that when a user selects the option to "Clone" a service order, a dialog box appears with checkboxes, allowing the user to choose what information to carry over.

This would provide three clear options:

✅ Full Clone: This would be the default behavior as it exists today. It clones all parameters of the service order, including site items, tasks, and all other details.

✅ Partial Clone (Exclude Site Items & Tasks): This option would clone the core service order information (e.g., Client, Location, Contact Info) but would exclude specific job details like site items, tasks, and notes. This is ideal for creating a new job at a previous location.

✅ Start Anew (Clone Header Only): This option would clone only the most basic "header" information (Client, Location) and leave all other fields blank, providing a fresh template for a new order.

Use Case & Benefit

A common scenario for our technicians is returning to a client's site for a completely new issue. They need to create a new service order with the same client and location data, but with entirely new tasks and items.

With this proposed feature, a technician could simply:

Open the previous service order.

Select "Clone."

Choose the "Partial Clone" option.

This would instantly create a new, correctly-assigned service order without the need to manually delete old information, saving time, preventing data entry errors, and improving overall workflow efficiency in the field.

Thank you for your consideration. We believe this enhancement would be a significant quality-of-life improvement for many of your users.

Best regards,

Paul

Canadian Smart Systems