feat: 新增规则链中英文配置

@@ -11,16 +11,48 @@ export default {
   customerAttributes: {
     name: 'customer attributes',
     details: `If Attributes enrichment configured, server scope attributes are added into Message metadata. If Latest Telemetry enrichment configured, latest telemetry added into metadata. To access those attributes in other nodes this template can be used <code>metadata.temperature</code>.`,
-    description: `Add Originators Customer Attributes or Latest Telemetry into Message Metadata`,
+    description: 'Add Originators Customer Attributes or Latest Telemetry into Message Metadata',
   },
   customerDetails: {
     name: 'customer details',
     details: `If checkbox: <b>Add selected details to the message metadata</b> is selected, existing fields will be added to the message metadata instead of message data.<br><br><b>Note:</b> only Device, Asset, and Entity View type are allowed.<br><br>If the originator of the message is not assigned to Customer, or originator type is not supported - Message will be forwarded to <b>Failure</b> chain, otherwise, <b>Success</b> chain will be used.`,
-    description: `Adds fields from Customer details to the message body or metadata`,
+    description: 'Adds fields from Customer details to the message body or metadata',
   },
   originatorAttributes: {
     name: 'originator attributes',
     details: `If Attributes enrichment configured, <b>CLIENT/SHARED/SERVER</b> attributes are added into Message metadata with specific prefix: <i>cs/shared/ss</i>. Latest telemetry value added into metadata without prefix. To access those attributes in other nodes this template can be used <code>metadata.cs_temperature</code> or <code>metadata.shared_limit</code> `,
-    description: `Add Message Originator Attributes or Latest Telemetry into Message Metadata`,
+    description: 'Add Message Originator Attributes or Latest Telemetry into Message Metadata',
+  },
+  originatorFields: {
+    name: 'originator fields',
+    details: `Will fetch fields values specified in mapping. If specified field is not part of originator fields it will be ignored.`,
+    description: 'Add Message Originator fields values into Message Metadata',
+  },
+  originatorTelemetry: {
+    name: 'originator telemetry',
+    details: `The node allows you to select fetch mode: <b>FIRST/LAST/ALL</b> to fetch telemetry of certain time range that are added into Message metadata without any prefix. If selected fetch mode <b>ALL</b> Telemetry will be added like array into Message Metadata where <b>key</b> is Timestamp and <b>value</b> is value of Telemetry.</br>If selected fetch mode <b>FIRST</b> or <b>LAST</b> Telemetry will be added like string without Timestamp.</br>Also, the rule node allows you to select telemetry sampling order: <b>ASC</b> or <b>DESC</b>. </br>Aggregation feature allows you to fetch aggregated telemetry as a single value by <b>AVG, COUNT, SUM, MIN, MAX, NONE</b>. </br><b>Note</b>: The maximum size of the fetched array is 1000 records.\n `,
+    description: 'Add Message Originator Telemetry for selected time range into Message Metadata\n',
+  },
+  relatedAttributes: {
+    name: 'related attributes',
+    details: `Related Entity found using configured relation direction and Relation Type. If multiple Related Entities are found, only first Entity is used for attributes enrichment, other entities are discarded. If Attributes enrichment configured, server scope attributes are added into Message metadata. If Latest Telemetry enrichment configured, latest telemetry added into metadata. To access those attributes in other nodes this template can be used <code>metadata.temperature</code>.`,
+    description:
+      'Add Originators Related Entity Attributes or Latest Telemetry into Message Metadata',
+  },
+  relatedDeviceAttributes: {
+    name: 'related device attributes',
+    details: `If Attributes enrichment configured, <b>CLIENT/SHARED/SERVER</b> attributes are added into Message metadata with specific prefix: <i>cs/shared/ss</i>. Latest telemetry value added into metadata without prefix. To access those attributes in other nodes this template can be used <code>metadata.cs_temperature</code> or <code>metadata.shared_limit</code>`,
+    description:
+      'Add Originators Related Device Attributes and Latest Telemetry value into Message Metadata',
+  },
+  tenantAttributes: {
+    name: 'tenant attributes',
+    details: `If Attributes enrichment configured, server scope attributes are added into Message metadata. If Latest Telemetry enrichment configured, latest telemetry added into metadata. To access those attributes in other nodes this template can be used <code>metadata.temperature</code>.`,
+    description: 'Add Originators Tenant Attributes or Latest Telemetry into Message Metadata',
+  },
+  tenantDetails: {
+    name: 'tenant details',
+    details: `If checkbox: <b>Add selected details to the message metadata</b> is selected, existing fields will be added to the message metadata instead of message data.<br><br><b>Note:</b> only Device, Asset, and Entity View type are allowed.<br><br>If the originator of the message is not assigned to Tenant, or originator type is not supported - Message will be forwarded to <b>Failure</b> chain, otherwise, <b>Success</b> chain will be used.`,
+    description: 'Adds fields from Tenant details to the message body or metadata',
   },
 };

