I would like to request a feature that adds dependency visibility and/or deletion safeguards within the web portal.
It would be helpful to easily see where an extension or call object is being used (ring groups, digital receptionists, queues, call flows, forwarding rules, etc.) without having to manually check each area. This becomes difficult and error-prone in larger environments. A simple dependency or “used by” view showing where an object is referenced across the system would greatly improve administration.
If full dependency tracking is not possible, even a basic safeguard during deletion would be valuable. For example, when attempting to delete an extension that is still in use, the system could either prevent deletion until dependencies are removed or clearly warn the administrator, list all usages, and require confirmation to proceed.
This would help avoid accidentally breaking call routing and reduce the risk of orphaned objects that usually only surface after users report issues. (Speaking from experience
)
It would be helpful to easily see where an extension or call object is being used (ring groups, digital receptionists, queues, call flows, forwarding rules, etc.) without having to manually check each area. This becomes difficult and error-prone in larger environments. A simple dependency or “used by” view showing where an object is referenced across the system would greatly improve administration.
If full dependency tracking is not possible, even a basic safeguard during deletion would be valuable. For example, when attempting to delete an extension that is still in use, the system could either prevent deletion until dependencies are removed or clearly warn the administrator, list all usages, and require confirmation to proceed.
This would help avoid accidentally breaking call routing and reduce the risk of orphaned objects that usually only surface after users report issues. (Speaking from experience
)
Upvote
7
