1.4.2 Temporary restrictions

(1) Temporary restrictions

The following functions are subject to temporary restrictions.

(Table) List of temporary restrictions

# Category Restriction When the restriction will be lifted
1 Task development with YAML definitions
 Document distribution rule definitions that store repositories and directories on a per-service basis are not supported. TBD
For the name on the distribution rule list, the value specified for [rules/name] is displayed rather than the name specified for [rules/label]. TBD
ACLs should be assigned to roles, not directly to users or groups. TBD
The file path of the YAML file (manifest.yaml) cannot be changed. If you want to move the file, use the following procedure to re-register it.
1. Delete all YAML files that have dependencies on the YAML file that you want to move by following the steps below.
① Find YAML files in which the YAML file that you want to move is specified as an Include target.
② Find YAML files in which the YAML files found in Step ① are specified as Include targets.
③ Repeat Step ② against the YAML files found in Step ② until there are no more such YAML files.
④ Staring from the last YAML files found, remove other YAML files from Include targets, in the reverse order of when they were found.
2. Delete the document that you want to move.
3. Change the path of the document to register that you want to move and re-register it.
4. Re-register the document deleted in Step 1.
TBD
If "selection" is not specified for the property of "table" in the YAML definition of the UI, a checkbox will appear. TBD
If a YAML syntax error occurs for a target of a "gitops-logs" API operation, the "name" and "kind" fields of that gitops will not be stored in gitops-logs. For this reason, gitops-logs for which a YAML syntax error has occurred cannot be searched for s using query parameters, or the combination of the "name" and "kind". TBD
The return value of OIData.updateCurrentRecord is of Promise<String> type, not Promise<Object> type. TBD
If you use "edit" for the action button type, be sure to specify "edit" for the "name" of the action button. TBD
In the "operator" label of the YAML definition of Statement, "in, notIn" cannot be used. TBD
The Tabs and Tab components in the YAML definition of the UI (version 1.1) are not available in the workflow detail window. The Article component cannot be used. TBD
If you want to delete a custom data model referenced from the "Custom data maintenance" window, follow the procedure described in "Deleting a custom data model". If you do not follow this procedure, you will not be able to use or delete the custom data model in question. Additionally, custom data models and Datamodel YAML files with the same name as the one that failed to delete cannot be used. TBD
The "Custom data maintenance" window supports only one level of inheritance for custom tables. If you create a "Custom data maintenance" window based on a custom table with inheritance settings, the columns you can view and operate are limited to those in the table one level above.
Examples:
  • Table B, which inherits from Table A
  • Table C, which inherits from Table B
In this case, the columns of Table A are not displayed in the "Custom data maintenance" window for Table C.
Therefore, creating a "Custom data maintenance" window that relies on inheritance structures with two or more levels is not supported. For details about inheritance settings, see "Datamodel". 		TBD
Options defined in "tables.columns.enum" within the Datamodel YAML definition cannot be deleted. TBD
2 API When workflowId is specified in a query with GET /api/v1/practice-contexts, 500 will be returned as the response code if a non-uuid-format value is specified. TBD
When executing GET /api/v1/acls/roles/{roleName}, malformed data may be returned if no ACL is assigned to the specified role.
(Example of malformed data: {"data":{"":{}})		 TBD
When creating a record in a custom table with a UUID via "POST /api/v1/graphql", using a UUID that does not comply with RFC9562 (versions 1-8) will result in an error when updating the record from the Datamodel application. If this happens, delete the record from the [Record List] window or the [record details] window. TBD
3 Other Importing and exporting tickets using OTOBO are not yet supported. TBD
You cannot delete tickets from the "Ticket zoom" window accessible via the following URL:
Ops I URL/sys_task/ticket/ticket_browser/ticket_detail/Ticket ID
TBD
If a group is renamed while users are logged in to Ops I, they cannot view the list of documents for the renamed group in the container window temporarily. Those users who have been logged in to Ops I will be able to see the list of the documents by logging in again. TBD
If you try to set an email address that was previously used by another user for an Ops I or IdP user, an error might occur during user creation, update, or login.
  • Ops I user creation:
    An error occurs during user creation, and the creation fails.
    Change the email address to one that has never been used before.
  • Ops I user update:
    An error occurs during the user update, and the update fails.
    Change the email address back to the previous one or to one that has never been used before.
  • IdP user creation:
    An error occurs during login via the IdP, and login fails.
    Change the email address to one that has never been used before.
  • IdP user update:
    An error occurs during login via the IdP, and login fails.
    Change the email address back to the previous one or to one that has never been used before.
 TBD
When importing records into a custom table, if the status is "processing", do not edit the Import YAML file specified during the import.
Also, if an error occurs during import, you must correct the problem causing the error and redo the import. Similarly, if the status does not change from "accepted" or "processing" to the next status, re-import the data.		 TBD
In custom tables, ensure that IDs are unique within the same table. When importing records into a custom table, if you set "id" as "target" in the "columnMappings" section of the Import YAML file and then import records containing duplicate IDs, records with duplicate IDs will be registered. If record IDs are duplicated, the records might be displayed incorrectly in the [Record List] window, and you might not be able to open the correct [record details] window from the [Record List] window.
If you have registered records with duplicate IDs, select and delete the records with duplicate IDs from the [Record List] window. Since all records with the selected ID are deleted, verify your registered data before proceeding with the deletion.
For details about the Import YAML file, see "Import".		 TBD
The system user (username "system") is a reserved user for Ops I. It might appear in windows where users are selected (e.g., the ticket watcher dialog box displayed via the [Watch] button in the "Ticket zoom" window, or the window for setting permissions in the dashboard application). Since there are no cases where you operate by the "system" user, this display has no operational impact. TBD
Changing the "Rows per page" setting or navigating between pages does not work correctly in "Organization List" in the "Organization management" window and the "Related resources" in the "Organization details" window.
Set the "Rows per page" setting to 100 and do not change it. Additionally, if the number of organizations or related resources exceeds the page limit, use filters to display only what fits on a single page before performing any operations.		 TBD
Depending on the display mode (client/server) of the window or table, the sorting results for string fields might appear different. (Example: Workflow list window)
In particular, if data containing blank (empty strings) or null values exists, those records might be grouped together at the beginning or end, resulting in an order that differs from your expectations.
When viewing data that includes "empty" records, use filter conditions such as "is empty" or "is not empty" as needed. For details about window and table display modes, see "Setting the display mode".		 TBD