Changes

Changes in (JCSM71-0290-01(E)) JP1 Cloud Service/Operations Integration 02-90

Additions and changes Location
Tickets can now be managed and Ops I definitions can be created and edited efficiently by linking with your AI agents. 4.11, 4.11.1
Added a feature to create and display any dashboards. 3.11, 3.11.2
Added the dashboard application to the menu area. 3.1
Added Iframe to the available UI components. 3.11.3, 6.2.2
Added the following dashboards to the dashboard application:
  • IT Operations Status
  • IT Operations Overview
 3.11
Added the datamodel application to enable operations on records in custom tables defined in the Datamodel YAML file and to reference records in custom views. 3.5, 3.5.1, 4.3.12, 6.3, 6.11
Added the Primitive role "custom_data_model_admin".
Users assigned this Primitive role can operate custom data models.		 3.5, 3.5.1, 4.3.12, 8.1
Added "Import" to the operational functions that can be specified in the YAML file. 3.5.2, 6, 6.14
Added "custom-data" to the resource types displayed in the "Import job list" window in the system application.
By default, the filter is set to display import jobs with resource types of "group", "role", and "customer".		 3.6 (3)
Added the Primitive role "resource_importer".
Users assigned this Primitive role can access the [Import] tab in the datamodel application and the following APIs:
  • GET /api/v1/import-jobs
  • POST /api/v1/import-jobs
  • GET /api/v1/import-jobs/{id}/errors
  • GET /api/v1/import-jobs/{id}
  • DELETE /api/v1/import-jobs/{id}
Also, this Primitive role is assigned to the following Pre-Installed roles:
  • System Administrator
  • Site Reliability Engineer
  • System Security Administrator
  • System Development Engineer
  • Operation Management Office Manager
  • Operation Management Office Agent
 3.5.2, 3.6 (3), 8.1, 8.2
Enabled the insertion and updating of records in custom tables through import operations. 1.4.2, 3.5, 3.5.2, 4.3.12 (2), 6.14
Changed the Primitive role required to use the [Import] tab of the system application as follows.
<Before change>
user_admin
<After change>
Both "user_admin" and "resource_importer"

Due to this change, if you are using Primitive roles or custom roles instead of Pre-Installed roles, you will need to review the roles you have assigned. If you are using the Primitive role "user_admin" to grant users the permission to use the [Import] tab of the system application, additionally assign the Primitive role "resource_importer". 		3.6 (3)
  • GET /api/v1/import-jobs
  • POST /api/v1/import-jobs
  • GET /api/v1/import-jobs/{id}/errors
Changed the Primitive role that has explicit permission for the above API as follows.
<Before change>
user_admin
<After change>
resource_importer

Due to this change, if you are using Primitive roles or custom roles instead of Pre-Installed roles, you will need to review the roles you have assigned. If you are using the Primitive role "user_admin" to grant users the explicit permission for the above API, additionally assign the Primitive role "resource_importer". 		8.2
Added the "parameters" label to the Catalog YAML file.
When creating a workflow from the service catalog, the parameters described in this label are used.		 4.3.1 (2), 6.4
Added OIWindow.getParams() to the action script.
This function allows you to retrieve parameters at workflow startup.		 4.3.1, 6.5.2
Added support for when notification object fields are added during Ops I version upgrades. 5.3
Added the workflow [Execution Log] window.
This change allows you to check the execution results and error details for the workflow and each task in the workflow when the workflow is executed.		 3.2.2 (4), 7.2.3
Added the "tooltip" label to "leftIcon" and "rightIcon" in the Table component. 6.2.2
Added the Icon component. 6.2.2
Changed the Pre-Installed roles that have access permissions to the "GitOps Log tab" window as follows.
<Before change>
  • Operation Management Office Manager
  • Operation Management Office Agent
  • System Operator
  • Service Desk Manager
  • Service Desk Agent
  • System Security Administrator
  • System Administrator
  • Site Reliability Engineer
  • System Development Engineer
