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

@@ -8,10 +8,17 @@ VITE_GLOB_PUBLIC_PATH = /
 # Please note that no line breaks
 
 # 本地
-VITE_PROXY = [["/api","http://localhost:8080/api"],["/thingskit-scada","http://localhost:3000/"],["/large-designer", "http://localhost:5555/large-designer/"]]
+<<<<<<< Updated upstream
+VITE_PROXY = [["/api","http://192.168.10.146:8080/api"],["/thingskit-scada","http://localhost:3000/"],["/large-designer", "http://localhost:5555/large-designer/"]]
 
 # 实时数据的ws地址
-VITE_GLOB_WEB_SOCKET = ws://localhost:8080/api/ws/plugins/telemetry?token=
+VITE_GLOB_WEB_SOCKET = ws://192.168.10.146:8080/api/ws/plugins/telemetry?token=
+=======
+VITE_PROXY = [["/api","http://222.180.200.114:48080/api"],["/thingskit-scada","http://192.168.10.115:3000/"],["/large-designer", "http://192.168.10.115:5555/large-designer/"]]
+
+# 实时数据的ws地址
+VITE_GLOB_WEB_SOCKET = ws://222.180.200.114:48080/api/ws/plugins/telemetry?token=
+>>>>>>> Stashed changes
 
 # Delete console
 VITE_GLOB_DROP_CONSOLE = true

@@ -12,17 +12,17 @@
     overlayClassName="app-locale-picker-overlay"
   >
     <span class="cursor-pointer flex items-center" :style="{ color: color }">
-      <!-- <Icon icon="ion:language" /> -->
-      <!-- <span v-if="showText" class="ml-1">{{ getLocaleText }}</span> -->
+      <Icon icon="ion:language" />
+      <span v-if="showText" class="ml-1">{{ getLocaleText }}</span>
     </span>
   </Dropdown>
 </template>
 <script lang="ts" setup>
   import type { LocaleType } from '/#/config';
   import type { DropMenu } from '/@/components/Dropdown';
-  import { ref, watchEffect, unref } from 'vue';
+  import { ref, watchEffect, unref, computed } from 'vue';
   import { Dropdown } from '/@/components/Dropdown';
-  // import { Icon } from '/@/components/Icon';
+  import { Icon } from '/@/components/Icon';
   import { useLocale } from '/@/locales/useLocale';
   import { localeList } from '/@/settings/localeSetting';
 
@@ -45,13 +45,13 @@
 
   const { changeLocale, getLocale } = useLocale();
 
