> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/virtual-environments/virtual-environment-packages/accessing-packages/the-anatomy-of-a-package.md). # The anatomy of a package ## Introduction Having created a new package or selected an existing package, package details are displayed - for example:

Here, information is displayed in two panels: * [Flows](#the-flows-panel) * [Deployments](#the-deployments-panel) ## The flows panel The `flows` panel displays all process flows in the package. The following details are shown for each process flow:

Panel	Summary
Name	The name of the process flow.
Version	The process flow version number that was added to the package.
Queue priority	The queue priority that was selected when the process flow was added to the package.
Remove	If the package has never been deployed, you have the option to remove an existing flow. This option is not displayed for a package that has been deployed.

## The deployments panel The `deployments` panel displays all virtual environments where this package is deployed. The following details are shown for each virtual environment:

Panel	Summary
Environment	The name of the virtual environment.
Version	The virtual environment configuration version used for this deployment. If a deployed configuration exists for the selected virtual environment, this will be used when a package is deployed. Otherwise, the current `draft` configuration is used.
Deployed at	The date and time when the package is deployed.
Deployed by	The name of the person who deployed the package (as per account settings).

Each entry has an associated 'expand' option - for example:

Use this to view the current status of the associated flows in the virtual environment. When a package is deployed, all associated flows are enabled in the selected virtual environment. Subsequently, you may choose to [disable](/product-documentation/virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/disabling-or-enabling-a-process-flow-deployment-for-a-virtual-environment.md) or [delete](/product-documentation/virtual-environments/managing-virtual-environments-versions-and-flows/managing-virtual-environment-flow-deployments/deleting-a-process-flow-deployment-from-a-virtual-environment.md) flow deployments in that environment; in this case the status shown here is updated. --- # 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://doc.wearepatchworks.com/product-documentation/virtual-environments/virtual-environment-packages/accessing-packages/the-anatomy-of-a-package.md?ask=&goal= ``` `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.