Merge pull request #460 from ritza-co/19.06.10

Docs 19.06.10 release (Week 28, 2025)

Author: sixhobbits

docs/infrastructure-management/devices/device-blade-chassis.mdx

@@ -10,7 +10,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 Locate your blade chassis in Device42 by navigating to **Resources > All Devices** and filtering for blade chassis devices:
 
-- Click **+ More** and select the **Blade Chassis** checkbox to display its dropdown menu.
+- Click **More Filters** and select the **Blade Chassis** checkbox to display its dropdown menu.
 - Choose **Yes** from the dropdown. 
 
 <ThemedImage
@@ -23,7 +23,7 @@ Locate your blade chassis in Device42 by navigating to **Resources > All Devices
 
 ## The Blades Tab
 
-Select a blade chassis from the Devices list page. Scroll down to the **Blades** tab, located below the device basic details section.
+Select a blade chassis from the Devices list page and, from the **Breakdown** panel on the right, click **Blades**.
 
 The **Blades** tab shows information about each device in the chassis. Blades are sorted by **Slot** number. Each blade has a link to its device page and displays its **Serial #**, **Asset #**, **Slot Location**, and **Hardware Model**.
 
@@ -37,7 +37,7 @@ The **Blades** tab shows information about each device in the chassis. Blades ar
 
 ### Add a New Blade 
 
-In device **Edit** mode, from the **Blade** tab, you can add blades to a chassis by clicking **+ Add New Blade**. The hardware model for the blade device must exist beforehand.
+In device **Edit** mode, from the **Blade** tab, you can add blades to a chassis by clicking **+ Add New**. The hardware model for the blade device must exist beforehand.
 
 <ThemedImage
   alt="Adding a new blade"
