> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/code-to-cloud/code-to-cloud/references/page-reference-f-call-to-action-routing-by-asset-type1.md).

# Page Reference F: Call-to-action routing by asset type1

This appendix lists the Code-to-Cloud tab's empty-state and partial-state call-to-action routing by asset type and trace condition.

| Asset type / condition              | Call-to-action routes to | Use when                                                                                           |
| ----------------------------------- | ------------------------ | -------------------------------------------------------------------------------------------------- |
| Repository or Software Package      | Onboard Pipeline         | The build/deploy pipeline is not yet onboarded, breaking the Build/Deploy trace.                   |
| General cloud asset                 | Onboard                  | The cloud asset lacks the upstream data source needed to trace it back to code.                    |
| IaC Resource with YOR tag           | Onboard                  | The IaC resource carries a YOR tag but the runtime cloud side is not yet onboarded.                |
| IaC Resource without YOR tag        | Enable Tagging Bot       | No YOR tag exists, so the tagging bot must be enabled to write the trace tag.                      |
| Partial trace (any supported asset) | Add Data Source          | Some phases are connected and at least one data source is missing to complete the remaining phase. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/code-to-cloud/code-to-cloud/references/page-reference-f-call-to-action-routing-by-asset-type1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.