From 41474c3e7e1c665744edb9ab9e0eabeae0cb7698 Mon Sep 17 00:00:00 2001 From: reey Date: Thu, 24 Oct 2024 14:53:46 +0000 Subject: [PATCH] Update opcua changelog dates to 2024-10-24 08:41:45.709186 as version 1020.91.0 was released --- .../opcua-10-20-88-0-fix-device-type-encoding.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/change-logs/device-management/opcua-10-20-88-0-fix-device-type-encoding.md b/content/change-logs/device-management/opcua-10-20-88-0-fix-device-type-encoding.md index fbdf46e68c..fe6dcce267 100644 --- a/content/change-logs/device-management/opcua-10-20-88-0-fix-device-type-encoding.md +++ b/content/change-logs/device-management/opcua-10-20-88-0-fix-device-type-encoding.md @@ -1,5 +1,5 @@ --- -date: +date: '2024-10-24' title: Special character encoding in OPC UA device types is now available product_area: Device management & connectivity change_type: @@ -12,6 +12,6 @@ build_artifact: - value: tc-MLn0oFRX- label: opcua ticket: DM-2442 -version: 10.20.88.0 +version: 1020.88.0 --- Previously, when creating an OPC UA device type with special characters in any of the fields, the gateway was not reading it correctly which caused an error while creating mappings. This issue is now fixed, the gateway encodes and decodes special characters as expected.