<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>6. YAML Definition on JP1 Cloud Service/Operations Integration User&#39;s Guide</title>
    <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/index.html</link>
    <description>Recent content in 6. YAML Definition on JP1 Cloud Service/Operations Integration User&#39;s Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>6.1 Workflow</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_workflow/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_workflow/index.html</guid>
      <description>Workflow definitions and definition examples are provided below. Workflow definitions are categorized into two main parts: A part that defines the overall workflow and a part that defines the individual activities. For descriptions of workflows, see &amp;ldquo;Workflow&amp;rdquo; and &amp;ldquo;Designing a workflow&amp;rdquo;.
(Table) Workflow definition
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;workflow&#34;. type: No Specify &#34;resource&#34;. It indicates a new definition to be added to the operational function of Ops I.</description>
    </item>
    <item>
      <title>6.2 UI</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_ui/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_ui/index.html</guid>
      <description>This section provides UI definitions and example definitions. For a description of the UI, see &amp;ldquo;UI design&amp;rdquo;.
There are two versions of UI YAML definitions: UI version 1.0 and UI version 1.1. For differences between the two UI versions, see &amp;ldquo;UI version&amp;rdquo;.
YAML definitions for Uipath for defining the URLs of components are also described. For details on URL definitions, see &amp;ldquo;Uipath&amp;rdquo;.
Usable template definitions are also provided below. These template definitions can be used for UI version 1.</description>
    </item>
    <item>
      <title>6.3 Datamodel</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_datamodel/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_datamodel/index.html</guid>
      <description>Datamodel definitions and definition examples are shown below. For details of Datamodel, see &amp;ldquo;Designing a data model&amp;rdquo; and &amp;ldquo;Designing a workflow&amp;rdquo;.
(Table) Datamodel definitions
Label Default Value Required*1 Description apiVersion: Yes API Version
Specify 1.0. kind: Yes Specify &#34;datamodel&#34;. type: No Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Datamodel definition.
&#34;name&#34; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.4 Catalog</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_catalog/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_catalog/index.html</guid>
      <description>Catalog definitions and definition examples are shown below. For details of the service catalog, see &amp;ldquo;Service catalog&amp;rdquo; and &amp;ldquo;Designing a service catalog&amp;rdquo;.
(Table) Catalog definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &amp;quot;catalog&amp;quot;. type: No Specify &amp;quot;resource&amp;quot;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Catalog definition.
&amp;quot;name&amp;quot; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.5 Script</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_script/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_script/index.html</guid>
      <description>Script definitions and example definitions are shown below. For details of Script, see &amp;ldquo;UI design&amp;rdquo;.
Although the script version of the action defined in the Script YAML file must match the UI version of the UI, the Script will always be the following apiVersion1.0 YAML definition. For details of UI versions, see &amp;ldquo;UI version&amp;rdquo;.
(Table) Script definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;</description>
    </item>
    <item>
      <title>6.6 Library</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_library/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_library/index.html</guid>
      <description>Library definitions and definition examples are shown below. For details on Library, see &amp;ldquo;Library&amp;rdquo;.
(Table) Library definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;library&#34;. type: No Specify &#34;container&#34;.
It indicates that this is the definition for creating a container to store documents. name: Yes Internal name of the Library definition.
&#34;name&#34; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.7 Attachment</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_attachment/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_attachment/index.html</guid>
      <description>Attachment definitions and definition examples are shown below. For details on the Attachment, see &amp;ldquo;Storing documents&amp;rdquo;.
(Table) Attachment definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &amp;quot;attachment&amp;quot;. type: No Specify &#34;container&#34;.
It indicates that this is the definition for creating a container to store documents. name: Yes Internal name of the Attachment definition.
&#34;name&#34; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.8 Distribution</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_distribution/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_distribution/index.html</guid>
      <description>Distribution definitions and definition examples are shown below. For details on Distribution, see &amp;ldquo;Storing documents&amp;rdquo;.
(Table) Distribution definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;distribution&#34;. type: No Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Distribution definition.
&#34;name&#34; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.9 ACL, Statement</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_acl_statement/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_acl_statement/index.html</guid>
      <description>ACL and Statement definitions and definition examples are shown below. For details on ACL and Statement, see &amp;ldquo;Users and ACL&amp;rdquo;.
ACL YAML definitions are shown below.
(Table) ACL definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;acl&#34;. type: No Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the ACL definition.</description>
    </item>
    <item>
      <title>6.10 Notification, Notifier</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_notification_notifier/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_notification_notifier/index.html</guid>
      <description>Notification and Notifier definitions and definition examples are shown below. For details of Notification and Notifier, see &amp;ldquo;Designing notifications&amp;rdquo;.
The YAML definitions of Notification are as follows.
(Table) Notification definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;notification&#34;. type: No Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Notification definition.</description>
    </item>
    <item>
      <title>6.11 Application</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_application/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_application/index.html</guid>
      <description>Application definitions and definition examples are shown below. For details on Application, see &amp;ldquo;Application&amp;rdquo;.
(Table) Application definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;application&#34;. type: No Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Application definition.
&#34;name&#34; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.12 Skill, Skillset</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_skill_skillset/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_skill_skillset/index.html</guid>
      <description>Skill and Skillset definitions and example definitions are shown below. For details of Skill and Skillset, see &amp;ldquo;Skills required for operation&amp;rdquo; and &amp;ldquo;Skill management&amp;rdquo;.
The Skillset YAML definition is as follows.
(Table) Skillset definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;skillset&#34;. type: No Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Skillset definition.</description>
    </item>
    <item>
      <title>6.13 Calendar</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_calendar/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_calendar/index.html</guid>
      <description>Calendar definitions and definition examples are shown below. For details on Calendar, see &amp;ldquo;Calendar management functions&amp;rdquo; and &amp;ldquo;Schedule management&amp;rdquo;.
(Table) Calendar definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &#34;calendar&#34;. type: Yes Specify &#34;resource&#34;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Calendar definition.
&#34;name&#34; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
    <item>
      <title>6.14 Import</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_import/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/yaml/yaml_import/index.html</guid>
      <description>The Import definitions and their example are shown below. For details about Import, see &amp;ldquo;Importing custom table records&amp;rdquo;.
(Table) Import definitions
Label Default value Required* Description apiVersion: Yes API version
Specify 1.0. kind: Yes Specify &amp;quot;import&amp;quot;. type: No Specify &amp;quot;resource&amp;quot;.
It indicates a new definition to be added to the operational function of Ops I. name: Yes Internal name of the Catalog definition.
&amp;quot;name&amp;quot; should follow the conventions shown below: Specify the directory name of this YAML file.</description>
    </item>
  </channel>
</rss>