1.4.2 Temporary restrictions
(1) Unsupported functions
The following functions are temporarily unsupported.
(Table) List of temporarily unsupported functions
| # | 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 | ||
| 2 | API | When workflowId is specified in a query with GET /practice-contexts, 500 will be returned as the response code if a non-uuid-format value is specified. | TBD |
| When executing GET /acls/roles/{roleName}, malformed data may be returned if no ACL is assigned to the specified role. (Example of malformed data: {"data":{"":{}}) |
TBD | ||
| 3 | Other | Importing and exporting tickets using OTOBO are not yet supported. | 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 |