<After change>
  • System Administrator
  • Site Reliability Engineer
  • System Development Engineer

Due to this change, users assigned Pre-Installed roles that have lost access rights will need to review their assigned roles. For users who want to continue having access rights to the "GitOps Log tab" window, assign the Pre-Installed roles listed after the change. 		8.1
Changed the Primitive role that has access permission to the "GitOps Log tab" window as follows.
<Before change>
  • dash_editor
  • dash_viewer
<After change>
  • gitops_logs_viewer

Due to this change, if you are using Primitive roles or custom roles instead of Pre-Installed roles, you will need to review the roles you have assigned. If you are using the Primitive role "dash_editor" or "dash_viewer" to grant users the permission for the "GitOps Log tab" window, assign the Primitive role "gitops_logs_viewer". 		8.1
Changed the Primitive role that has explicit permission for the API "GET /api/v1/gitops-logs" as follows.
<Before change>
system_config_admin
<After change>
gitops_logs_viewer

Due to this change, if you are using Primitive roles or custom roles instead of Pre-Installed roles, you will need to review the roles you have assigned. If you are using the Primitive role "system_config_admin" to grant users the explicit permission for the API "GET /api/v1/gitops-logs", assign the Primitive role "gitops_logs_viewer". 		8.2
Added the Primitive role "action_execution_viewer".
This Primitive role is required to access the [Execution Log] screen of workflows.
Also, this Primitive role is assigned to the following Pre-Installed roles:
  • System Administrator
  • Site Reliability Engineer
  • System Development Engineer
 8.1
Added the Primitive role "gitops_logs_viewer".
This Primitive role is required to access the "GitOps Log tab" window and the API "GET /api/v1/gitops-logs".
Also, this Primitive role is assigned to the following Pre-Installed roles:
  • System Administrator
  • Site Reliability Engineer
  • System Development Engineer
 8.1
The validation results for YAML files that can be checked by executing the API "gitops-logs" are now provided for all repositories, regardless of the group to which the user belongs. 3.6, 3.7.5
Added how to handle errors displayed in the [Execution Log] window of the workflow. 7.2.3
Specific columns can now be added to the "Workflow list" window.
The display names of columns can be changed, and the column values can be changed by adding fields in the "Workflow details" window. This function allows you to customize the display of the "Workflow list" window to suit your needs.
In addition, the "Workflow list" windows for both the request application and the task application can now be customized.
To perform customization, edit each YAML file.		 3.2.2 (1), 4.5.4
Added instructions on how to handle conflicts when upgrading Ops I with a customized workflow screen. 5.3, 5.3.1
Added the Primitive role "ticket_admin".
Users assigned this Primitive role can use APIs related to tickets, such as deleting tickets.
Also, this Primitive role is assigned to the Pre-Installed role "System Administrator".		 8.1, 8.2
Users assigned the Primitive role "ticket_admin" can now delete tickets in the "Ticket browser" window. 3.2.3, 4.3.8 (2)
Users assigned the Primitive role "ticket_admin" can now delete tickets in the "Ticket zoom" window. 3.2.3, 4.3.8 (2)
Users assigned the Primitive role "context_admin" can now delete workflows in the "Workflow list" window. 3.2.2
When the row selection state of a Table component is changed by "OITable.setSelectedIds", the change is now detected and the "handleSelectionModelChange" method configured for the same Table component is executed.
If "OITable.setSelectedIds" is executed within "handleSelectionModelChange", modify the process so that "OITable.setSelectedIds" is not called.		 5.3, 6.5.2
Added notifications from workflows, in addition to notifications by event.
Also, the following changes have been made to the description of notifications by existing events:
  • Deleted the description of follow-up notifications in cases where the request is not executed even after a certain amount of time has elapsed since the request.
  • Added an explanation of the triggers that cause notifications to be sent.
  • Added a note that schedules subject to notifications include schedules linked to users.
  • Added an explanation of the term "starting point".
  • Changed "(Figure) Example of notification in case of VM lending tasks".
  • Added an explanation of the code described in the definition example of "(Figure) Conceptual diagram of a YAML definition that sets the requester as the destination for notifications".
 4.3.3
