> For the complete documentation index, see [llms.txt](https://docs.colt.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.colt.net/on-demand/ja/on-demand-lso-portal/akutibitirogu.md).

# 注文アクティビティログ

## 注文アクティビティ&#x20;

その **注文** このセクションでは、新規注文（“create”）、既存注文の変更（“modify”）、および停止（“delete”）を含め、アクティビティログ形式で登録されたすべての注文を表示します。&#x20;

<figure><img src="https://content.gitbook.com/content/VLSaOIDXVwkVeVU0OgDq/blobs/KVva4ajN2gOs9wVQFQhD/Screenshot%202026-06-26%20155740.png" alt=""><figcaption></figcaption></figure>

各注文アクション（create、modify、delete）には、Mplify Sonata仕様に整合した個別のステータスが割り当てられます。 &#x20;

以下の表は、各サービスステータスの簡単な説明を示しています：&#x20;

| LSO注文ステータス | 説明                       | Mplify注文状態 | カラーコード |
| ---------- | ------------------------ | ---------- | ------ |
| 進行中        | 注文は登録され、現在配送中です          | 確認済み / 進行中 | 白      |
| 完了         | 注文は配送されました               | 完了         | 緑      |
| キャンセル済み    | 注文はColt管理者によってキャンセルされました | キャンセル済み    | 赤      |
| 失敗         | 配送に失敗しました（修正待ち）          | 失敗         | 赤      |


---

# 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.colt.net/on-demand/ja/on-demand-lso-portal/akutibitirogu.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.
