Differences

This shows you the differences between two versions of the page.

--- extensions:teemip-cable-mgmt [2025/07/15 16:02] – [Cable Management] cnaud
+++ extensions:teemip-cable-mgmt [2025/07/16 09:20] (current) – [Revision History] cnaud
@@ Line 32: / Line 32: @@
 ===== Revision History =====
 ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^
-|  **1.4.0**  |  2025-07-15  |  Supported  |  3.2.0  |  3.2.0  | - A Cable Category may be set on a Patch Panel and on a Network Socket\\ - The creation of Back End Network Cables from a Patch Panel may be limited to a given number \\ - The organization of a Network Socket is the one of its Patch Panel (if set) or its Location otherwise \\ - A Back End Network Cable may be attached to a Breakout Cable \\ - Local and peer device and physical interface attributes have been added to Cross Connects \\ - Cables that make the path of a Cross Connect are displayed in a tab \\ - Sockets that make the Cross Connect are automatically set or reset with a pointer to the Cross Connect they belong to \\ - Once in production, all device and front end cables of a Cross Connect may be created \\ - Cable names can be automatically computed from a method that may be overloaded \\ - Replace legacy CRUD methods by new CRUD events |
+|  **1.4.0**  |  2025-07-15  |  Supported  |  3.2.0  |  3.2.0  | - Add Brazilian translation \\ - A Cable Category may be set on a Patch Panel and on a Network Socket\\ - The creation of Back End Network Cables from a Patch Panel may be limited to a given number \\ - The organization of a Network Socket is the one of its Patch Panel (if set) or its Location otherwise \\ - A Back End Network Cable may be attached to a Breakout Cable \\ - Local and peer device and physical interface attributes have been added to Cross Connects \\ - Cables that make the path of a Cross Connect are displayed in a tab \\ - Sockets that make the Cross Connect are automatically set or reset with a pointer to the Cross Connect they belong to \\ - Once in production, all device and front end cables of a Cross Connect may be created \\ - Cable names can be automatically computed from a method that may be overloaded \\ - Replace legacy CRUD methods by new CRUD events |
 |  1.3.1  |  2024-10-29  |  Obsolete  |  3.1.2  |  3.2.0  | - Issue [[https://github.com/TeemIp/teemip-cable-mgmt/issues/6|#6]] - Can't create second direct cable connection between two devices  \\ - Breakout Cable: edit the n:n relations with PatchPanels while on display and not on edition anymore \\ - Breakout Vable: improve automation functions |
 |  1.3.0  |  2024-06-26  |  Obsolete  |  3.1.1  |  3.1.4  | - A Patch Panel can be mounted in an enclosure \\ - Network Sockets can be automatically created for a given Patch Panel \\ - Back End Cables can be automatically created between the sockets of 2 Patch Panels \\ - Number of free & ready Network Sockets in Patch Panels are displayed \\ - Cross Connects and Breakout Cables are now modelized \\ - Wiring paths can be proposed to connect the 2 Patch Panels of a Cross Connect \\ - Documents can be attached to Network Cables |

Documentation

User Tools

Site Tools

Differences

Page Tools