Added object fields that can be used in "Notification".
  • workflow
    • parentContext
    • rootContext
    • label
    • currentSchedule
    • schedules. Any task name
    • description
    • category
    • dueDate
    • note1
    • note2
    • note3
  • user
    • displayName
  • customer
    • id
    • name
In addition, existing fields can now refer to different objects.
  • workflow
    • createdBy
    • customer
  • workitem
    • createdBy
    • updatedBy
    • workflowExecUser
If a task name that is the same as a field added to the workflow in "Notification" is specified, change it to schedules. Any task name.		 6.10
Added the notification component "oi.notify" so that notifications can be sent directly from workflows. 3.2.2, 4.3.3, 4.3.3.2, 6.1.1, 6.10
The sender email address used when sending notifications from Ops I has been changed from "noreply.opsi@itg.hitachi.co.jp" to "noreply@ops-integration.com". 1.4.1 (8), 4.3.8, 4.3.8.1, 5.3, 6.1, 6.10
Added the following as timings when email notifications are sent from Ops I:
  • The user password was initialized via the login window.
  • The Ops I notification function was used for ticket creation or update notifications.
 1.4.1 (8)
Changed the "User details" window on the System Configuration tab of the system application so that user profiles and related resources are edited and saved separately. With this change, the [Edit] button at the bottom of the screen has been changed to the [Edit Groups] and [Edit Roles] buttons. 3.6.1.1
Changed the "Group details" window on the System Configuration tab of the system application so that group information and related resources are edited and saved separately. With this change, the [Edit] button at the bottom of the screen has been changed to the [Edit Users], [Edit Groups], [Edit Roles], and [Edit Git Roles] buttons. 3.6.1.2
Changed the "Role details" window on the System Configuration tab of the system application so that role information and related resources are edited and saved individually. With this change, the [Edit] button has been changed to the [Edit Users], [Edit Groups], and [Edit Roles] buttons. 3.6.1.3
On the following screens under user management on the System Configuration tab of the system application, changed the data to be exported from all data (including pages that are not displayed) to only the data on the displayed page:
  • "User" window
  • "Group" window
  • "Role" window
Also, export page by page when exporting on the above screen. 		3.1
In the resources related to the "Add user" window and "User details" window on the System Configuration tab of the system application, changed the [Assign Group] dialog box and [Assign Role] dialog box to the table format.
With this change, while previously only the group name or role name was displayed, detailed information is now displayed and sorting and filtering can be performed.
Also, changed the method for changing the relation type of a related group from double-clicking on the tab of the related resource to editing in the [Relate Group] dialog box.		 3.6.1.1, 3.6.1.2
In the resources related to the "Add group" window and "Group details" window on the System Configuration tab of the system application, changed the [Assign User] dialog box, [Relate Group] dialog box, and [Assign Role] dialog box to the table format.
With this change, while previously only the user name, group name, or role name was displayed, detailed information is now displayed and sorting and filtering can be performed.		 3.6.1.2
In the "Add group" window and "Group details" window on the System Configuration tab of the system application, the Ops I user name and Git Role are now displayed in the information shown on the [Git Members] tab of the related resources.
In addition, Git roles can now be changed on the [Git Members] tab.		 3.6.1.2
In the resources related to the "Add role" window and "Role details" window on the System Configuration tab of the system application, changed the [Assign User] dialog box and [Assign Group] dialog box to the table format.
With this change, while previously only the user name or group name was displayed, detailed information is now displayed and sorting and filtering can be performed.		 3.6.1.3
Added support for the mode label in Form components and Table components that specify a table as the data source in YAML-defined UI (UI version 1.1).
With this change, while previously all data from the specified table was retrieved and displayed, by specifying "server" for the mode label, only the data to be displayed on the page can now be retrieved and displayed. This setting is recommend when you want to display a custom table that stores a large amount of data on the UI.		 6.2.2
Added a temporary limitation regarding the fact that the sort results of string items might appear different depending on the display format of the screen or table. 1.4.2
You can now create custom views that allow you to define tables for viewing by joining multiple custom tables.
You can now customize the data displayed in lookup dialogs on tables and forms displayed on workflows or custom applications.		 4.3.12
Added a note that the behavior of the following functions changes depending on the method used to retrieve data when displaying a table:
  • OITable.setRows
  • OITable.addRows
  • OITable.deleteRows
  • OITable.getRows
