@things-factory/integration-base 6.1.141 → 6.1.145

package/helps/integration/task/log.ko.md

@@ -8,7 +8,8 @@
 - 메시지
   - 특정한 메시지를 로그로 남겨둘 필요가 있을 경우 사용하며 메시지의 로그가 유효하기 위해서는 접근자가 빈 상태로 있어야 한다.
   - 설정된 메시지는 로그의 내용에 남겨진다.
-  - [템플릿 리터럴](../concept/template-literal.md)이 적용되므로, data, variables, domain 등의 변수를 활용할 수 있다.
+  - [템플릿 리터럴](../concept/template-literal.md)이 적용되므로, data, variables, domain, user, lng 등의 변수를 활용할 수 있다.
+    - [스크립트 내장변수](../concept/script-internal-variables.md)
 - 접근자 [accessor](../concept/data-accessor.md)
   - 시나리오 내의 하나의 스텝이름으로, 해당 스텝의 결과 값을 출력하고자 할 경우에 접근자를 사용한다.
   - 이 접근자 결과는 로그에 남겨진다.

package/helps/integration/task/log.md

@@ -1,15 +1,16 @@
 # Log Task
 
-This feature is used to log changes in the value of a scenario's state for monitoring purposes. The generated logs are stored in the 'logs' folder of the application and are saved in log files starting with 'scenario-scenarioName'.
+The Log Task is used to output logs for monitoring changes in scenario states. These logs are stored in the application's "logs" folder and are saved in a log file that starts with "scenario-ScenarioName."
 
 ## Parameters
 
 - Message
-  - Used to leave a specific message as a log if necessary, and for the message log to be valid, the accessor must be empty.
-  - The configured message will be included in the log's content.
-  - [Template literals](../concept/template-literal.md) are applied, allowing the use of variables like data, variables, and domain.
+  - If you need to log a specific message, use this parameter. To make the message log effective, the accessor should be empty.
+  - The configured message will be recorded in the log.
+  - Since [template literals](../concept/template-literal.md) are applied, you can utilize variables such as data, variables, domain, user, lng, and more.
+    - [Script Built-in Variables](../concept/script-internal-variables.md)
 - Accessor [accessor](../concept/data-accessor.md)
-  - Represents the name of a step within the scenario; when you want to output the result value of that step, use this accessor.
+  - Use an accessor when you want to output the result value of a specific step within the scenario.
   - The result of this accessor will be recorded in the log.
 - Level
-  - Sets the level of the log message. The levels can be 'info', 'warn', or 'error'.
+  - You can set the log message level to 'info,' 'warn,' or 'error.'

package/helps/integration/task/log.ms.md

@@ -1,15 +1,17 @@
-## Tugasan Log
+# Tugas Log
 
-Fungsi ini digunakan untuk mencatat perubahan dalam nilai status sesuatu senario untuk tujuan pemantauan. Log yang dihasilkan disimpan dalam folder 'logs' aplikasi dan disimpan dalam fail log yang bermula dengan 'senario-namaSenario'.
+Tugas Log digunakan untuk menghasilkan log bagi memantau perubahan dalam keadaan senario. Log ini disimpan dalam folder "logs" aplikasi dan disimpan dalam fail log yang bermula dengan "scenario-ScenarioName."
 
 ## Parameter
 
 - Mesej
