https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/index.html Recent content in 4.1 Prerequisite knowledge on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/func_relation/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/func_relation/index.html The associations between each function are shown in the figure below. (Figure) Associations between each function The knowledge required for each function is as follows. [Document management] (Table) Functions and prerequisite knowledge for document management Function name Outline Prerequisite knowledge Attachment Define distribution paths and naming rules for files attached through the UI. Dates, serial numbers, etc. can be added to folder names. YAML (GitLab) Distribution Attachments, trails, etc. can be assigned to per-customer repositories or fixed repositories can be designated. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/yaml_note/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/design_pre/yaml_note/index.html (1) Reflecting updates to YAML files to workflows Updates made to YAML files are not reflected in workflows that are being run. Updates to YAML files are reflected in workflows executed after the updates were made. (2) Restrictions on updates to YAML files The following table shows the column types of table definitions that can be updated in datamodel YAML files. (Table) Updatable column types Before update After update varchar varchar (larger), text For details on datamodel YAML definitions, see “Datamodel”.