Also, added detailed explanations for the following functions:
  • OIForm.setEnumValues
  • OITable.setRows
  • OITable.addRows
  • OITable.deleteRows
  • OITable.getSelectedIds
  • OITable.setSelectedIds
  • OILabel.setContent
 6.5.2
Added information that can be retrieved with the getUserProfile() function. 4.4.1, 6.5.2
Changed the behavior so that a login error occurs during mapping at the time of single sign-on by the IdP in the following cases:
  • The customer to be assigned to the user does not exist.
  • The customer to be assigned is "invalid" or "invalid-temporarily".
This change can prevent unintended customer mapping.
Additionally, users who were able to log in before the version upgrade might encounter a login error after the version upgrade. In that case, check whether the customer to be assigned exists and is enabled, or review the customer mapping settings for user attributes. 		2.7.3
Made changes so that even if the customer settings for a user who created a workflow or ticket are changed, the customer for workflows or tickets already created by that user will not be changed.
This change prevents unintended disclosure of information to users.		 1.4.1 (4), 2.7.3 (4), 3.6.1, 3.6.2.2
For access control based on customer separation, added a combination of direct assignment of Primitive roles and assignment of custom roles as roles that must be assigned to customer users. 1.4.1 (4), 2.7.3, 3.6.1, 3.6.2.2
When displaying columns as chips in the Table component, changed the upper limit of the number of chips to display from 3 to unlimited. －
Fixed an issue where the leftmost column in the lookup dialog was displayed as a link-like format. －
Added apis to the dataSource of the YAML-defined UI (UI version 1.1) to enable the use of user:UserList and group:GroupList. With this change, you can now display user information or group information that can be retrieved via API in the lookup dialog. 4.4.3, 6.2.2
Added the "hide" label to the lookup field of the Form component in the YAML-defined UI (UI version 1.1). When "true" is specified for hide, the target column is initially displayed in a hidden state. 4.4.3, 6.2.2
For lookup fields in the Form component of YAML-defined UI (UI version 1.1), multiple items can now be displayed in a single column.
When multiple items are displayed in a single column with the default settings in the Table component, the delimiter is a comma (,) instead of a space.		 4.4.3, 6.2.2
Added items that can be displayed in the user table and group table provided by default. However, they can be referenced only if joined when defining a custom view in the Datamodel YAML file. 4.3.12, 6.3
Changed the supported browser versions.
<Before change>
  • Google Chrome 138 or later
  • Microsoft Edge 138 or later
<After change>
  • Google Chrome 145 or later
  • Microsoft Edge 145 or later
 2.2.1
Added information on Ops I v02-90 to the lifecycle of the AWX execution environment. 5.3.2
Added the following to the Linux distributions supported by the relay server:
  • RHEL: 9.7, 10.1
  • Oracle Linux: 9.7, 10.1
 2.5.1
Added Grafana (version: 12.3.1) to OSS.
The dashboard function is available based on Grafana.		 9.1
Upgraded GitLab to version 18.4.2.
The following changes have been made in accordance with this change:
  • Changed the URL of the referenced GitLab manual to "https://archives.docs.gitlab.com/18.4/".
  • Screen layout and display text of the GUI for the Git application (GitLab)
  • The following procedures:
    • Procedure for issuing a GitLab access token
    • Procedure for opening the GitLab Web IDE
 3.7.1, 3.7.2, 3.7.3, 9.1
