> For the complete documentation index, see [llms.txt](https://boomi.markusschmidt.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boomi.markusschmidt.pro/boomi-console/command-collection/command-collection-1.md).

# Deployment Task Document

Normally you want to document what needs to be deployed. One process, multiple processes, with dependend components (e.g. process routes) etc. A deployment task document would be required.

Create a deployment task document that lists all components that must be deplyoed together with a *parent* component.

```batch
bc comp get /c <compId> /t deployTask.md /DeployableOnly /Children=Independent
```

* `/c` the components for which to create a deploymen task document. You may also provide multiple components or a component package, as mentioned abouve\
  (see [Common Arguments](/boomi-console/commands/arguments/common-arguments.md)).
* `/DeployableOnly` restricts the considered components to deployable componentes: *Processes, Certificates, Services, Process Routes, APIs*.\
  \&#xNAN;*Maps*, *Profiles* are not deployable and therefore skipped.
* `/Children=Independent` Get only children which have an *independent* relationship to their parent(s) - the `<compId>`. Only those child components require a separate deployment. Sub-Processes (not routes), for example, are *dependent* components and not deployed separately.
* `/t` specifies the [template ](/boomi-console/library/the-report-engine.md)that is used to render a nice document.

### Templates

The `deployTask.md`template renders a nice Markdown output that you can hand over to your deployment admin.

<figure><img src="/files/9hhs4zSBnQnSaurqSFgc" alt=""><figcaption><p>Deployment Task MarkdDown file</p></figcaption></figure>