-  // const getLocaleText = computed(() => {
-  //   const key = selectedKeys.value[0];
-  //   if (!key) {
-  //     return '';
-  //   }
-  //   return localeList.find((item) => item.event === key)?.text;
-  // });
+  const getLocaleText = computed(() => {
+    const key = selectedKeys.value[0];
+    if (!key) {
+      return '';
+    }
+    return localeList.find((item) => item.event === key)?.text;
+  });
 
   watchEffect(() => {
     selectedKeys.value = [unref(getLocale)];

+/**
+ *规则链 属性集 英文配置文件
+  目前共有10个，分类按名称进行配置
+ */
+export default {
+  calculateDelta: {
+    name: 'calculate delta',
+    details: `Calculates delta and period based on the previous time-series reading and current data. Delta calculation is done in scope of the message originator, e.g. device, asset or customer. If there is input key, the output relation will be 'Success' unless delta is negative and corresponding configuration parameter is set. If there is no input value key in the incoming message, the output relation will be 'Other'.`,
+    description: `Calculates and adds 'delta' value into message based on the incoming and previous value`,
+  },
+  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`,
+  },
+  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`,
+  },
+  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`,
+  },
+};

+/**
+ *规则链 筛选器 英文配置文件
+  目前共有11个，分类按名称进行配置
+ */
+export default {
+  checkAlarmStatus: {
+    name: 'check alarm status',
+    details:
+      'If the alarm status matches the specified one - msg is success if does not match - msg is failure.',
+    description: 'Checks alarm status.',
+  },
+  checkExistenceFields: {
+    name: 'check existence fields',
+    details: `If selected checkbox 'Check that all selected keys are present'\" and all keys in message data and metadata are exist - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.\nElse if the checkbox is not selected, and at least one of the keys from data or metadata of the message exists - send Message via <b>True</b> chain, otherwise, <b>False</b> chain is used. `,
+    description: 'Checks the existence of the selected keys from message data and metadata.',
+  },
+  checkRelation: {
+    name: 'check relation',
+    details:
+      'If at least one relation exists - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.',
+    description: `Checks the relation from the selected entity to the originator of the message by type and direction if 'Check for single entity' is set to true, otherwise rule node will check if exist any relation to the originator of the message by type and direction.`,
+  },
+  gpsGeofencingFilter: {
+    name: 'gps geofencing filter',
+    details: `Extracts latitude and longitude parameters from incoming message and returns 'True' if they are inside configured perimeters, 'False' otherwise.`,
+    description: 'Filter incoming messages by GPS based geofencing',
+  },
+  messageType: {
+    name: 'message type',
+    details: `If incoming MessageType is expected - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.`,
+    description: 'Filter incoming messages by Message Type',
+  },
+  messageTypeSwitch: {
+    name: 'message type switch',
+    details: `Sends messages with message types <b>"Post attributes", "Post telemetry", "RPC Request"</b> etc. via corresponding chain, otherwise <b>Other</b> chain is used.`,
+    description: 'Route incoming messages by Message Type',
+  },
+  originatorType: {
+    name: 'originator type',
+    details: `If Originator Type of incoming message is expected - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.`,
+    description: 'Filter incoming messages by message Originator Type',
+  },
+  originatorTypeSwitch: {
+    name: 'originator type switch',
+    details: `Routes messages to chain according to the originator type ('Device', 'Asset', etc.).`,
+    description: 'Route incoming messages by Message Originator Type',
+  },
+  sceneReact: {
+    name: 'originator type switch',
+    details: `Implement interactive control of devices based on business scenarios`,
+    description: 'Implement interactive control of devices based on business scenarios',
+  },
+  script: {
+    name: 'script',
+    details: `Evaluate incoming Message with configured JS condition. If <b>True</b> - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.Message payload can be accessed via <code>msg</code> property. For example <code>msg.temperature < 10;</code><br/>Message metadata can be accessed via <code>metadata</code> property. For example <code>metadata.customerName === 'John';</code><br/>Message type can be accessed via <code>msgType</code> property.`,
+    description: 'Filter incoming messages using JS script',
+  },
+  switch: {
+    name: 'switch',
+    details: `Node executes configured JS script. Script should return array of next Chain names where Message should be routed. If Array is empty - message not routed to next Node. Message payload can be accessed via <code>msg</code> property. For example <code>msg.temperature < 10;</code><br/>Message metadata can be accessed via <code>metadata</code> property. For example <code>metadata.customerName === 'John';</code><br/>Message type can be accessed via <code>msgType</code> property.`,
+    description: 'Route incoming Message to one or multiple output chains',
+  },
+};

+/**
+ *规则链 属性集 中文配置文件
+  目前共有10个，分类按名称进行配置
+ */
+export default {
+  calculateDelta: {
+    name: '计算增量',
+    details: `该节点可以在规则中获取上一次遥测的值，以此可以实现二次遥测的差。比如一个设备，一天上传一次数据，如果你要对比今天和昨天的数据，并将两者数据差保存到数据库，就能够使用该节点。增量计算是在消息发起者的范围内完成的，例如设备、资产或客户。如果有输入键，则输出关系将为“成功”，除非增量为负并且设置了相应的配置参数。如果传入消息中没有输入值键，则输出关系将为“其他”。`,
+    description: `根据传入值和上一个值计算增量值并将其添加到消息中。`,
+  },
+  customerAttributes: {
+    name: '客户端属性',
+    details: `如果已配置属性，则会将服务器范围属性添加到消息元数据中。如果配置了'最新遥测'，则将最新遥测添加到元数据中。要访问其他节点中的这些属性，可以使用metadata.temperature访问。`,
+    description: `将发起者客户端属性或最新遥测添加到消息元数据中。`,
+  },
+  customerDetails: {
+    name: '客户详情',
+    details: `如果选中：【将选定的详细信息添加到消息元数据】，则现有字段将添加到消息元数据，而不是消息数据。注意：只允许设备、资产和实体视图类型；如果消息的原始发件人未分配给客户或者不支持原始发件人类型的消息将转发到失败链路，否则将使用成功链路。`,
+    description: `将“客户详细信息”中的字段添加到消息正文或元数据中。`,
+  },
+  originatorAttributes: {
+    name: '客户详情',
+    details: `如果选中：【将选定的详细信息添加到消息元数据】，则现有字段将添加到消息元数据，而不是消息数据。注意：只允许设备、资产和实体视图类型；如果消息的原始发件人未分配给客户或者不支持原始发件人类型的消息将转发到失败链路，否则将使用成功链路。`,
+    description: `将“客户详细信息”中的字段添加到消息正文或元数据中。`,
+  },
+};

