<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>4.5.3 Customizing the ticket window on JP1 Cloud Service/Operations Integration User&#39;s Guide</title>
    <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/index.html</link>
    <description>Recent content in 4.5.3 Customizing the ticket window 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/customer/tips/tips_ticketcustom/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>4.5.3.1 Ticket fields</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/field_custom/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/field_custom/index.html</guid>
      <description>The ticket fields can be customized as follows.
Adding fields Deleting fields Reflecting to filters Changing field names Setting up the ACL When changing ticket information on the Ops I Ticket window, information is exchanged with OTOBO via API. To add or delete &amp;ldquo;fields&amp;rdquo; to be displayed on the Ticket window, it is necessary to edit the configuration file for the API to be used. The API to be used is called &amp;ldquo;custom API&amp;rdquo; here.</description>
    </item>
    <item>
      <title>4.5.3.2 Ticket statuses</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/status_custom/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/status_custom/index.html</guid>
      <description>The ticket statuses can be customized as follows.
Changing status names Changing the initial status and transition order of statuses Adding and deleting statuses (1) Changing status names To change status names, edit the JavaScript file and JSON Schema file.
■JavaScript file
Change the status name enclosed in double quotation marks (&amp;quot;) in the following files.
(Table) Sections to edit in the JavaScript file
JavaScript file Location Description script/ticket-common/ticket_mapping_definition.js LABELSDISPLAY_STATUS ClientScript* *For details on ClientScript, see &#34;</description>
    </item>
    <item>
      <title>4.5.3.3 Ticket types</title>
      <link>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/type_custom/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/customer/tips/tips_ticketcustom/type_custom/index.html</guid>
      <description>You can customize the following for ticket types.
Changing ticket type names Adding and deleting types displayed on the ticket tab (1) Changing ticket type names When changing the type name, edit the JavaScript file, JSON Schema file, Application YAML file, and Uipath YAML file.
■JavaScript file
Change the type name enclosed in double quotation marks (&amp;quot;) in the following files.
(Table) Sections to edit in the JavaScript file</description>
    </item>
  </channel>
</rss>