@@ -19,8 +19,38 @@ export default {
     description: `将“客户详细信息”中的字段添加到消息正文或元数据中。`,
   },
   originatorAttributes: {
-    name: '客户详情',
-    details: `如果选中：【将选定的详细信息添加到消息元数据】，则现有字段将添加到消息元数据，而不是消息数据。注意：只允许设备、资产和实体视图类型；如果消息的原始发件人未分配给客户或者不支持原始发件人类型的消息将转发到失败链路，否则将使用成功链路。`,
-    description: `将“客户详细信息”中的字段添加到消息正文或元数据中。`,
+    name: '发起者属性',
+    details: `如果配置了单个/多个属性，客户端属性/共享属性/服务器属性将添加到具有特定前缀的消息元数据中：cs/SHARED/ss。添加到元数据中的最新遥测值，不带前缀。要访问其他节点中的这些属性，可以使用metadata.cs_temperature或metadata.shared_limit。`,
+    description: `将消息发起者的属性或最新遥测添加到消息元数据中。`,
+  },
+  originatorFields: {
+    name: '发起者字段',
+    details: `将获取映射中指定的字段值。如果指定的字段不是原始发件人字段的一部分，它将被忽略。`,
+    description: '将消息发起人字段值添加到消息元数据中。',
+  },
+  originatorTelemetry: {
+    name: '发起者遥测',
+    details: `该节点允许您选择提取模式：FIRST/LAST/ALL 以提取添加到消息元数据中的特定时间范围的遥测数据，而不带任何前缀。如果选择提取模式，ALL遥测将像数组一样添加到消息元数据中，其中Key为时间戳，Value是遥测的值；如果选择提取模式FIRST或LAST遥测将像不带时间戳的字符串一样添加；此外，规则节点允许您选择遥测采样顺序：ASC或DESC；聚合功能允许您通过AVG、COUNT、SUM、MIN、MAX、NONE将聚合遥测作为单个值获取；注意：提取数据放入数组中最大记录为1000条。`,
+    description: '将选定时间范围的消息发起人遥测添加到消息元数据中。',
+  },
+  relatedAttributes: {
+    name: '关联属性',
+    details: `使用配置的关系方向和关系类型找到相关实体；若找到多个相关实体，则只有第一个实体用于单个/多个属性，其他实体将被丢弃；如果配置了属性，则会将服务器范围属性添加到消息元数据中；如果配置了最新遥测，则将最新遥测添加到元数据中。要访问其他节点中的这些属性，可以使用metadata.temperature访问。`,
+    description: '将发起人相关实体属性或最新遥测添加到消息元数据中。',
+  },
+  relatedDeviceAttributes: {
+    name: '关联设备属性',
+    details: `如果配置了单个/多个属性，CLIENT/SHARED/SERVER 属性将添加到具有特定前缀的消息元数据中：cs/SHARED/ss。添加到元数据中的最新遥测值，不带前缀。要访问其他节点中的这些属性，可以使用 metadata.cs_temperature或metadata.shared_limit。`,
+    description: '关联设备属性将发起者关联设备属性和最新遥测值添加到消息元数据中。',
+  },
+  tenantAttributes: {
+    name: '租户属性',
+    details: `如果配置了单个/多个属性，则会将服务器范围属性添加到消息元数据中。如果配置了单个/多个“最新遥测”，则将最新遥测添加到元数据中。要访问其他节点中的这些属性，可以使用metadata.temperature。`,
+    description: '将发起者租户属性或最新遥测添加到消息元数据中。',
+  },
+  tenantDetails: {
+    name: '租户属性',
+    details: `如果配置了单个/多个属性，则会将服务器范围属性添加到消息元数据中。如果配置了单个/多个“最新遥测”，则将最新遥测添加到元数据中。要访问其他节点中的这些属性，可以使用metadata.temperature。`,
+    description: '将发起者租户属性或最新遥测添加到消息元数据中。',
   },
 };

