> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/gao-ji-gong-neng-yu-gong-ju/course/create-your-custom-app-in-infor-os.md).

# 在 Infor OS 中创建自定义应用

{% embed url="<https://youtu.be/TituJ3ljVQA?si=_9VWR1EAhWYjpBRb>" %}

{% hint style="warning" %}
自定义应用导入 DocBits API 规范时，请使用 **Swagger 2.0** 规范（`/openapi-swagger2.json`），而不要使用 OpenAPI 3.0 规范。Infor OS 使用的旧版 swagger-ui 需要 2.0 方言才能正确构建文件上传请求，否则上传会失败并显示 `400 — Missing boundary in multipart`。完整说明及 URL 的复制方法请参阅 [Infor OS 与 DocBits API 集成](/chinese/gao-ji-gong-neng-yu-gong-ju/course/infor-os-with-docbits-api-integration.md)。
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/gao-ji-gong-neng-yu-gong-ju/course/create-your-custom-app-in-infor-os.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.