Upgraded StackStorm to version 3.8.1.
With this change, changed the URL of the referenced manual to "https://docs.stackstorm.com/3.8/".		 9.1
Changed the OTOBO version to 11.0.13. 9.1
Upgraded MUI (Material-UI) to version 7.3.5.
With this change, changed the URL of the referenced manual to "https://v7.mui.com/material-ui/".		 9.1
With the upgrade of MUI (Material-UI), the Table component of UI version 1.0 now clears the row selection state when filter conditions are changed. 4.4.1
The following changes have been made to the display information operation icons that appear when there is information to be displayed in a list:
  • Changed [Show All] and [Hide All] in columns to [Show/Hide All].
  • Added [Reset] to columns.
  • Added [Remove all] to filters.
  • Removed restrictions on printing and [Document]-[Distribution]-[Distribution Rules], and changed the export behavior so that only the lines you checked are always output. Noted that even when there are no checkboxes for each row, only the selected rows are output.
 3.1
Changed the menu names and displayed menus of the site application. 4.3.10.1
Added a description of recovery measures when "Page not found" or "Not found" is displayed when implementing multilingual support for a site. 4.3.10.6
The following changes have been made to the table of OSS versions and editions and reference manuals:
  • Added a note of "No distinction between editions" to the editions of AWX and WordPress.
  • Deleted the note "Refer to this manual although this is different from the version used with Ops I." for the AWX version.
 9.1
The following SAML configuration items for identity providers are now unsupported:
  • Want AuthnRequests Signed
  • Signature Algorithm
  • SAML Signature Key Name
  • Want Assertions Encrypted
  • Encryption Algorithm
  • Sign Service Provider Metadata
 3.6.2
Added the following for the catalog item images in the service catalog.
  • Recommended image size for catalog items
  • Supported image file formats
 －
Changed the design of the "Catalog item list area" on the Service catalog tab window.
When displayed in tiles, 1 to 5 columns are displayed depending on the window size. Descriptions are displayed up to a maximum of 2 lines.
When displayed in lines, descriptions are displayed up to a maximum of 5 lines.		 －
Changed the following labels in YAML-defined UI (UI version 1.1):
  • Changed columns[].sortName to queryName in the Table component
  • Added lookup.columns[].queryName to the Form component
 4.5.3.1, 6.2.2
Changed the method for specifying filters and sorting for the API of the Table component when mode is "server" and source is "api".
<Before change>
columns[].column.read.data-source-name. The B part of A.B(The last part separated by periods)
<After change>
columns[].column.read.data-source-name. The A.B part of A.B(All after the data source name)

If the changed specification method cannot accommodate your needs, use columns[].queryName. 		6.2.2
Changed the schedule resource related to the workflow that is the target of the notification, when "time" is specified for type and "schedule" is specified for resource in Notification. If you specify "time" for type and "schedule" for resource and are monitoring schedules related to workflows, review the conditions.
<Before change>
"Schedules where the start date/time ("plannedStart") or end date/time ("plannedEnd") is set within one week (10,080 minutes) of the current time" or "Schedules for uncompleted workflows"
<After change>
"Schedules where the start date/time ("plannedStart") or end date/time ("plannedEnd") is set within one week (10,080 minutes) of the current time" or "Schedules for workflow steps where the start date/time ("plannedStart") or end date/time ("plannedEnd") is set within one week (10,080 minutes) of the current time" 		6.10
Access can now be controlled based on the values of dynamic fields added by users to tickets and their related resources. 4.5.3.1
Added A-Z as characters that can be entered as the first character of columns.enum in Datamodel YAML files. 6.3
Registration errors can now be detected when categories.items.workflow in Catalog YAML files is not configured. －
Fixed a bug where FAQ articles with a Symptom field in plain text that does not contain HTML tags were not reflected in the search results of AI extension function. －
For uuid/inet type columns, the filter operators "contains", "starts with", and "ends with" are no longer displayed in the Table component and the lookup dialogs with mode specified as "server". －
Made the following changes to the labels in the Form component:
  • Changed the required field of fields[].lookup.source and fields[].lookup.filter[][].operator/firstOperand/secondOperand from "Yes" to "No".
  • Added fields[].lookup.columns and fields.lookup.columns[].name/column/source/label/filterable/sortable/hide.