@@ -2,9 +2,11 @@ import { EnrichmentCategoryComponentEnum } from '../../../enum/category';
 import { useCreateNodeKey } from '../../../hook/useCreateNodeKey';
 import type { NodeItemConfigType } from '../../../types/node';
 import { RuleNodeTypeEnum } from '../../index.type';
+import { useI18n } from '/@/hooks/web/useI18n';
 
 const keys = useCreateNodeKey(EnrichmentCategoryComponentEnum.ORIGINATOR_FIELDS);
 
+const { t } = useI18n(); //加载国际化
 export interface OriginatorFieldsDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const OriginatorFieldsConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetOriginatorFieldsNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'originator fields',
+  name: t('enrichments.index.originatorFields.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'Will fetch fields values specified in mapping. If specified field is not part of originator fields it will be ignored.',
-      description: 'Add Message Originator fields values into Message Metadata',
+      details: t('enrichments.index.originatorFields.details'),
+      description: t('enrichments.index.originatorFields.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure'],

@@ -2,9 +2,11 @@ import { EnrichmentCategoryComponentEnum } from '../../../enum/category';
 import { useCreateNodeKey } from '../../../hook/useCreateNodeKey';
 import type { NodeItemConfigType } from '../../../types/node';
 import { RuleNodeTypeEnum } from '../../index.type';
+import { useI18n } from '/@/hooks/web/useI18n';
 
 const keys = useCreateNodeKey(EnrichmentCategoryComponentEnum.ORIGINATOR_TELEMETRY);
 
+const { t } = useI18n(); //加载国际化
 export interface OriginatorTelemetryDataType {
   someConfiguration?: Recordable;
 }
@@ -13,13 +15,11 @@ export const OriginatorTelemetryConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetTelemetryNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'originator telemetry',
+  name: t('enrichments.index.originatorTelemetry.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'The node allows you to select fetch mode: <b>FIRST/LAST/ALL</b> to fetch telemetry of certain time range that are added into Message metadata without any prefix. If selected fetch mode <b>ALL</b> Telemetry will be added like array into Message Metadata where <b>key</b> is Timestamp and <b>value</b> is value of Telemetry.</br>If selected fetch mode <b>FIRST</b> or <b>LAST</b> Telemetry will be added like string without Timestamp.</br>Also, the rule node allows you to select telemetry sampling order: <b>ASC</b> or <b>DESC</b>. </br>Aggregation feature allows you to fetch aggregated telemetry as a single value by <b>AVG, COUNT, SUM, MIN, MAX, NONE</b>. </br><b>Note</b>: The maximum size of the fetched array is 1000 records.\n ',
-      description:
-        'Add Message Originator Telemetry for selected time range into Message Metadata\n',
+      details: t('enrichments.index.originatorTelemetry.details'),
+      description: t('enrichments.index.originatorTelemetry.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure'],

@@ -2,9 +2,11 @@ import { EnrichmentCategoryComponentEnum } from '../../../enum/category';
 import { useCreateNodeKey } from '../../../hook/useCreateNodeKey';
 import type { NodeItemConfigType } from '../../../types/node';
 import { RuleNodeTypeEnum } from '../../index.type';
+import { useI18n } from '/@/hooks/web/useI18n';
 
 const keys = useCreateNodeKey(EnrichmentCategoryComponentEnum.RELATED_ATTRIBUTES);
 
+const { t } = useI18n(); //加载国际化
 export interface RelatedAttributesDataType {
   someConfiguration?: Recordable;
 }
@@ -13,13 +15,11 @@ export const RelatedAttributesConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetRelatedAttributeNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'related attributes',
+  name: t('enrichments.index.relatedAttributes.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'Related Entity found using configured relation direction and Relation Type. If multiple Related Entities are found, only first Entity is used for attributes enrichment, other entities are discarded. If Attributes enrichment configured, server scope attributes are added into Message metadata. If Latest Telemetry enrichment configured, latest telemetry added into metadata. To access those attributes in other nodes this template can be used <code>metadata.temperature</code>.',
-      description:
-        'Add Originators Related Entity Attributes or Latest Telemetry into Message Metadata',
+      details: t('enrichments.index.relatedAttributes.details'),
+      description: t('enrichments.index.relatedAttributes.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure'],

@@ -2,9 +2,11 @@ import { EnrichmentCategoryComponentEnum } from '../../../enum/category';
 import { useCreateNodeKey } from '../../../hook/useCreateNodeKey';
 import type { NodeItemConfigType } from '../../../types/node';
 import { RuleNodeTypeEnum } from '../../index.type';
+import { useI18n } from '/@/hooks/web/useI18n';
 
 const keys = useCreateNodeKey(EnrichmentCategoryComponentEnum.RELATED_DEVICE_ATTRIBUTES);
 
+const { t } = useI18n(); //加载国际化
 export interface RelatedDeviceAttributesDataType {
   someConfiguration?: Recordable;
 }
@@ -13,13 +15,11 @@ export const RelatedDeviceAttributesConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetDeviceAttrNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'related device attributes',
+  name: t('enrichments.index.relatedDeviceAttributes.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'If Attributes enrichment configured, <b>CLIENT/SHARED/SERVER</b> attributes are added into Message metadata with specific prefix: <i>cs/shared/ss</i>. Latest telemetry value added into metadata without prefix. To access those attributes in other nodes this template can be used <code>metadata.cs_temperature</code> or <code>metadata.shared_limit</code> ',
-      description:
-        'Add Originators Related Device Attributes and Latest Telemetry value into Message Metadata',
+      details: t('enrichments.index.relatedDeviceAttributes.details'),
+      description: t('enrichments.index.relatedDeviceAttributes.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure'],

@@ -2,9 +2,11 @@ import { EnrichmentCategoryComponentEnum } from '../../../enum/category';
 import { useCreateNodeKey } from '../../../hook/useCreateNodeKey';
 import type { NodeItemConfigType } from '../../../types/node';
 import { RuleNodeTypeEnum } from '../../index.type';
+import { useI18n } from '/@/hooks/web/useI18n';
 
 const keys = useCreateNodeKey(EnrichmentCategoryComponentEnum.TENANT_ATTRIBUTES);
 
+const { t } = useI18n(); //加载国际化
 export interface TenantAttributesDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const TenantAttributesConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetTenantAttributeNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'tenant attributes',
+  name: t('enrichments.index.tenantAttributes.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'If Attributes enrichment configured, server scope attributes are added into Message metadata. If Latest Telemetry enrichment configured, latest telemetry added into metadata. To access those attributes in other nodes this template can be used <code>metadata.temperature</code>.',
-      description: 'Add Originators Tenant Attributes or Latest Telemetry into Message Metadata',
+      details: t('enrichments.index.tenantAttributes.details'),
+      description: t('enrichments.index.tenantAttributes.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure'],