Automatically Delete Parent VC-12 When a E1 Transport Container Is Deleted

Feature Request Summary: 

When a service such as an E1 is deleted or it's re-routed and a transport container removed from the service routing editor, ConnectMaster should automatically delete the associated parent transport container, such as the VC-12. This will prevent orphaned transport container records from remaining in the system and ensure the network inventory accurately reflects the current service routing.

Functional Area / Module: 

Transport Container

Description/Use Cases: 

When an E1 transport container is created and routed across all hops in the routing editor, ConnectMaster also creates or maintains the associated parent VC-12 transport container.

If the service is later re-routed or the E1 is deleted, the associated parent VC-12 should also be removed automatically where it is no longer required.

Currently, the E1 can be deleted or a TC removed from the routing editor, but the associated VC-12 remains in the system. This leaves an orphaned parent transport container that no longer reflects the active routing.

Expected behaviour: when the E1 is deleted or a TC removed from the routing editor, ConnectMaster should automatically check whether the associated VC-12 is still required. If it is not used, the VC-12 should be deleted at the same time.

Business impact of limitation or missing of the feature:

If the parent transport container is not deleted when the child transport container is removed from the routing editor, obsolete VC-12 records remain in ConnectMaster. This can create inaccurate network inventory data, require manual investigation and cleanup, and increase the risk of users making routing or capacity decisions based on stale information. Automating the deletion of the parent container would improve data accuracy, reduce rework for planners and network administrators, and support more efficient service rerouting workflows.