npm - @fmsim/fmsim - Versions diffs - 0.0.99 → 1.0.0 - Mend

@fmsim/fmsim 0.0.99 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1185) hide show

package/dist-app/helps/about/things-factory.ko.md DELETED Viewed

@@ -1,258 +0,0 @@
-# about things factory
-Things-Factory는 데스크톱 및 모바일 그리고 엣지 디바이스 환경에서 구동되는 웹기반 어플리케이션을 개발하기위한 프레임워크입니다.
-Things-Factory 프레임워크는 수많은 NPM 패키지들로 구성된 모노리포 개발환경을 제공합니다.
-이 패키지들은 잘 조합되어 고성능의 자바스크립트 앱을 개발하는데 있어서 최신의 개발 및 테스트 환경을 제공합니다.
-이 패키지들은 자바스크립트 앱을 개발하기위한 최적의 계층적 구조를 구성하도록 개발되었습니다.
-Typescript를 포함하여, 서버사이들의 Koa, 웹컴포넌트 UI를 위한 LitElement, 클라이언트 서버간의 Graphql 통신을 위한 Apollo 그리고 테스트를 위한 Jest 등이 적용되었습니다. 이들을 잘 연결하고 조립하여 최고의 어플리케이션을 만들어보세요.
-- [Contents for modules](./modules.md)
-- [Contents for components](./components.md)
-- [Concepts for framework](./framework.md)
-## features
-- It is based on module structure.
-  - You can configure related feature sets for each module.
-  - It is removable by module.
-  - You can define dependencies between modules. Apply nodejs module dependency structure.
-  - [Things Factory Modules](./modules.md)
-  - [What modules does this application consist of ? (click here with holding ALT key.)](/dependencies)
-- Responsible Web App
-  - by Service Worker, Webpush notification, Manifest
-  - application layout for mobile
-- Help
-  - markdown based online help
-- Support Theme
-- Monorepo managed by lerna and yarn
-  - [things-factory github repository](https://github.com/hatiolab/things-factory)
-- Powerful Graphic UI design & viewing tools (board modules)
-- Redux pattern
-- Use i18next for internationalization
-- Simple datagrid
-  - responsible design
-- Packaging function uses webpack
-- The code set is based on es6,7,8, and transpiling with babel
-  - class-properties
-  - decorators
-  - object-rest-spread
-- Using Web Component-based DomElement - Defining custom element with LitElement
-- It is activated by linking with URL path and history in Single Page Application.
-- Each page is loaded at the time of initial activation. (lazy loading)
-- Zero Configuration function. It uses SSDP (Service Discovery Protocol) to automatically find services to be connected automatically and provide related functions. For example, it attempts to connect automatically by finding a server to connect to.
-- JWT based authentication (requires improvement to be supported by the server framework)
-- Oauth2 based extern interface
-  - as a Oauth2 Server
-  - as a Oauth2 Client
-- Free branding
-- Deploy
-  - [docker](http://docker.com) ready
-  - [kubernetes](http://kubernetes.io) ready
-## structural conventions
-- Redux
-  - The way to manage the overall state of an Application is using Redux pattern.
-  - The application, or base modules, can prepare points in the store that can be extended by a sub-module and provide an action.
-  - The sub-modules connect to the extension structure of the application or parent module using the action defined in the parent (base) module.
-- Page, Layout and Component
-  - Pages are activated by associating with the URL. (route)
-  - Layouts provide a framework for the layout and structure of the entire application UI elements.
-  - The components provide independent (atomic) functionality.
-    - The component excludes dependencies on the application in order to maintain implementation independence.
-      - Style maintains its independence by using css variables.
-      - Multilinguals maintain independence by using ox-i18n components. (Only have dependencies on ox-i18n.)
-      - The component does not have a premise for the layout (display, position) of the host (container) to which it will be used.
-  - page, layouts are connected to redux.
-  - Components do not connect to redux, but they work with pages through properties.
-- Base Module and extension (common) Modules (ex. provider, ui)
-  - The Base Module provides an abstract definition of special functions.
-  - The Base Module is said to provide functional services to the extension module.
-  - The extension module can add the base module as a dependent module and directly use the functions defined in the base module.
-  - Another way the extension module extends the Base Module is by using the reducer and action added to the store.
-  - The Base Module is a base module that reads a group of modules. For example, board-base module is a base module for all board functions. In addition, label-base module defines and implements functions related to the label, including barcode label pop-up, barcode label scanning, barcode label rendering and printing.
-  - The naming convention of base module for xxx module is 'xxx-base'.
-- Provider Module
-  - Sub-module that fills the data of Base module
-  - It mainly serves to fill the data defined in Base module from the external server.
-  - The naming convention for Provider module of xxx module is 'xxx-provider'.
-  - If it is necessary to be distinguished by the way data is provided, the naming convention for Provider module of xxx module using yyy method can be defined as 'xxx-provider-yyy'.
-- UI Module
-  - Sub-module responsible for the screen configuration related to Base module
-  - The naming convention for UI module of xxx module is 'xxx-ui'.
-  - If it is necessary to be distinguished by UI configuration method, the naming convention for UI module of xxx module using yyy method may be 'xxx-ui-yyy'.
-- Shell, Module and Application
-  - Shell provides all the structures that enable the module structure in the development and execution stages.
-    - redux, assets, routing
-    - build module, build application
-  - Module is only responsible for implementing its own purpose in the Shell base.
-  - Application is the final product that consists of the modules necessary for the purpose of Shell and the user.
-    - Configurations by Application
-      - Manifest file (brand-related - application name, logo image)
-      - Other brand related - homepage link, banner logo
-      - Style : Representative color table, other css variables
-      - Server connection IP
-      - Other source/resource override
-## Other coding conventions
-- Source file length recommended
-  - Each source file implements one of the most important purposes. (Be responsible for simple purposes rather than multiple purposes.)
-  - If there is no specific reason for each source file, it is recommended not to exceed 200 lines.
-- Naming
-  - class
-    - Class name : starts with uppercase, camel-case
-    - private property, method : starts with \_(underscore), camel-case
-    - public property, method : starts with lowercase, camel-case
-    - class property, method : starts with lowercase, camel-case
-    - Event handler : starts with on + EventName, camel-case
-- Localization
-  - Don’t capitalize explicitly in locale file
-```
-"field.system brief": "System Brief" (x)
-"field.system brief": "system brief" (o)
-```
-You can set it to style where you need it.
-```
-text-transform: capitalize;
-text-transform: uppercase;
-```
-- If possible, use ‘ms.json’ rather than ‘ms-My.json’. In particular, use ‘ms-My’ only if it is a Malay language that is used differently only in Malaysia.
-## authentication
-### things-factory/shell
-- Control the authentication process through auth base.
-  - Set authentication through auth base.
-- Provide auth action.
-  - You can change store through authentication related action.
-- Provide auth reducer.
-- That is, it sets through auth base and provides auth-related extension point.
-- In particular, auth base function is provided directly in things-factory shell.
-### things-factory/auth-ui
-- Provide the client side authentication process based on JSON webtoken.
-## prerequisites
-- Install Windows Subsystem for Linux on Windows (Windows)
-  - Install WSL using Ubuntu following https://docs.microsoft.com/en-gb/windows/wsl/install-win10
-- VS Code Extensions
-  - Prettier - Code formatter
-  - es6-string-css
-  - lit-html
-- VS Code Configuration
-  - Format on save: true
-- nodejs (v8.0.0 and above)
-- yarn
-- Chrome Browser Extension
-  - https://github.com/zalmoxisus/redux-devtools-extension
-- Node-gyp (For Ubuntu)
-  - npm install -g node-gyp
-- Python2 (For Ubuntu)
-  - sudo apt-get install python
-  - npm install --python=python2.7
-  - npm config set python python2.7
-- mdns (For Ubuntu)
-  - sudo apt-get install build-essential
-  - sudo apt-get install libavahi-compat-libdnssd-dev
-- node-printer (For Ubuntu)
-  - sudo apt-get install libcups2-dev
-## Usages
-The things-factory repo is managed as a monorepo that is composed of hundreds of npm packages.
-Each package has its own `README.md` and documentation describing usage.
-```
-# very first time
-$ yarn install
-$ yarn build # build all packages
-$ DEBUG=things-factory:*,typeorm:* yarn workspace @things-factory/operato-mms run migration
-$ DEBUG=things-factory:* yarn workspace @things-factory/operato-mms run serve:dev
-```
-```
-# after a new module package(ie. @things-factory/newbee) added
-$ yarn install # make newbee package join
-$ yarn workspace @things-factory/newbee build
-$ DEBUG=things-factory:* yarn workspace @things-factory/operato-mms run serve:dev
-```
-```
-# after a dependent package(ie. @things-factory/dependa) modified
-$ yarn workspace @things-factory/dependa build
-$ DEBUG=things-factory:* yarn workspace @things-factory/operato-mms run serve:dev
-```
-```
-# run application (ie. @things-factory/operato-mms) in production mode
-$ yarn workspace @things-factory/dependa build
-$ yarn workspace @things-factory/dependa build:client
-$ yarn workspace @things-factory/operato-mms run serve
-# The way to use the config file is the same as before.
-# Don't forget to give a config file to make the app run.
-```
-```
-# generate new application (ie. @things-factory/operato-xyz)
-$ yarn generate app
-  ? What should this application's name be? e.g. operato-abc > # type "operato-xyz"
-# generate new module (ie. @things-factory/notification)
-$ yarn generate module
-  ? What should this module's name be? e.g. menu > # type "notification"
-# generate new entity in a module (ie. "sms" entity in @things-factory/notification module)
-$ yarn generate entity
-  ? What is target package's name? e.g. biz-base, operato-mms > # type "notification"
-  ? What should this entitie's name be? e.g. company, company-ext > # type "sms"
-# generate new page in a module (ie. "sms-view" page in @things-factory/notification module)
-$ yarn generate page
-  ? What is target package's name? e.g. biz-base, operato-mms > # type "notification"
-  ? What should this pages's name be? e.g. abc-viewer > # type "sms-view"
-# generate new scene-module from scratch (ie. @things-factory/scene-random)
-$ yarn generate app
-  ? What should this module's name be? e.g. random > # type "scene-random"
-# generate new scene-component in a module (ie. "button" component in @things-factory/scene-switch module)
-$ yarn generate component
-  ? What is target package's name? e.g. switch > # type "switch"
-  ? What should this component's name be? e.g. button > # type "button"
-# generate new container component in a module (ie. "button" container component in @things-factory/scene-switch module)
-$ yarn generate container
-  ? What is target package's name? e.g. switch > # type "switch"
-  ? What should this component's name be? e.g. button > # type "button"
-# generate new html base scene component in a module (ie. "button" html-component in @things-factory/scene-switch module)
-$ yarn generate html-component
-  ? What is target package's name? e.g. switch > # type "switch"
-  ? What should this component's name be? e.g. button > # type "button"
-# generate new data source scene component in a module (ie. "button" component in @things-factory/scene-switch module)
-$ yarn generate data-source
-  ? What is target package's name? e.g. switch > # type "switch"
-  ? What should this component's name be? e.g. button > # type "button"
-# generate new data transform scene component in a module (ie. "button" component in @things-factory/scene-switch module)
-$ yarn generate data-transform
-  ? What is target package's name? e.g. switch > # type "switch"
-  ? What should this component's name be? e.g. button > # type "button"
-```
-## References
-- https://github.com/material-components/material-components-web-components

package/dist-app/helps/auth/appliance.en.md DELETED Viewed

@@ -1,22 +0,0 @@
-# Appliance
-![flowchart_appliance](./images/flowchart-appliance-registration.jpg)
-## <ins>Register appliances</ins>
-1.	You can register an appliance:
-- From the  appliance menu in the sidebar
-- On the Appliance Home page
-![register_appliance](./images/register-appliance.png)
-2.	Click REGISTER after entering the information on the appliance registration. The name value is required; other information is optional.
-![register_appliance](./images/register-appliance-new.png)
-## <ins>Update Appliance</ins>
-1.	Double click on the appliance name you want to update.
-2.	Enter all necessary information.
-3.	Click **Update**
-## <ins>Delete Appliance</ins>
-1.	Double click on the appliance name you want to delete.
-2.	Click **Delete This Appliance**

package/dist-app/helps/auth/appliance.ko.md DELETED Viewed

@@ -1,40 +0,0 @@
-# 어플라이언스
-외부 단말장치에서 API를 통해서 시스템을 사용하는 경우에 사용자가 로그인 프로세스를 진행하기 어려운 경우가 많은데, 이 경우에는 어플라이언스(단말장치) 유저를 등록하고 장기 사용 가능한 액세스토큰을 생성해서 인증을 진행하면 편리하다.
-![flowchart_appliance](./images/flowchart-appliance-registration.jpg)
-## <ins>어플라이언스(단말장치) 등록하기</ins>
-1. 다음과 같이 단말장치를 등록할 수 있다:
-- 사이드바의 '단말장치' 메뉴를 실행하면 단말장치 등록 화면을 볼 수 있다.
-  ![register_appliance](./images/register-appliance.png)
-2. 기본 정보를 입력하고 'register' 버튼을 클릭한다.
-   ![register_appliance](./images/register-appliance-new.png)
-## <ins>어플라이언스(단말장치) 정보 갱신</ins>
-1. 단말장치 이름을 클릭하여 단말장치 정보화면으로 이동
-2. 관련 정보를 수정한 뒤
-3. **Update** 버튼을 클릭
-## <ins>어플라이언스(단말장치) 정보 삭제</ins>
-1. 단말장치 이름을 클릭하여 단말장치 정보화면으로 이동
-2. **Delete This Appliance** 버튼을 클릭
-## <ins>어플라이언스(단말장치) 테스트</ins>
-단말장치는 사용자 타입중 한가지로 이해될 수 있다. 단말장치가 생성되면 일반 사용자와 같이 역할을 부여하고 원하는 정보에 접근할 수 있다.
-일반 사용자는 로그인 화면을 통해서 인증 절차를 거치지만, 단말장치는 그런 과정을 거치기 어렵기 때문에, 단말장치에서 API 호출시 인증 정보에 포함할 수 있도록 액세스토큰을 생성해서 사용한다.
-1. 단말장치 액세스토큰 생성하기
-   'Generate New Access Token' 버튼을 클릭해서 Access Token을 생성한다.
-   ![generate_key](./images/appliance-generate-key.png)
-2. 'API 샌드박스'에서 사용자 API를 시험하기 이전에 Authorize 버튼을 누르고 Bearer에 위에서 생성한 액세스토큰을 복사한 후 Authorize 버튼을 눌러서 Login한다.
-   ![appliance-sandbox-auth-1](./images/appliance-sandbox-auth-1.png)
-   ![appliance-sandbox-auth-2](./images/appliance-sandbox-auth-2.png)
-3. 시나리오 실행(start-scenario)을 수행해 보면, 다음과 같이 헤더에 Authorization 항목이 추가된 것을 확인하실 수 있다. 실제로, 단말장치로부터 API 호출을 구현할 때, 같은 방법으로 API를 호출하면 인증을 해결할 수 있다.
-   ![appliance-sandbox-auth-3](./images/appliance-sandbox-auth-3.png)

package/dist-app/helps/auth/application.en.md DELETED Viewed

@@ -1,33 +0,0 @@
-# Applications
-This page allows third party applications to integrate with Operato by registering the application in Operato HUB.
-## <ins>Register Application</ins>
-Register an application
-1.	You can register an application:
-- From the Applications menu in the sidebar
-- On the Applications page
-![register_application](./images/register-application.png)
-2.	Enter all necessary information.
-3.	Click Register New Application.
-## <ins>How to use application</ins>
-![application_hub](./images/application-hub.png)
-4.	Enter http://localhost:3000 in the Application URL section and http://localhost:3000/callback-operato in the Redirect URL section.
-5.	Copy the Auth URL, Access Token URL, AppKey, AppSecret one by one and paste them into the Postman application.
-## <ins>One-time setup of Postman application</ins>
-6.	Click the + New button in the top left corner.
-![postman](./images/postman.png)
-7.	Click Request
-8.	Enter the request name and select a collection.
-Authorize URL
-9.	Select OAuth 2.0 in the type section
-10.	Paste the copied URL and credentials in step 5 into the Auth URL, Access Token URL, Client ID, and Client Secret.
-![authorization_postman](./images/authorization-postman.png)
-11. Click Get New Access Token and the image below will be displayed.
-![app_binding](./images/app-binding.png)
-12.	Click one of the roles you want to assign and click ALLOW to connect Operato with a third party application. Click DENY to abort the operation.

package/dist-app/helps/auth/images/app-binding.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/appliance-generate-key.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/appliance-sandbox-auth-1.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/appliance-sandbox-auth-2.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/appliance-sandbox-auth-3.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/application-hub.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/authorization-postman.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/create-button2.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/create-role.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/flowchart-appliance-registration.jpg DELETED Viewed

Binary file

package/dist-app/helps/auth/images/flowchart-role-management.jpg DELETED Viewed

Binary file

package/dist-app/helps/auth/images/flowchart-user-account.jpg DELETED Viewed

Binary file

package/dist-app/helps/auth/images/invite-user.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/owner-transfer-confirm.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/owner-transfer.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/postman.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/register-appliance-new.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/register-appliance.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/register-application.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/registered-role.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/role-list.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/role-privilage.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/role-privileges.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/save-button2.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/save-button3.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/transfer-owner.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/update-roles.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/user-delete.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/user-error.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/user-invite.png DELETED Viewed

Binary file

package/dist-app/helps/auth/images/user-roles.png DELETED Viewed

Binary file

package/dist-app/helps/auth/roles.en.md DELETED Viewed

@@ -1,59 +0,0 @@
-# Roles
-![flowchart_role_management](./images/flowchart-role-management.jpg)
-Operato has roles for users’ access rights. Each role confers a different set of privileges for a given user of Operato. For example, users who have **Admin** rights can restrict other users’ access rights so that they cannot view or modify internal information.
-### Properties
-- **Roles**: job (title) or role name
-- **Privileges**: privileges to access the system
-### Role List
-You can search the roles registered by domain.
-![registered_role](./images/registered-role.png)
-### Type of Roles
-1. Main role
-- It has privilege to access Operato.
-| ROLES             | PRIVILEGE                                                                                                                                                   |
-| :---------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Admin             | Can invite users to Operato Hub, have full privilege in WMS                                                                                                 |
-| Customer          | Can create Goods Arrival Notice (GAN) and Release Order (RO), and view reports                                                                              |
-| Office admin      | Can receive or approve the request of Goods Arrival Notice (GAN), Release Order (RO), activate worksheets and generate reports in Operato WMS for customers |
-| Warehouse manager | Execute unloading, putaway, returning, picking, batch picking and loading                                                                                   |
-| Warehouse staff   | Execute unloading, putaway, returning, picking, batch picking and loading                                                                                   |
----
-2. Shared role
-- It is used to assign menus in the Operato WMS.
-## <ins>Create Role</ins>
-**Admins** can add any role they want.
-![create_role](./images/create-role.png)
-1. Enter the name and description according to the form format.
-2. Click ![create_button](./images/create-button2.png)
-## <ins>Update Role</ins>
-Click on a role name to edit the role's name, description and privileges.
-### Role Privilages
-Below the role name, a list of access rights for functions is displayed. After checking the desired authority, click ![save_button](./images/save-button2.png)
-![role_privilage](./images/role-privilage.png)
-You can grant roles to users in a bizplace through the **User Management** menu which is accessible through the **Users** tab in the sidebar.
-## <ins>Delete Role</ins>
-You can delete unused roles. Please note that if a partner is using a role, it cannot be deleted.

package/dist-app/helps/auth/roles.ko.md DELETED Viewed

@@ -1,42 +0,0 @@
-# roles
-operato는 사용자들의 접근 권한을 위한 역할들이 존재합니다. 각각의 역할에 따라 operato system을 사용하는 기능들에 대한 접근 권한을 둘 수 있습니다.<br>
-예를 들어, 관리자 권한이 없는 일반 사용자의 경우 내부 정보를 조회하거나 수정할 수 없도록 읽기, 편집 등의 접근 권한을 제한할 수 있습니다.<br>
-## porperties
-- **roles**
-  : 직업(직책)이나 역할 이름
-- **privileges**
-  : 시스템에 접근할 수 있는 권한
-## role list
-도메인별로 등록된 role을 조회할 수 있습니다.<br>
-![role_list](./images/role-list.png)
-<br>
-## create role
-관리자는 원하는 role을 추가할 수 있습니다.<br>
-![create_role](./images/create-role.png)
-form 형식에 맞게 name, description을 입력 후 'create' 버튼을 클릭하여 생성합니다.<br>
-(role의 privileges는 role을 추가한 후 추가된 role을 클릭하여 수정할 수 있습니다.)
-## update role
-role 이름을 클릭하면 해당 role의 이름, 설명과 privileges를 수정할 수 있습니다.
-### role privileges
-role name아래에는 기능들에 대한 접근 권한 리스트가 보여지며, 원하는 권한을 체크한 후 'save'버튼을 클릭하여 저장합니다.
-![role_privileges](./images/role-privileges.png)
-_<u>사용자에게 role을 부여하려면 user 관리 메뉴에서 도메인에 속한 사용자들의 role을 설정할 수 있습니다.</u>_
-## delete role
-사용하지 않는 role을 삭제할 수 있습니다.<br>
-<u>\* partner에서 role을 사용하고 있을 경우 삭제가 되지 않습니다.</u>

package/dist-app/helps/auth/users.en.md DELETED Viewed

@@ -1,33 +0,0 @@
-# Users
-![user_account](./images/flowchart-user-account.jpg)
-All users in your business are displayed on the **User Management** screen. You can invite users to a bizplace, edit roles, or remove users.
-There are three types of users: general user, application, and appliance.
-## <ins>Invite users to your bizplace</ins>
-You can invite registered users by entering their email address.
-1.	Enter the email address of the user in the box as shown below.
-2.	Click **INVITE USER**. You can assign a role to each user you invite to your bizplace.
-![invite_user](./images/invite-user.png)
-## <ins>Update roles</ins>
-Click on a user to see the roles they have been assigned. Click in the check box next to each role to assign or remove that role, then press ![save_button](./images/save-button3.png)
-![update_roles](./images/update-roles.png)
-## <ins>Delete User</ins>
-To remove a user from a bizplace, select the user then click **DELETE USER**. You can delete all users except the owner. Note that this does not delete a user’s account, just their access to this bizplace.
-![delete_roles](./images/update-roles.png)
-## <ins>Transfer Owner</ins>
-If you are the owner of the bizplace you have the option to select another user to become the owner.
-1. Click the user you want to designate as the owner of the domain. ![transfer_owner](./images/update-roles.png)
-2.	Click **TRANSFER OWNER**. ![transfer_owner](./images/transfer-owner.png)
-3. Enter the email address of the user you wish to transfer ownership to.
-4. Click **CONFIRM**. Note that changing the owner may limit the functions that the current user can access.
-## <ins>ERROR MESSAGE</ins>
-| ERROR MESSAGE | EXPLANATION |
-| :------------:| :----------:|
-| ![user_error](./images/user-error.png) ! Failed to find user | Users must have previously registered their email address in Operato.|
-|

package/dist-app/helps/auth/users.ko.md DELETED Viewed

@@ -1,54 +0,0 @@
-# users
-각 도메인에 소속된 사용자들을 보여줍니다. 사용자를 도메인에 초대할 수 있으며, 등록된 사용자에 대해 role을 편집하거나 사용자를 삭제할 수 있습니다.<br>
-users는 일반 사용자(user)와 application, appliance 세 가지의 타입이 존재합니다.<br>
-## porperties
-- **users**
-  : 사용자 정보(이름, 이메일 등) 조회
-- **roles**
-  : 사용자가 소속된 도메인별로 부여할 수 있는 역할(직책)
-## Invite Users
-사용자를 추가하는 기능입니다. 가입된 사용자의 이메일을 입력하여 초대할 수 있습니다.<br><br>
-![invite_user_image](./images/user-invite.png)
-초대하려는 사용자의 이메일을 입력한 후 'invite user' 버튼을 클릭합니다.
-초대된 사용자는 해당 도메인에 대한 role을 지정할 수 있습니다.
-## Update Roles
-update roles는 해당 도메인에 접근할 수 있는 역할을 설정하는 기능입니다.
-역할마다 서로 다른 권한이 존재합니다.
-![user_roles_image](./images/user-roles.png)
-파트너쉽에 의해 부여받은 역할 또한 설정할 수 있습니다.
-유저에 맞게 roles을 부여한 후 'save'버튼을 클릭하여 수정사항을 저장합니다.
-## Delete User
-사용자를 삭제하는 기능입니다. <br>
-![delete_user_image](./images/user-delete.png)
-더이상 사용하지 않는 user를 'Delete User' 버튼을 클릭하여 삭제합니다. owner를 제외한 모든 사용자를 삭제할 수 있습니다.<br>
-도메인에 접근할 수 있는 사용자를 제거하는 기능이며, 사용자가 영구적으로 삭제되는 것은 아닙니다.
-## Transfer User
-해당 도메인의 owner를 변경하는 기능입니다.<br> \*_현재 user 타입의 사용자가 도메인의 owner인 경우에만 나타나는 기능입니다._<br>
-![transfer_owner_image_1](./images/owner-transfer.png)
-도메인의 owner로 지정하고 싶은 사용자를 클릭하면 'transfer owner' 버튼이 나타납니다.<br>
-![transfer_owner_image_2](./images/owner-transfer-confirm.png)
-transfer owner 버튼을 클릭하면 변경하려는 사용자의 이메일을 확인하기 위한 팝업이 나타납니다.<br>
-비즈니스 계정의 소유자로 변경하고자 하는 사용자의 이메일을 정확히 입력한 후 'confirm' 버튼을 클릭합니다.<br>
-\*_owner를 변경하면 현재 유저가 접근할 수 있는 기능이 제한될 수 있습니다._
-## Update Apps
-도메인에 등록된(appKey를 가진) 모든 application, appliance (apps) 리스트를 조회할 수 있습니다.<br>
-app을 사용할 땐, 활성화(activate)하고 사용하지 않을 경우엔 비활성화(deactivate)를 선택합니다.<br>

package/dist-app/helps/board-modeller/accessor.ko.md DELETED Viewed

@@ -1,4 +0,0 @@
-# 접근자 (accessor)
-- 소스 컴포넌트의 data 객체 중에서, 일부분만 전파하거나 변환된 데이타를 전파하고자 하는 경우에 설정한다.
-- 설정 방법은 [JSONATA 도큐먼트](http://docs.jsonata.org/overview.html)를 따른다.

package/dist-app/helps/board-modeller/accessor.md DELETED Viewed

@@ -1,4 +0,0 @@
-# Accessor
-- Set when you want to propagate only a part of the data object of the source component or the transformed data.
-- The setting method follows [JSONATA document](http://docs.jsonata.org/overview.html).

package/dist-app/helps/board-modeller/accessor.zh.md DELETED Viewed

@@ -1,4 +0,0 @@
-# Data Binding
-- 它是根据源组件的数据值更改目标组件的属性的设置。
-- 设置方法遵循[JSONATA 文档](http://docs.jsonata.org/overview.html)。