-  - Digunakan untuk meninggalkan mesej tertentu sebagai log jika perlu, dan untuk log mesej menjadi sah, accessor harus kosong.
-  - Mesej yang dikonfigurasi akan dimasukkan dalam kandungan log.
-  - [Literal templat](../concept/template-literal.md) digunakan, membenarkan penggunaan pemboleh ubah seperti data, variables, dan domain.
-- Accessor [accessor](../concept/data-accessor.md)
-  - Mewakili nama langkah dalam senario; apabila anda ingin mengeluarkan nilai hasil langkah tersebut, gunakan accessor ini.
-  - Hasil accessor ini akan direkodkan dalam log.
+  - Jika anda perlu mencatat mesej tertentu, gunakan parameter ini. Untuk membuat log mesej berkesan, aksesori harus kosong.
+  - Mesej yang dikonfigurasi akan direkodkan dalam log.
+  - Oleh kerana [literal templat](../concept/template-literal.md) digunakan, anda boleh menggunakan pembolehubah seperti data, pembolehubah, domain, pengguna, lng, dan lain-lain.
+    - [Pembolehubah Terbina Dalam Skrip](../concept/script-internal-variables.md)
+- Aksesori [accessor](../concept/data-accessor.md)
+  - Gunakan aksesori apabila anda ingin menghasilkan hasil nilai langkah tertentu dalam senario.
+  - Hasil aksesori ini akan direkodkan dalam log.
 - Tahap
-  - Menetapkan tahap mesej log. Tahap boleh menjadi 'info', 'warn', atau 'error'.
+
+  - Anda boleh menetapkan tahap mesej log kepada 'info,' 'warn,' atau 'error.'

package/helps/integration/task/log.zh.md

@@ -1,11 +1,16 @@
+# 记录任务
+
+记录任务用于输出日志，以监视场景状态的变化。这些日志存储在应用程序的“logs”文件夹中，并保存在以“scenario-ScenarioName”开头的日志文件中。
+
 ## 参数
 
 - 消息
-  - 如果需要，在日志中留下特定消息，以便记录消息的日志有效，访问器必须为空。
-  - 配置的消息将包含在日志的内容中。
-  - 应用[模板文字](../concept/template-literal.md)，允许使用变量如 data、variables 和 domain。
-- 访问器 [accessor](../concept/data-accessor.md)
-  - 表示场景内某个步骤的名称；当您希望输出该步骤的结果值时，请使用此访问器。
-  - 此访问器的结果将被记录在日志中。
+  - 如果需要记录特定消息，请使用此参数。为了使消息记录生效，访问者应为空。
+  - 配置的消息将记录在日志中。
+  - 由于应用了[模板文字](../concept/template-literal.md)，您可以利用诸如数据、变量、域、用户、lng 等变量。
+    - [脚本内置变量](../concept/script-internal-variables.md)
+- 访问者 [accessor](../concept/data-accessor.md)
+  - 当您希望输出场景内特定步骤的结果值时，请使用访问者。
+  - 此访问者的结果将记录在日志中。
 - 级别
-  - 设置日志消息的级别。级别可以是'info'、'warn'或'error'。
+  - 您可以将日志消息级别设置为“info”，“warn”或“error”。

package/helps/integration/task/script.ja.md