Also, added columns.hideable to the label of the Table component. 		6.2.2
Changed the default value of the icon label in the Application YAML file to blank and changed the required field to "Yes". 6.11
Changed the target of tickets that can navigate to related workflows from the "Workflow" tab of related records from incident tickets to all types of tickets. 3.2.3 (4)
Changed the output value of "workflow.customer" in "(Table) Object fields that can be used in Notification" from "Customer" to the more specific expression "Customer ID". 6.10
The manual description regarding user login has been changed as follows.
  • Changed the 25-hour login session retention period from "since the last operation" to "since login".
  • Partially changed the content to clarify that it might take up to 30 minutes for changes to a logged-in user's role, group, or customer to be reflected, and to prompt re-login if immediate reflection is required.
  • Changed the content to clarify that it might take up to 30 minutes to reflect changes to the role or group of users who issued an Ops I token, and to prompt users to reissue the Ops I token if immediate reflection is required.
 1.4.1
Noted for customer users that the user might be able to view or update records (such as tickets or workflows) that are not associated with their assigned customer, or might not be able to access records that are associated with them in the following cases:
  • If neither Pre-Installed role "Customer User" or "Customer Manager" is assigned nor the customer is configured.
  • If the appropriate Ops I role or customer is not applied to the user.
 1.4.1 (4), 2.7.3 (4), 3.6.1, 3.6.2.2
Changed the default value and description of the label related to the width size of the Grid and Form components. 6.2.2
Noted that workflow settings can be configured not only from the [Add Recurring Work Item] window but also from the [Add Single Work Item] window. 3.2.4.2
Added the working branch that is generated during backup. Also, regarding the tasks to be performed during the version upgrade, changed the name of the source branch to be merged. 5.3.1
Added that it is not necessary to specify the YAML file of the Workflow that defines the subflow in the "includes" label of the Workflow definition. 6.1
Added the maximum number of characters for the "Text" and "Textarea" type custom fields of tickets. 1.4.1 (7), 4.5.3.1 (1)
Added "sys_customer" and "ctx_id" to the columns provided by default, and changed the descriptions of "approved", "domain", and "group" to "Reserved Field". 6.3
Changed the GUI of the AI extension function as follows.
  • Changed "chat icon" to "Co-Operator icon".
  • Changed the [New Chat] button to the [New conversation] button.
 3.1.2
Added the procedure for registering authentication information for accessing credentials in Ops I. 3.10, 3.10.1, 3.10.4
Noted that notifications are sent to watchers who are customer users or requester users, even if the "Customer Visible" checkbox is not selected in Work Notes. 4.3.8.1 (2)
Added a description about "Uipath", "Library", "Application", "Calendar", and "Import" to "(Table) Operational functions that can be added in YAML files". In addition, the Notification description now includes notifications that are sent at any point in the workflow. 6
Added the number of lines that can be displayed in the description label of the YAML definition of Catalog. 6.4
Changed the descriptions of the following functions:
  • OIForm.setEnable
  • OIForm.setFieldEnable
Also, added the following functions:
  • OIForm.setReadOnly
  • OIForm.setFieldReadOnly
 6.5.2
The handleLoad function can now be used for actions that can be specified in the Table component of the UI definition. This change allows actions to be executed when the Table component is displayed. 6.5.2
Improved the description of conditions under which periods cannot be used in email addresses. 1.4.1 (7)
Added explanations of how to configure site notifications and destinations. 4.3.10.7
Added the following descriptions for "(Table) Notification definitions":
  • includes
  • event.resource
  • event.type
  • conditions[][].resource
 6.10