@@ -51,7 +51,7 @@ In device **Edit** mode, from the **Blade** tab, you can add blades to a chassis
 
 Layouts allow you to visualize blades within their chassis. The overall layout architecture is defined by the chassis [Hardware Model](#editing-hardware-models), which needs to be defined before you add and position specific blades. 
 
-From the view mode of the [device chassis page](#view-blade-chassis-devices), click the **ellipsis menu** and select **Layout** from the dropdown. 
+From the view mode of the [device chassis page](#view-blade-chassis-devices), click the **Layout** button.
 
 <ThemedImage
   alt="Device Layout button"
@@ -78,19 +78,17 @@ For blade-specific templating information, see the [Blade Slots documentation](d
 
 ### Editing Hardware Models
 
-To edit the layout of a blade, first define its Hardware Model under **Infrastructure > Hardware Models > + Add Device Hardware Model**. 
+To edit the layout of a blade, select its hardware model from the list page under **Infrastructure > Hardware Models** and click the **Model Layout** tab.
 
 <ThemedImage
   alt="Hardware Model menu"
   sources={{
-    light: useBaseUrl('/assets/images/device-blade-chassis/hardware-model-menu-light.png'),
-    dark: useBaseUrl('/assets/images/device-blade-chassis/hardware-model-menu-dark.png'),
+    light: useBaseUrl('/assets/images/device-blade-chassis/model-layout-tab-light.png'),
+    dark: useBaseUrl('/assets/images/device-blade-chassis/model-layout-tab-dark.png'),
   }}
 />
 
-You can find a link to an existing Hardware Model in the right panel of an individual **Layout**.
-
-Add a **New Slot** to an existing model by dragging it to the layout and filling in the fields:
+Turn on edit mode and add a **New Slot** to an existing model by dragging the slot box to the layout and filling in the fields:
 
 <ThemedImage
   alt="Add new blade"

docs/infrastructure-management/devices/device-blade-slots.mdx

@@ -10,7 +10,7 @@ A blade slot is a placeholder for a blade server in a blade chassis. You can add
 
 ## Create or Edit a Chassis Hardware Model 
 
-Navigate to **Infrastructure > Hardware Models** and select an existing hardware model or click **+ Add Device Hardware Model** to create a new one.
+Navigate to **Infrastructure > Hardware Models** and select an existing hardware model or click **Create** to create a new one.
 
 For **Physical Subtype**, choose **Rackable** or a similarly defined subtype to reveal the **Blade Host/Chassis** option and select it.
 
@@ -29,8 +29,8 @@ Scroll down to **Chassis Blade Slots** and add as many blade slots as necessary
 <ThemedImage
   alt="Add blade slots to chassis Hardware Model"
   sources={{
-    light: useBaseUrl('/assets/images/device-blade-slots/add-hardware-model-light.png'),
-    dark: useBaseUrl('/assets/images/device-blade-slots/add-hardware-model-dark.png'),
+    light: useBaseUrl('/assets/images/device-blade-slots/chassis-blade-slots-light.png'),
+    dark: useBaseUrl('/assets/images/device-blade-slots/chassis-blade-slots-dark.png'),
   }}
 />
 
@@ -63,7 +63,7 @@ Click **Turn ON** to enable edit mode, then drag and drop blade slots as desired
 
 The slots created when the Hardware Model was defined will appear in the left column under **Un-mapped Existing Blade Slots**.
 
-Toggle the grid background on or off using the **third semi-circle icon** to help you align the slots.
+Toggle the grid background on or off using the **Grid** icon to help you align the slots.
 
 <ThemedImage
   alt="Unmapped blade slots"
@@ -75,7 +75,7 @@ Toggle the grid background on or off using the **third semi-circle icon** to hel
 
 ### Editing a Blade Slot
 
-Double-click a blade slot to change the slot size, orientation, or number. 
+Double-click a blade slot or select it and click the **Pencil** icon to change the slot size, orientation, or number. 
 
 Note that parts cannot be placed into a blade slot; however, you can specify the height of the blade that occupies the slot.
 

docs/infrastructure-management/devices/device-cluster.mdx

@@ -12,7 +12,7 @@ A device cluster can be a server farm, an active-active cluster, an active-passi
 
 **Cluster** is one of the available device types, in addition to the **physical**, **virtual**, and **unknown** types. 
 
-To create a new cluster, navigate to **Resources > All Devices** and click **+ Add New Device**. Select **cluster** as the device **Type** to reveal the cluster-related options. 
+To create a new cluster, navigate to **Resources > All Devices** and click **Create**. Select **cluster** as the device **Type** to reveal the cluster-related options. 
 
 <ThemedImage
   alt="Adding a cluster-type device"
@@ -22,9 +22,7 @@ To create a new cluster, navigate to **Resources > All Devices** and click **+ A
   }}
 />
 
-Search for and select the devices you want to add to the cluster and move them across to the right-hand box using the **right arrow** button.
-
-Use the search box to narrow down the list of available devices and make it easy to select one among hundreds or thousands of devices. Add new devices using the **+ (plus sign)** button.
+Start typing in the **Devices in Cluster** field to narrow down the list of available devices and make it easy to select one among hundreds or thousands of devices. Add new devices using the **plus sign** button.
 
 <ThemedImage
   alt="Select devices for a cluster"

docs/infrastructure-management/devices/device-lifecycle-tab.mdx

@@ -6,41 +6,43 @@ sidebar_position: 7
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-## The LifeCycle Tab
+From version 19.05 of the Device42 UI onward, the **Lifecycle Tab** is only available using the device **Legacy** view. 
 
-Under the **Lifecycle tab** you can record and track asset lifecycle events, assign an asset QR code or barcode, and add purchasing information for a device. **Purchase/Support Info** includes fields to add **Vendor**, **Cost**, **Contract Type**, and **Service Type** details.
+In the device details view, from version 19.05 and later, the following sections have been moved from the **Lifecycle Tab** to the right-hand **Breakdown** panel:
+- **Asset Lifecycle**
+- **Purchase/Support Info**
+
+The **Device QR/Barcode** field is now under the **Details** section of the device details view.
 
 <ThemedImage
-  alt="The LifeCycle tab"
+  alt="The Breakdown panel"
   sources={{
-    light: useBaseUrl('/assets/images/device-lifecycle-tab/lifecycle-tab-light.png'),
-    dark: useBaseUrl('/assets/images/device-lifecycle-tab/lifecycle-tab-dark.png'),
+    light: useBaseUrl('/assets/images/device-lifecycle-tab/device-breakdown-panel-light.png'),
+    dark: useBaseUrl('/assets/images/device-lifecycle-tab/device-breakdown-panel-dark.png'),
   }}
-  style={{ width: '110%' }} 
 />
 
 ### Asset Lifecycle
 
-Provide the required details of **Date**, **Time**, and lifecycle **Event** to associate a new lifecycle event to the device. Optionally add an **End User** and related **Notes** and **Tags** to the event. Tags are useful for adding additional categories to manage your devices.
+Provide the required details of **Date**, **Time**, and lifecycle **Event** to associate a new lifecycle event with the device. Optionally add an **End User** and related **Notes** and **Tags** to the event. Tags are useful for adding additional categories to manage your devices.
 
-Add a new lifecycle event to the device using the **+ Add another Asset lifecycle** button. 
+Add a new lifecycle event to the device using the **+ Add New** button. 
 
 <ThemedImage
   alt="Asset lifecycle"
   sources={{
     light: useBaseUrl('/assets/images/device-lifecycle-tab/asset-lifecycle-event-light.png'),
     dark: useBaseUrl('/assets/images/device-lifecycle-tab/asset-lifecycle-event-dark.png'),
   }}
-  style={{ width: '110%' }} 
 />
 
-Some of the predefined **Events** have logic built-in. For example, you cannot choose **Checked Out** on a device or asset already checked out. Similarly, you can only select **Checked In** if the device is checked out.
+Some of the predefined **Events** have logic built in. For example, you cannot choose **Checked Out** on a device or asset already checked out. Similarly, you can only select **Checked In** if the device is checked out.
 
 To add logic to asset lifecycle **Events**, go to **Tools > Lifecycle Event Actions**.
 
 ### Add a New LifeCycle Event
 
-Define a custom lifecycle **Event** by clicking the **+** button near the **Events** dropdown menu.
+Define a custom lifecycle **Event** by clicking the **plus sign** button near the **Events** dropdown menu and then **Create** on the pop-up window. 
 
 <ThemedImage
   alt="Add new lifecycle event"
@@ -99,7 +101,7 @@ Enter purchase information related to the device under **Purchase/Support Info**
   }}
 />
 