@@ -0,0 +1,37 @@
+# スクリプト
+
+これは JavaScript 構文で書かれたスクリプトを実行し、その結果を返すタスクです。
+
+## パラメータ
+
+- script
+  - JavaScript 構文で記述します。
+  - グローバルオブジェクトは、対応する[シナリオコンテキスト](../concept/scenario-context.md)からのデータと変数を含むシンプルなオブジェクトです。つまり、スクリプト内では、シナリオの[スクリプト内蔵変数](../concept/script-internal-variables.md)から特別な修飾子なしで、または`this`アクセサを介してデータ、変数、ドメイン、ユーザー、lng 変数を使用できます。
+  - タスクの実行結果は`return`構文を介して返されます。
+  - スクリプト内のグ
+
+ローバルオブジェクトはデータと変数、および他の[スクリプト内蔵変数](../concept/script-internal-variables.md)に制限されているため、システム関連の機能のほとんどは使用できないサンドボックス環境として考えてください。単純な操作を実装することをお勧めします。 - [Node Sandbox](https://medium.com/@devnullnor/a-secure-node-sandbox-f23b9fc9f2b0) - [vm2](https://github.com/patriksimek/vm2/blob/master/README.md)
+
+## サンプルスクリプト
+
+```
+return data['step1'].map(record => {
+  return {
+    ...record,
+    id: 'PREFIX-' + record.id
+  }
+})
+```
+
+```
+return Math.floor(Number(this.data['step2']))
+```
+
+```
+return this.data['step3'].map(record => {
+  return {
+    ...record,
+    id: (this.variables.prefix || 'DEFAULT-') + record.id
+  }
+})
+```

package/helps/integration/task/script.ko.md

@@ -0,0 +1,37 @@
+# Script
+
+Javascript Syntax로 작성된 script를 실행하여 그 결과를 리턴하는 태스크이다.
+
+## parameters
+
+- script
+  - javascript systax로 작성한다.
+  - global 오브젝트는 해당된 [Scenario Context](../concept/scenario-context.md)중 data 와 variables 를 가진 단순한 오브젝트이다. 즉, 스크립트 내에서 해당된 시나리오의 [스크립트 내장변수](../concept/script-internal-variables.md)인 data, variables, domain, user, lng 변수를 특별한 수식자없이 또는 this 접근자를 통해서 사용할 수 있다.
+  - 태스크의 수행 결과는 return 신택스를 통해서 반환된다.
+  - script 내에서는 global 오브젝트가 data와 variables 등 [스크립트 내장변수](../concept/script-internal-variables.md)로 한정되므로, 대부분의 시스템 관련된 기능은 사용할 수 없는 sandbox 환경이라고 이해하고, 단순한 연산정도의 기능을 구현하는 것을 권장한다.
+    - [Node Sandbox](https://medium.com/@devnullnor/a-secure-node-sandbox-f23b9fc9f2b0)
+    - [vm2](https://github.com/patriksimek/vm2/blob/master/README.md)
+
+## sample script
+
+```
+return data['step1'].map(record => {
+  return {
+    ...record,
+    id: 'PREFIX-' + record.id
+  }
+})
+```
+
+```
+return Math.floor(Number(this.data['step2']))
+```
+
+```
+return this.data['step3'].map(record => {
+  return {
+    ...record,
+    id: (this.variables.prefix || 'DEFAULT-') + record.id
+  }
+})
+```

package/helps/integration/task/script.md

@@ -1,20 +1,18 @@
 # Script
 
-Javascript Syntax로 작성된 script를 실행하여 그 결과를 리턴하는 태스크이다.
+This is a task that executes a script written in JavaScript syntax and returns the result.
 
-## parameters
+## Parameters
 
 - script
-  - javascript systax로 작성한다.
-  - global 오브젝트는 해당된 [Scenario Context](../concept/scenario-context.md)중 data 와 variables 를 가진 단순한 오브젝트이다. 즉, 스크립트 내에서 해당된 시나리오의 data 변수와 variables 변수를 특별한 수식자없이 또는 this 접근자를 통해서 사용할 수 있다.
-    - data : 시나리오 인스턴스 컨텍스트의 data 속성
-    - variables : 시나리오 인스턴스 컨텍스트의 시작 파라미터 속성
-  - 태스크의 수행 결과는 return 신택스를 통해서 반환된다.
-  - script 내에서는 global 오브젝트가 data와 variables로 한정되므로, 대부분의 시스템 관련된 기능은 사용할 수 없는 sandbox 환경이라고 이해하고, 단순한 연산정도의 기능을 구현하는 것을 권장한다.
+  - Write in JavaScript syntax.
+  - The global object is a simple object that contains data and variables from the corresponding [Scenario Context](../concept/scenario-context.md). In other words, within the script, you can use the data, variables, domain, user, and lng variables from the scenario's [Script Built-in Variables](../concept/script-internal-variables.md) without any special modifiers or through the `this` accessor.
+  - The task's execution result is returned through the `return` syntax.
+  - Since the global object within the script is limited to data and variables, as well as other [Script Built-in Variables](../concept/script-internal-variables.md), consider it a sandbox environment where most system-related functionalities are unavailable. It's recommended to implement simple operations.
     - [Node Sandbox](https://medium.com/@devnullnor/a-secure-node-sandbox-f23b9fc9f2b0)
     - [vm2](https://github.com/patriksimek/vm2/blob/master/README.md)
 
-## sample script
+## Sample Scripts
 
 ```
 return data['step1'].map(record => {

package/helps/integration/task/script.ms.md

@@ -0,0 +1,37 @@
+# Tugasan Skrip
+
+Ini adalah tugas yang menjalankan skrip yang ditulis dalam sintaks JavaScript dan mengembalikan hasil.
+
+## Parameter
+
+- skrip
+  - Ditulis dalam sintaks JavaScript.
+  - Objek global adalah objek sederhana yang mengandungi data dan pembolehubah dari [Konteks Senario](../concept/scenario-context.md) yang berkaitan. Dengan kata lain, dalam skrip ini, anda boleh menggunakan data, pembolehubah, domain, pengguna, dan pembolehubah lng dari [Pembolehubah Terbina Dalam Skrip](../concept/script-internal-variables.md) senario tanpa modifier khas atau melalui aksesori `this`.
+  - Hasil pelaksanaan tugas dikembalikan melalui sintaks `return`.
+  - Oleh kerana objek global dalam skrip terhad kepada data dan pembolehubah, serta Pembolehubah Terbina Dalam Skrip yang lain, pertimbangkan ia sebagai persekitaran sandbox di mana kebanyakan fungsi berkaitan sistem tidak tersedia. Disarankan untuk melaksanakan operasi yang ringkas.
+    - [Node Sandbox](https://medium.com/@devnullnor/a-secure-node-sandbox-f23b9fc9f2b0)
+    - [vm2](https://github.com/patriksimek/vm2/blob/master/README.md)
+
+## Skrip Contoh
+
+```
+return data['step1'].map(record => {
+  return {
+    ...record,
+    id: 'PREFIX-' + record.id
+  }
+})
+```
+
+```
+return Math.floor(Number(this.data['step2']))
+```
+
+```
+return this.data['step3'].map(record => {
+  return {
+    ...record,
+    id: (this.variables.prefix || 'DEFAULT-') + record.id
+  }
+})
+```

package/helps/integration/task/script.zh.md

@@ -0,0 +1,37 @@
+# 脚本
+
+这是一个执行 JavaScript 语法脚本并返回结果的任务。
+
+## 参数
+
+- 脚本
+  - 以 JavaScript 语法编写。
+  - 全局对象是一个简单的对象，包含来自相应[场景上下文](../concept/scenario-context.md)的数据和变量。换句话说，在脚本内部，您可以使用来自场景的[脚本内置变量](../concept/script-internal-variables.md)（例如 data、variables、domain、user 和 lng 变量）而无需任何特殊修饰符，或者通过`this`访问器。
+  - 任务的执行结果通过`return`语法返回。
+  - 由于脚本内的全局对象仅限于数据和变量以及其他[脚本内置变量](../concept/script-internal-variables.md)，请将其视为一个沙盒环境，在该环境中大多数与系统相关的功能不可用。建议实现简单的操作。
+    - [Node Sandbox](https://medium.com/@devnullnor/a-secure-node-sandbox-f23b9fc9f2b0)
+    - [vm2](https://github.com/patriksimek/vm2/blob/master/README.md)
+
+## 示例脚本
+
+```
+return data['step1'].map(record => {
+  return {
+    ...record,
+    id: 'PREFIX-' + record.id
+  }
+})
+```
+
+```
+return Math.floor(Number(this.data['step2']))
+```
+
+```
+return this.data['step3'].map(record => {
+  return {
+    ...record,
+    id: (this.variables.prefix || 'DEFAULT-') + record.id
+  }
+})
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@things-factory/integration-base",
-  "version": "6.1.141",
+  "version": "6.1.145",
   "main": "dist-server/index.js",
   "browser": "client/index.js",
   "things-factory": true,
@@ -26,12 +26,12 @@
   },
   "dependencies": {
     "@apollo/client": "^3.6.9",
-    "@things-factory/api": "^6.1.141",
-    "@things-factory/auth-base": "^6.1.141",
-    "@things-factory/env": "^6.1.141",
-    "@things-factory/oauth2-client": "^6.1.141",
-    "@things-factory/scheduler-client": "^6.1.141",
-    "@things-factory/shell": "^6.1.141",
+    "@things-factory/api": "^6.1.145",
+    "@things-factory/auth-base": "^6.1.145",
+    "@things-factory/env": "^6.1.145",
+    "@things-factory/oauth2-client": "^6.1.145",
+    "@things-factory/scheduler-client": "^6.1.145",
+    "@things-factory/shell": "^6.1.145",
     "async-mqtt": "^2.5.0",
     "chance": "^1.1.11",
     "cross-fetch": "^3.0.4",
@@ -46,5 +46,5 @@
   "devDependencies": {
     "@types/cron": "^2.0.1"
   },
-  "gitHead": "e3d3ba0a80acd94b85b4ee881c5e9374fc3ee04d"
+  "gitHead": "615af7d8a649cb70f13c13dfafdf6cb84db13b9b"
 }

package/server/engine/task/database-query.ts

@@ -3,7 +3,7 @@ import { ConnectionManager } from '../connection-manager'
 import { TaskRegistry } from '../task-registry'
 
 async function DatabaseQuery(step, context) {
-  var { domain, user, data, variables } = context
+  var { domain, user, data, variables, lng } = context
   var {
     connection: connectionName,
     params: { query }
@@ -15,6 +15,7 @@ async function DatabaseQuery(step, context) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }
@@ -36,4 +37,6 @@ DatabaseQuery.parameterSpec = [
   }
 ]
 
+DatabaseQuery.help = 'integration/task/database-query'
+
 TaskRegistry.registerTaskHandler('database-query', DatabaseQuery)

package/server/engine/task/graphql-mutate.ts

@@ -10,12 +10,13 @@ async function GraphqlMutate(step, context) {
   var { connection: connectionName, params: stepOptions } = step
   var { mutation, variables: variablesAccessorMap, headers } = stepOptions || {}
 
-  var { domain, user, data, variables } = context
+  var { domain, user, data, variables, lng } = context
 
   const vm = new VM({
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/graphql-query.ts

@@ -9,12 +9,13 @@ import { TaskRegistry } from '../task-registry'
 async function GraphqlQuery(step, context) {
   var { connection: connectionName, params: stepOptions } = step
   var { query, variables: variablesAccessorMap, headers } = stepOptions || {}
-  var { domain, user, data, variables } = context
+  var { domain, user, data, variables, lng } = context
 
   const vm = new VM({
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/http-get.ts

@@ -6,7 +6,7 @@ import { TaskRegistry } from '../task-registry'
 import { ConnectionManager } from '../connection-manager'
 import { substitute } from './utils/substitute'
 
-async function HttpGet(step, { logger, data, domain, user, variables }) {
+async function HttpGet(step, { logger, data, domain, user, variables, lng }) {
   var { connection: connectionName, params: stepOptions } = step
   var { headers: requestHeaders, searchParams = {}, path } = stepOptions || {}
   var connection = ConnectionManager.getConnectionInstanceByName(domain, connectionName)
@@ -21,6 +21,7 @@ async function HttpGet(step, { logger, data, domain, user, variables }) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/http-post.ts

@@ -6,7 +6,7 @@ import { TaskRegistry } from '../task-registry'
 import { ConnectionManager } from '../connection-manager'
 import https from 'https'
 
-async function HttpPost(step, { logger, data, domain, user, variables }) {
+async function HttpPost(step, { logger, data, domain, user, variables, lng }) {
   var { connection: connectionName, params: stepOptions } = step
   var { headers: requestHeaders, contentType, path, accessor } = stepOptions || {}
 
@@ -22,6 +22,7 @@ async function HttpPost(step, { logger, data, domain, user, variables }) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/local-graphql-mutate.ts

@@ -10,7 +10,7 @@ import { TaskRegistry } from '../task-registry'
 async function LocalGraphqlMutate(step, context) {
   var { params, updaterId } = step
   var { mutation, variables: variablesAccessorMap, headers } = params || {}
-  var { client, domain, user, data, variables } = context
+  var { client, domain, user, data, variables, lng } = context
 
   user =
     user ||
@@ -23,6 +23,7 @@ async function LocalGraphqlMutate(step, context) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/local-graphql-query.ts

@@ -10,7 +10,7 @@ import { TaskRegistry } from '../task-registry'
 async function LocalGraphqlQuery(step, context) {
   var { params, updaterId } = step
   var { query, variables: variablesAccessorMap, headers } = params || {}
-  var { client, domain, user, data, variables } = context
+  var { client, domain, user, data, variables, lng } = context
 
   user =
     user ||
@@ -23,6 +23,7 @@ async function LocalGraphqlQuery(step, context) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/log.ts

@@ -2,7 +2,7 @@ import { access, hasTemplateExpression } from '@things-factory/utils'
 import { VM } from 'vm2'
 import { TaskRegistry } from '../task-registry'
 
-async function Log(step, { logger, data, variables, domain, user }) {
+async function Log(step, { logger, data, variables, domain, user, lng }) {
   var {
     params: { message, accessor, level = 'info' }
   } = step
@@ -12,6 +12,7 @@ async function Log(step, { logger, data, variables, domain, user }) {
       sandbox: {
         domain,
         user,
+        lng,
         data,
         variables
       }

package/server/engine/task/oracle-procedure.ts

@@ -42,7 +42,7 @@ const DIR = {
 }
 
 async function OracleProcedure(step, context) {
-  var { domain, user, data, variables } = context
+  var { domain, user, data, variables, lng } = context
   var { connection: connectionName, params } = step
 
   var { code = '', parameters = [] } = params.parameters as ValueType
@@ -53,6 +53,7 @@ async function OracleProcedure(step, context) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/task/script.ts

@@ -6,7 +6,7 @@ async function Script(step, context) {
     params: { script }
   } = step
 
-  const { domain, user, data, variables, logger } = context
+  const { domain, user, data, variables, lng, logger } = context
 
   const vm = new NodeVM({
     timeout: 5000,
@@ -15,6 +15,7 @@ async function Script(step, context) {
     sandbox: {
       domain,
       user,
+      lng,
       data,
       variables
     }

package/server/engine/types.ts

@@ -13,6 +13,7 @@ export interface Connector {
 export type Context = {
   domain: Object
   user: Object
+  lng: string
   logger: any
   publish: Function
   load: Function

package/server/service/scenario-instance/scenario-instance-mutation.ts

@@ -71,7 +71,7 @@ export class ScenarioInstanceMutation {
     @Arg('variables', type => ScalarObject, { nullable: true }) variables: any,
     @Ctx() context: ResolverContext
   ): Promise<ScenarioInstance> {
-    const { domain, user } = context.state
+    const { domain, user, lng } = context.state
 
     debug('startScenario', instanceName, scenarioName, variables)
 
@@ -86,7 +86,7 @@ export class ScenarioInstanceMutation {
     }
 
     instanceName = instanceName || scenarioName
-    return await ScenarioEngine.load(instanceName, scenario, { domain, user, variables })
+    return await ScenarioEngine.load(instanceName, scenario, { domain, user, lng, variables })
   }
 
   @Mutation(returns => ScenarioInstance, { nullable: true, description: 'To start new scenario instance' })

package/server/service/scenario-instance/scenario-instance-type.ts

@@ -153,7 +153,7 @@ export class ScenarioInstance {
   }
 
   constructor(instanceName, { name: scenarioName, steps, domain: scenarioDomain }, context?) {
-    const { domain = scenarioDomain, user } = context || {}
+    const { domain = scenarioDomain, user, lng } = context || {}
 
     this.instanceName = instanceName
     this.scenarioName = scenarioName
@@ -165,6 +165,7 @@ export class ScenarioInstance {
     this.context = {
       domain,
       user,
+      lng,
       logger:
         context?.logger ||
         createLogger({