Changes
Changes in (JCSM71-0280-01(E)) JP1 Cloud Service/Operations Integration 02-80
| Additions and changes | Location |
|---|---|
The following were added to the Windows Server versions.
|
Introduction |
| The expression for characters that can be input was changed from "single-byte symbols" to "single-byte special characters". | 1.4.1, 3.5.2, 3.5.5, 6, 6.1, 6.3, 6.13 |
| Added a note that when a user's role or group is changed, it might take up to 30 minutes for the change to be reflected in the permissions of the Ops I token used for executing the API. | 1.4.1 (3) |
| Added "Affected Scope" to the allowable characters in the Ticket zoom window, and added "Affected Scope", "Implementation Plan", "Root Cause", "Workaround", and "Backout Plan" to the allowable characters in the Add new ticket window. | 1.4.1 (6) |
| Deleted the notes on editability for the [Type] field on the Ticket zoom window. | 1.4.1 (9) |
| Added a note that when changing a user's email address, an error might occur if an email address that was previously used is set. | 1.4.2 |
| Changed the versions of supported web browsers. | 2.2.1 |
| Added descriptions regarding encryption of communication between Ops I and the relay server, of communication between the relay server and the managed servers, and of the configuration items in the user settings file. | 2.5 |
Made the following changes to the prerequisites for RPM package installation:
|
2.5.1 (1) |
| Added a note that user-defined mapping takes precedence over automatic mapping. | 2.7.3 (3) |
| Added a note that when automatic mapping is performed and the customer ID corresponding to the user attribute "Customer" does not exist in Ops I, the customer information is overwritten with a blank value. | 2.7.3 (4) |
Made the following changes to the description of exporting:
|
3.1 |
| Added a function to search for tickets in the chat panel (Co-Operator chat panel), as well as to search for and create knowledge articles, and added descriptions of the configuration and operation of the chat panel. | 3.1, 3.1.2, 4.3.8 |
| Added a note that the Stepper component is used once the workflow execution stage reaches "Creation" or later. | 3.2.2 (3), 4.3.2 (1) |
| Added a "Create knowledge article" button to the Ticket zoom window. | 3.2.3, 4.3.11 |
| Deleted ticket ID from the input items for navigating directly by URL to the Ticket zoom tab. | 3.2.3 (1) |
| Changed the conditions under which the [Delete] button in the approval flow is enabled. | 3.2.3 (2) |
| Added a description of Source. | 3.2.3.2, 3.2.3.4 |
| Added a description of how to delete a schedule from the Workflow tab. | 3.2.4.3 (4) |
| Added the knowledge application and added operation descriptions for the Ops I GUI. | 3.3 |
| Added an Import tab that can import information on groups, roles, and customers. | 3.5 |
| Added a description of password encryption. | 3.5.1.1 (1) |
For the display items on the Add SAML window, changed the Required fields of the following items to Yes and added the following to the description.
|
3.5.2 (3) |
| Added a method of assigning values by template string to the types of identity provider mapping. | 3.5.2 (5) |
| Added a note that when searching SAML attribute names and friendly names, attribute names take precedence in the search results. | 3.5.2 (5) |
| Added descriptions of the notation rules and error messages when assigning values by template string to the types of identity provider mapping. | 3.5.2.2 |
| The validity period of the GitLab access token was changed from one year to unlimited. | 3.6.3 |
| Added a description of encryption of registered secrets. | 3.7 |
Added the knowledge function and added the following descriptions:
|
4.3, 4.3.11 |
| Added that the Stepper component is not supported in UI version 1.1. | 4.3.2 (1) |
| Regarding the Ops I notification function, the description of a function that can consolidate multiple notifications sent to the same recipient within 10 minutes into a single email was added. | 4.3.8.1 (1) |
| Added that if the operator who performed the event that triggered the ticket notification (such as creating a ticket or adding an article) is not a customer user, the operator will not receive a notification even if that operator is set as [Recipient]. | 4.3.8.1 (1) |
| Added a description of the function where, when a ticket is updated, the ticket approval request notification is sent again to the approver. | 4.3.8.3 |
| Deleted screen diagrams that duplicated the explanations and information in the text. | 4.3.10.1, 4.3.10.4, 4.3.10.6, 4.3.10.7, 4.3.10.8, 4.3.10.9 |
| Added Knowledge to the header of the template site for the Site application and described the URL for direct access. | 4.3.10.1 (3), 4.3.10.6 |
Added the following to the default contents of the Ops I Block for embedding Ops I windows in the Service Portal:
|
4.3.10.3 |
| Added a method for directly accessing the URL of an Ops I Block embedded in the Service Portal. | 4.3.10.3 |
| Changed the operation descriptions in line with the WordPress upgrade. | 4.3.10.3, 4.3.10.4, 4.3.10.6 |
When a template site is imported, the pages where the Ops I Block is placed are now supplemented with the following.
|
4.3.10.4 |
| Added a description of the conditions under which the checkbox for "The front page URL contains the language code instead of the page name or page id" is displayed. | 4.3.10.4 |
| Changed the description of data type conversion of checkboxes when customizing ticket fields, regarding the OTOBO format and Ops I format. | 4.5.3.1 |
Added the following settings for using customized ticket fields in object authorization ACLs.
|
4.5.3.1, 6.9 |
| Added that when adding a ticket field, the only UI YAML file that needs to be edited is the YAML file for the application to which the field is being added. | 4.5.3.1 (1) |
| Added a note that when adding ticket fields to the request application, the update property is not to be written in the UI YAML file. | 4.5.3.1 (1) |
| Added methods for checking AI extension function users and the number of job executions. | 5.1 |
| Added an explanation of the category settings for knowledge articles required when upgrading Ops I from v02-70 or earlier to v02-80 or later. | 5.3 |
| Changed the scope of maintaining customized functions required during Ops I upgrades, from ticket functions to Ops I functions. | 5.3, 5.3.1 |
| Added a warning that if conflicts occur in files edited for customizing ticket fields during an Ops I upgrade and are not resolved, there will be an impact. | 5.3.1 |
| Added procedures required when upgrading Ops I by two consecutive versions. | 5.3.1 |
| Added information on Ops I v02-80 to the lifecycle of the AWX execution environment. | 5.3.2 |
| Added procedures for checking the version of the execution environment of "OpsI Outpost EE". | 5.3.2 (1) |
Made the following changes to the description of YAML definitions:
|
Chapter 6 (throughout) |
| Added Statement and Notification to the YAML files where parameters can be used. Also added descriptions for when the authzType of the "resources.value" label is uri. | 6, 6.9, 6.10 |
| Changed the description of the "publish" attribute available in the "next" workflow activity. | 6.1 |
| Added the method for specifying lists under conditions of the filter in the lookup property of Form. | 6.2.1, 6.2.2 |
| Changed context.-type in the UI definition to context.type. | 6.2.2 |
Made the following additions, changes, and deletions to the properties of Table:
|
6.2.2 |
| Added a description stating that Attachment can only be used in workflows. | 6.2.2 |
| Added the Label component. | 6.2.2 |
Made the following additions and changes to the Datamodel definition.
|
6.3 |
| Added descriptions of the "customers" and "groups" labels in the YAML definition of the service catalog. | 6.4 |
| Added the column types that can be specified in Form but where the function "handleBlur" cannot be used. | 6.5.1 |
| Added Label to the list of execution timings for each component and function names. | 6.5.2 |
Made the following additions to the actions of action scripts (UI version 1.1):
|
6.5.2 |
Changed the classes that require instance creation to use, as follows:
|
6.5.2 |
| Deleted OIApiDataSource from the list of function names available when describing actions. | 6.5.2 |
| Changed the expression "context" in the operand description to "parameter". | 6.9 |
| Corrected the description of "type" from "container" to "resource". | 6.10 |
Added to the table of relationships between Pre-Installed roles and supported functions that the following Pre-Installed roles can only access the GitOps log window and cannot retrieve display data.
|
8.1 |
| Added knowledge articles and import to the table that maps roles with supported functions. | 8.1 |
| Changed the "user_admin" permission for the API "GET /groups/{id}" from explicitly allowed to implicitly denied, and changed the "user" permission from implicitly denied to explicitly allowed. | 8.2 |
| Changed the WordPress version to 6.8.2. | 9.1 |
| Since the validity period of the GitLab access token was changed from one year to unlimited, the note about the validity period was deleted. | 9.1 |
Made the following changes to the table of OSS versions installed in the container image of the execution environment.
|
9.1 |
(Legend) -: N/A
Simple typos, omissions, and the like have been corrected without notice.