-Add new **Purchase/Support Info** using the **+ Add New Purchase/Support Info** button.
+Add new **Purchase/Support Info** using the **+ Add New** button.
 
 <ThemedImage
   alt="Add new Purchase/Support Info"
@@ -109,4 +111,4 @@ Add new **Purchase/Support Info** using the **+ Add New Purchase/Support Info**
   }}
 />
 
-See [managing purchases](infrastructure-management/accounting/purchases.mdx) for more information.
+See [managing purchases](infrastructure-management/accounting/purchases.mdx) for more information.

docs/infrastructure-management/devices/device-other-tab.mdx

@@ -3,45 +3,70 @@ title: "Device - Other Tab"
 sidebar_position: 8
 ---
 
-### Other Tab
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
 
-![device other tab](/assets/images/other_tab_screenshot_HL.png)
+From version 19.05 of the Device42 UI onward, the **Other Tab** is only available using the **Legacy** view of the device details page.
 
-The Other Tab includes:
+In the latest versions of the UI, most of the sections that belonged to the **Other Tab** can be found in the right-hand **Breakdown** panel of the device details page. This includes:
 
-- **Device URLs** - see below
-- **Power Unit (PDU) Ports** - see below
-- **BIOS info** - BIOS version details
-- **Patch Panel Ports** - see below
-- **Device direct connection** - see below
-- **[Custom Key / Values](administration/custom-key-value-pairs-explained.mdx)** - create and store custom attributes
-- **File Attachments** - attach files associated to this device
-- **Power Monitoring** - see below
+- **Device URLs**
+- **BIOS Info** (under **Details** in the **Breakdown** panel)
+- **[Custom Fields](administration/custom-key-value-pairs-explained.mdx)** - used to create and store custom attributes
+- **File Attachments** - used to attach files associated with the device
 
-### Device URLs
+Port details for power units can be found under the **Ports** section on the details page of a power unit (located under **Infrastructure > Power Units**).
+
+<ThemedImage
+  alt="The Breakdown panel"
+  sources={{
+    light: useBaseUrl('/assets/images/device-other-tab/device-breakdown-view-other-tab-light.png'),
+    dark: useBaseUrl('/assets/images/device-other-tab/device-breakdown-view-other-tab-dark.png'),
+  }}
+/>
 
-![device URLs on other tab](/assets/images/device_URLs.png)
+### Device URLs
 
-Device URLs enable you to create links associated to the device.
+Device URLs enable you to create links associated with the device.
 
 The following variables can be used: 
 
-- `{{device.name}}` = device name 
-- `{{device.serial\_no}}` = serial number associated with this device
-- `{{device.asset\_no}}` = asset number associated with this device
+- `{{device.name}}`: Device name 
+- `{{device.serial_no}}`: Serial number associated with this device
+- `{{device.asset_no}}`: Asset number associated with this device
+
+<ThemedImage
+  alt="Device URLS"
+  sources={{
+    light: useBaseUrl('/assets/images/device-other-tab/device-urls-light.png'),
+    dark: useBaseUrl('/assets/images/device-other-tab/device-urls-dark.png'),
+  }}
+/>
 
 See also - [How to video adding links and other URLs](how-to-videos/adding-links-and-other-urls-to-devices.mdx)
 
 ### Ports in PDU
 
-![ports in PDU](/assets/images/power_unit_ports.png)
+Navigate to **Infrastructure > Power Units** and select a power unit. If this device has associated PDU ports, the ports are shown here.
 
-If this device has associated PDU ports, the ports would be shown here.
+<ThemedImage
+  alt="Power Unit Ports"
+  sources={{
+    light: useBaseUrl('/assets/images/device-other-tab/power-unit-ports-light.png'),
+    dark: useBaseUrl('/assets/images/device-other-tab/power-unit-ports-dark.png'),
+  }}
+/>
 
-### File Attachements
+### File Attachments
 
-![Uploaded File Attachements](/assets/images/file_attachments_other_tab.png)
+Any files you have uploaded or associated with this device will be shown here.
 
-Any files you have uploaded and/or associated with this device will be shown here.
+<ThemedImage
+  alt="File attachments"
+  sources={{
+    light: useBaseUrl('/assets/images/device-other-tab/file-attachments-light.png'),
+    dark: useBaseUrl('/assets/images/device-other-tab/file-attachments-dark.png'),
+  }}
+/>
 
-See also - managing [patch panels](infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx) and [switch ports](infrastructure-management/ipam/switch-ports.mdx) in Device42
+See also: Managing [patch panels](infrastructure-management/connectivity/patch-panels/patch-panel-cable-management-definitions-and-legends-2.mdx) and [switch ports](infrastructure-management/ipam/switch-ports.mdx) in Device42.