Added the definition example "Notifier (Work item deletion notification)". 6.10
Added explanations of the code described in the definition examples of use cases for notification conditions based on schedules and work items. 4.3.3.1
Added the following descriptions for "(Table) Notification definitions":
  • When the event type is "time" for conditions[][].resource
  • An example of specifying an array for notifications[].destinations[].notifiers
 6.10
Changed the following for "(Table) Notification definitions":
  • Added descriptions that the content notified in the GUI to property.to/subject/message can also be notified by email.
  • Improved descriptions of property.to/subject/message and property.conditions[][].resource.
  • Added descriptions for when sending to multiple destinations in "property.to".
 6.10
Modified the procedure for displaying the "system" group repository on the GitLab GUI. 4.9.1, 4.9.2.1, 4.10
Deleted the chapter about how to check YAML file registration information that was described in Chapter 4, and integrated it into "Checking registration status of YAML files" in Chapter 3. 3.7.5
Added "https://" to the URL set in "referTo" in the definition example of the Notification YAML file. 6.10
Add a description about the fields that serve as the information source for the phenomena in tickets and knowledge articles. 3.1.2
Divided the content of Chapter 4 "Designing a data model" into "Designing a service catalog" and "Designing a data model" for description. 4.3.1, 4.3.12
Added the maximum length of strings when "varchar" is specified as the column type. 6.3
Added the locations used when "document" is specified as the column type. 6.3
Added the following error messages regarding assignments in template strings:
  • An error occurred, and the System was unable to set up your account. Please contact your administrator. [Details] User email is in invalid format.
  • An error occurred, and the System was unable to set up your account. [Details] Failed to execute api get customer name by id.
 3.6.2.2
Added a description about the execution timing of the Form component action. 6.5.2
Added a description and usage example for "overrideFieldValues" specified in "options" of update/create/delete for OITableDataSource. 6.5.2
Improved a description about the display order by the "order" label for Application YAML files and Catalog YAML files. 4.3.1, 6.4, 6.11
Added a note that if uppercase email addresses are used in IdP, they must be converted to lowercase through mapping in the template. 2.7.3, 3.6.2 (5)
Added a description about "authn_info" available for mapping in identity provider template strings when the connection method is SAML. 3.6.2.2
Included precautions when searching with the AI extension function. 3.1.2
Added a note that "override" can be used when using it in Form or Table components that specify "client" for "mode". 6.2.2
Added a note that error page messages related to precautions for logging in and logging out of Ops I include "401 Unauthorized" and "500 Internal Server Error" in addition to "403 Forbidden". 1.4.1 (1)
Added a description of the Pre-Installed role "System Administrator" in "(Table) Relationship between Pre-Installed roles and supported functions". 8.1
Change the description from "external IdP" to "IdP" regarding IdP integration. General
Included precautions for when using branches or tags other than "main". 1.4.1 (9)
Included precautions on data to be registered when the tables[].columns[].index label in the Datamodel definition is "true". 6.3
Added a description of the content to be specified as the next activity to be executed for the workflow activity "next". 6.1
Added a description of "manifest". 6
Added a note that it is recommended to use "pat" for the authentication type "auth_type" used to log in to automation with "awx.run_job_template". 6.1.1
Added a note that for the YAML definition of Datamodel, when type is "enum", added options cannot be deleted. 1.4.2
Added an explanation about the response when the "Customer" designation and cancellation are repeated for the same user regarding the inheritance of OTOBO information of deleted users. 3.6.1.1 (5)
Added a description about the Ops I reserved user (user name "system") being displayed on the screen for selecting some users. 1.4.2
Added temporary restrictions about display settings such as "Rows per page" for the list screen on the "Organization management" window. 1.4.2

(Legend) -: N/A
Simple typos, omissions, and the like have been corrected without notice.