<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>3. Functions on JP1 Cloud Service/Operations Integration User&#39;s Guide</title>
    <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/index.html</link>
    <description>Recent content in 3. Functions 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/function/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>3.1 Basic window structure</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/basic/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/basic/index.html</guid>
      <description>This sections describes the basic window structure for the &amp;ldquo;Ops I&amp;rdquo; window and how to call items on the window.
(Figure) Basic window structure
&amp;#9312; Menu area
Select the various menu items to display the corresponding information in the contents area. &amp;#9313; Contents area
Displays information in accordance with the item selected in the menu area. &amp;#9314; Display icon
Several display icons are displayed in the window. Details are described.</description>
    </item>
    <item>
      <title>3.2 Tasks and Requests</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/task/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/task/index.html</guid>
      <description>&amp;ldquo;Tasks and Requests&amp;rdquo; is an application for finding all the functions necessary to respond to work requests and incidents as and when they occur.
It is used to request the execution of a task, to assign a user to a request, to execute a task and to check the status of a task that has been executed.
(Figure) Operational tasks within &amp;ldquo;Tasks and Requests&amp;rdquo; conceptual diagram
(Table) &amp;ldquo;Tasks and Requests&amp;rdquo; outline</description>
    </item>
    <item>
      <title>3.3 Knowledge</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/knowledge/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/knowledge/index.html</guid>
      <description>All users can take advantage of knowledge articles containing accumulated insights and expertise gained through the processes of failure response and inquiry handling.
You can categorize knowledge articles and rate those articles in terms of usefulness, so you can take advantage of those categories and rating scores when performing a search.
To create, edit, or delete knowledge articles or categories or to configure publishing options, you must use [FAQ] in the ITSM application.</description>
    </item>
    <item>
      <title>3.4 Documents</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/document/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/document/index.html</guid>
      <description>Documents is used for centralized management of attachment files for use in operational work.
(Figure) Documents conceptual diagram
Attachments are files that are attached to individual steps in a workflow, such as application forms for when a customer user makes an application from the service catalog when using the service, or reports summarizing the results of the execution of a service by the assigned agent for an operation.
These files are stored according to predefined file naming rules (Attachment) and distribution rules (Distribution).</description>
    </item>
    <item>
      <title>3.5 Datamodel</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/datamodel/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/datamodel/index.html</guid>
      <description>The Datamodel application allows you to view a list of data models registered in Ops I and to edit data (records) in those data models. It is also possible to import records from data models.
To use the Datamodel application, you must be assigned the Primitive role &amp;ldquo;custom_data_model_admin&amp;rdquo;. Access control for data models by group or customer is not supported. Users assigned the Primitive role &amp;ldquo;custom_data_model_admin&amp;rdquo; can access all datamodels available for display.</description>
    </item>
    <item>
      <title>3.6 System</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/system/index.html</guid>
      <description>This section describes the System Configuration tab, GitOps Log tab, and Import tab in the system application.
(1) System configuration tab The System Configuration tab is for managing users and organizations, and it is used for settings that are reflected throughout the entire system for the functions provided by Ops I.
The System Configuration tab window consists of Operation buttons (①), Selection buttons (②), the navigation area (③) and the configuration area (④).</description>
    </item>
    <item>
      <title>3.7 Git</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/index.html</guid>
      <description>This application does not support: functions other than the registration of files such as YAML files and image files, checking of differences when updating errors during registration, issuing of GitLab access tokens required to execute Git commands, creating of directories, using Container registry, or using Terraform states. Please do not attempt to use them. To register a YAML file, you must have a Git role with Maintainer or higher privileges in the group to which the target repository belongs.</description>
    </item>
    <item>
      <title>3.8 Secret management</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/secret/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/secret/index.html</guid>
      <description>In Ops I, users can safely manage credential information (for example, IDs and passwords required for accessing existing systems, public clouds, tools, and other operation targets) as secrets. By doing so, the operation agent will no longer need to manage multiple instances of credential information by using a ledger or anything else, thus reducing the risk of information leaks that might be caused as a result of loss or theft. Registered secrets are encrypted with AES-GCM using a 256-bit AES key and a 96-bit nonce and then saved.</description>
    </item>
    <item>
      <title>3.9 IT service management (ITSM)</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/itsm/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/itsm/index.html</guid>
      <description>This application provides a variety of functions, mainly for ticket management and customer management, in conjunction with OTOBO.
For details, see &amp;ldquo;JP1 Cloud Service/Operations Integration User&amp;rsquo;s Guide (ITSM Operation Manual)&amp;rdquo;.</description>
    </item>
    <item>
      <title>3.10 Automation</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/automation/index.html</guid>
      <description>The automation uses AWX, an OSS. Automation is an extension of the workflow, and by linking it with Playbook, it is possible to automatically execute jobs. The job execution results can also be confirmed.
Using the example of linking the Playbook called &amp;ldquo;Playbookβ.yaml&amp;rdquo; that is registered in the GitLab repository to AWX and executing it, the following section shows the procedure required in AWX.
Registering authentication information Setting projects Registering inventory Registering templates Checking job execution results To perform these registration and configuration operations, you must be a user with a role assigned by the AWX organization that matches each operation.</description>
    </item>
    <item>
      <title>3.11 Dashboard</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/dashboard/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/dashboard/index.html</guid>
      <description>This application allows you to visually display Ops I information using graphs and other visualizations. For example, it is useful for displaying tickets that require immediate action or unassigned tickets to understand the status, and for displaying the number of tickets and workflows in progress for each assignee to understand the workload. It also supports graphical display of user-created custom data models.
Users can create and view any dashboards. They can also view dashboards provided by Ops I.</description>
    </item>
  </channel>
</rss>