+/**
+ *规则链 筛选器 中文配置文件
+ 目前共有11个，分类按名称进行配置
+ */
+export default {
+  checkAlarmStatus: {
+    name: '检测报警状态',
+    details: '如果警报状态与指定的状态匹配，则消息成功；如果不匹配，则消息失败。',
+    description: '检测报警状态',
+  },
+  checkExistenceFields: {
+    name: '检测字段是否存在',
+    details: `如果选中【检查所有选择的键是否存在】 ，就必选满足Message data中配置的字段和Message metadata中配置的字段，都必须存在才会返回true发送消息，否则返回false。
+    如果未选中，Message data中配置的字段或者Message metadata中配置的字段至少有一个键存在返回true，否则返回false。`,
+    description: '检查消息中的字段数据和消息元数据中所选择的键是否都存在。',
+  },
+  checkRelation: {
+    name: '检查实体关系是否存在',
+    details: '如果至少存在一个关系，通过True链路发送消息，否则使用False链路。',
+    description: `检查关系是按类型和方向将所选实体发送给消息的发起者；如果“检查单个实体”设置为true，否则规则节点将按类型和方向检查是否存在与消息发起者的任何关系。`,
+  },
+  gpsGeofencingFilter: {
+    name: 'GPS地理围栏过滤器',
+    details: `从传入消息中提取纬度和经度参数，如果它们位于配置的周界内，则返回'True'，否则返回'False'。`,
+    description: '通过基于GPS的地理围栏过滤传入消息。',
+  },
+  messageType: {
+    name: '消息类型',
+    details: `如果需要传入消息类型通过，则'True'链发送消息，否则使用'False'链路。`,
+    description: '按消息类型筛选传入消息。',
+  },
+  messageTypeSwitch: {
+    name: '消息类型转换',
+    details: `通过相应链发送消息类型为'属性上报'，'遥测上报'，'RPC请求'等的消息，否则使用其他链。`,
+    description: '按消息类型路由传入消息。',
+  },
+  originatorType: {
+    name: '发起者类型',
+    details: `如果预期传入消息的发起者类型，通过则True链发送消息，否则使用False链路。`,
+    description: '按消息发起者类型过滤传入消息。',
+  },
+  originatorTypeSwitch: {
+    name: '发起者类型转换',
+    details: `根据发起方类型（设备、资产等）将消息路由到链。`,
+    description: '按消息发起者类型路由传入消息。',
+  },
+  sceneReact: {
+    name: '场景交互',
+    details: `基于业务场景，实现设备的交互控制。`,
+    description: '基于业务场景，实现设备的交互控。',
+  },
+  script: {
+    name: 'JS脚本',
+    details: `使用配置的JS匹配条件传入消息。如果为True，则通过True链发送消息，否则使用False链。可以通过msg属性访问消息负载。 例如 msg.temperature < 10 ;可以通过metadata属性访问消息元数据。例如metadata.customerName === 'John';可以通过msgType属性访问消息类型。`,
+    description: '使用JS脚本过滤传入消息。',
+  },
+  switch: {
+    name: '转换器',
+    details: `节点执行配置的JS脚本。脚本返回的消息应该路由到下一个链名称的数组。如果数组为空，则消息不会路由到下一个节点。可以通过 msg 属性访问消息负载。例如 msg.temperature < 10;  可以通过 metadata 属性访问消息元数据。例如  metadata.customerName==='John' ；可以通过 msgType属性访问消息类型。`,
+    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.CALCULATE_DELTA);
 
+const { t } = useI18n(); //加载国际化
 export interface CalculateDeltaDataType {
   someConfiguration?: Recordable;
 }
@@ -13,13 +15,11 @@ export const CalculateDeltaConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.CalculateDeltaNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'calculate delta',
+  name: t('enrichments.index.calculateDelta.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        "Calculates delta and period based on the previous time-series reading and current data. Delta calculation is done in scope of the message originator, e.g. device, asset or customer. If there is input key, the output relation will be 'Success' unless delta is negative and corresponding configuration parameter is set. If there is no input value key in the incoming message, the output relation will be 'Other'.",
-      description:
-        "Calculates and adds 'delta' value into message based on the incoming and previous value",
+      details: t('enrichments.index.calculateDelta.details'),
+      description: t('enrichments.index.calculateDelta.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure', 'Other'],

@@ -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.CUSTOMER_ATTRIBUTES);
 
+const { t } = useI18n(); //加载国际化
 export interface CustomerAttributesDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const CustomerAttributesConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetCustomerAttributeNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'customer attributes',
+  name: t('enrichments.index.customerAttributes.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 Customer Attributes or Latest Telemetry into Message Metadata',
+      details: t('enrichments.index.customerAttributes.details'),
+      description: t('enrichments.index.customerAttributes.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.CUSTOMER_DETAILS);
 
+const { t } = useI18n(); //加载国际化
 export interface CustomerDetailsDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const CustomerDetailsConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetCustomerDetailsNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'customer details',
+  name: t('enrichments.index.customerDetails.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      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',
+      details: t('enrichments.index.customerDetails.details'),
+      description: t('enrichments.index.customerDetails.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_ATTRIBUTES);
 
+const { t } = useI18n(); //加载国际化
 export interface OriginatorAttributesDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const OriginatorAttributesConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.metadata.TbGetAttributesNode',
   categoryType: RuleNodeTypeEnum.ENRICHMENT,
-  name: 'originator attributes',
+  name: t('enrichments.index.originatorAttributes.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 Message Originator Attributes or Latest Telemetry into Message Metadata',
+      details: t('enrichments.index.originatorAttributes.details'),
+      description: t('enrichments.index.originatorAttributes.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Success', 'Failure'],

@@ -3,9 +3,11 @@ import { useCreateNodeKey } from '../../../hook/useCreateNodeKey';
 import type { NodeItemConfigType } from '../../../types/node';
 import { RuleNodeTypeEnum } from '../../index.type';
 import { AlarmStatus } from '/@/enums/alarmEnum';
+import { useI18n } from '/@/hooks/web/useI18n';
 
 const keys = useCreateNodeKey(FilterCategoryComponentEnum.CHECK_ALARM_STATUS);
 
+const { t } = useI18n(); //加载国际化
 export interface CheckAlarmStatusDataType {
   alarmStatusList: AlarmStatus[];
 }
@@ -14,13 +16,12 @@ export const CheckAlarmStatusConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbCheckAlarmStatusNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'check alarm status',
+  name: t('filters.index.checkAlarmStatus.name'),
   configurationDescriptor: {
     nodeDefinition: {
       icon: 'material-symbols:filter-list',
-      details:
-        'If the alarm status matches the specified one - msg is success if does not match - msg is failure.',
-      description: 'Checks alarm status.',
+      details: t('filters.index.checkAlarmStatus.details'),
+      description: t('filters.index.checkAlarmStatus.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.CHECK_EXISTENCE_FIELDS);
 
+const { t } = useI18n(); //加载国际化
 export interface CheckExistenceFieldsDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const CheckExistenceFieldsConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbCheckMessageNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'check existence fields',
+  name: t('filters.index.checkExistenceFields.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        "If selected checkbox 'Check that all selected keys are present'\" and all keys in message data and metadata are exist - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.\nElse if the checkbox is not selected, and at least one of the keys from data or metadata of the message exists - send Message via <b>True</b> chain, otherwise, <b>False</b> chain is used. ",
-      description: 'Checks the existence of the selected keys from message data and metadata.',
+      details: t('filters.index.checkExistenceFields.details'),
+      description: t('filters.index.checkExistenceFields.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,12 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.CHECK_RELATION);
 
+const { t } = useI18n(); //加载国际化
+
 export interface CheckRelationDataType {
   someConfiguration?: Recordable;
 }
@@ -13,13 +16,11 @@ export const CheckRelationConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbCheckRelationNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'check relation',
+  name: t('filters.index.checkRelation.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'If at least one relation exists - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.',
-      description:
-        "Checks the relation from the selected entity to the originator of the message by type and direction if 'Check for single entity' is set to true, otherwise rule node will check if exist any relation to the originator of the message by type and direction.",
+      details: t('filters.index.checkRelation.details'),
+      description: t('filters.index.checkRelation.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.GPS_GEOFENCING_FILTER);
 
+const { t } = useI18n(); //加载国际化
 export interface GpsGeofencingFilterDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const GpsGeofencingFilterConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.geo.TbGpsGeofencingFilterNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'gps geofencing filter',
+  name: t('filters.index.gpsGeofencingFilter.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        "Extracts latitude and longitude parameters from incoming message and returns 'True' if they are inside configured perimeters, 'False' otherwise.",
-      description: 'Filter incoming messages by GPS based geofencing',
+      details: t('filters.index.gpsGeofencingFilter.details'),
+      description: t('filters.index.gpsGeofencingFilter.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,12 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.MESSAGE_TYPE);
 
+const { t } = useI18n(); //加载国际化
+
 export interface MessageTypeDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +16,11 @@ export const MessageTypeConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbMsgTypeFilterNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'message type',
+  name: t('filters.index.messageType.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'If incoming MessageType is expected - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.',
-      description: 'Filter incoming messages by Message Type',
+      details: t('filters.index.messageType.details'),
+      description: t('filters.index.messageType.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.MESSAGE_TYPE_SWITCH);
 
+const { t } = useI18n(); //加载国际化
 export interface MessageTypeSwitchDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const MessageTypeSwitchConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbMsgTypeSwitchNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'message type switch',
+  name: t('filters.index.messageTypeSwitch.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'Sends messages with message types <b>"Post attributes", "Post telemetry", "RPC Request"</b> etc. via corresponding chain, otherwise <b>Other</b> chain is used.',
-      description: 'Route incoming messages by Message Type',
+      details: t('filters.index.messageTypeSwitch.details'),
+      description: t('filters.index.messageTypeSwitch.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: [

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.ORIGINATOR_TYPE);
 
+const { t } = useI18n(); //加载国际化
 export interface OriginatorTypeDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const OriginatorTypeConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbOriginatorTypeFilterNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'originator type',
+  name: t('filters.index.originatorType.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        'If Originator Type of incoming message is expected - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.',
-      description: 'Filter incoming messages by message Originator Type',
+      details: t('filters.index.originatorType.details'),
+      description: t('filters.index.originatorType.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.ORIGINATOR_TYPE_SWITCH);
 
+const { t } = useI18n(); //加载国际化
 export interface OriginatorTypeSwitchDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const OriginatorTypeSwitchConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbOriginatorTypeSwitchNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'originator type switch',
+  name: t('filters.index.originatorTypeSwitch.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        "Routes messages to chain according to the originator type ('Device', 'Asset', etc.).",
-      description: 'Route incoming messages by Message Originator Type',
+      details: t('filters.index.originatorTypeSwitch.details'),
+      description: t('filters.index.originatorTypeSwitch.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: [

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.SCENE_REACT);
 
+const { t } = useI18n(); //加载国际化
 export interface SceneReactDataType {
   someConfiguration?: Recordable;
 }
@@ -13,11 +15,11 @@ export const SceneReactConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.yunteng.scene.TbSceneReactNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'scene react',
+  name: t('filters.index.sceneReact.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details: '基于业务场景，实现设备的交互控制。',
-      description: '基于业务场景，实现设备的交互控制。',
+      details: t('filters.index.sceneReact.details'),
+      description: t('filters.index.sceneReact.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Message', 'Alarm Created', 'Alarm Updated', 'RPC Request', 'Failure'],

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.SCRIPT);
 
+const { t } = useI18n(); //加载国际化
 export interface ScriptDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const ScriptConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbJsFilterNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'script',
+  name: t('filters.index.script.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        "Evaluate incoming Message with configured JS condition. If <b>True</b> - send Message via <b>True</b> chain, otherwise <b>False</b> chain is used.Message payload can be accessed via <code>msg</code> property. For example <code>msg.temperature < 10;</code><br/>Message metadata can be accessed via <code>metadata</code> property. For example <code>metadata.customerName === 'John';</code><br/>Message type can be accessed via <code>msgType</code> property.",
-      description: 'Filter incoming messages using JS script',
+      details: t('filters.index.script.details'),
+      description: t('filters.index.script.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['True', 'False', 'Failure'],

@@ -2,9 +2,11 @@ import { FilterCategoryComponentEnum } 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(FilterCategoryComponentEnum.SWITCH);
 
+const { t } = useI18n(); //加载国际化
 export interface SwitchDataType {
   someConfiguration?: Recordable;
 }
@@ -13,12 +15,11 @@ export const SwitchConfig: NodeItemConfigType = {
   ...keys,
   clazz: 'org.thingsboard.rule.engine.filter.TbJsSwitchNode',
   categoryType: RuleNodeTypeEnum.FILTER,
-  name: 'switch',
+  name: t('filters.index.switch.name'),
   configurationDescriptor: {
     nodeDefinition: {
-      details:
-        "Node executes configured JS script. Script should return array of next Chain names where Message should be routed. If Array is empty - message not routed to next Node. Message payload can be accessed via <code>msg</code> property. For example <code>msg.temperature < 10;</code><br/>Message metadata can be accessed via <code>metadata</code> property. For example <code>metadata.customerName === 'John';</code><br/>Message type can be accessed via <code>msgType</code> property.",
-      description: 'Route incoming Message to one or multiple output chains',
+      details: t('filters.index.switch.details'),
+      description: t('filters.index.switch.description'),
       inEnabled: true,
       outEnabled: true,
       relationTypes: ['Failure'],