> 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/administration-and-setup/workflow/cards-overview/card-versions-guide.md).

# Card versions and availability

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-9b9cb5985a90a9605b32acda7252234fefd2dc2f%2Fworkflow-card-qa-20261021-card-4636f0bfbcc3-en.png?alt=media" alt="Card fields in the displayed version. The placeholders are not configured." width="563"><figcaption><p>Card fields in the displayed version. The placeholders are not configured.</p></figcaption></figure>

A card in a saved workflow retains its card ID and version. A newer template can add fields or change behavior without changing every previously saved workflow. Check the version on the actual card before applying instructions for a newer version.

## Before changing a saved card

1. Record its fields and current result on representative test data.
2. Compare its version with the reference, including defaults and missing-data behavior.
3. Upgrade or replace the card only through the supported builder action and review its settings again.
4. Validate the graph and test passing, failing and missing-data cases before activating the changed workflow.

Do not edit a stored technical card type merely to correct its spelling. Existing workflows can depend on that identifier. An unsupported version is an execution error, not a false business condition.

## If a documented card is absent

Check the selected When, And or Then group, category, Standard versus Advanced builder, enabled modules, permissions and deployed release with your administrator. A card mentioned in a technical integration or newer reference is not necessarily enabled for your organization. Do not create or import a guessed card definition to work around a missing template.

The additional calendar conditions described in some development material are not a confirmed selectable set in every release. The Document-variable setter is also implemented without a generally seeded UI template. Use the cards actually available in your environment and request clarification before depending on an unavailable one.

## References that depend on the version

* [Export cards](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/export-cards-guide.md): result status and immediate versus queued export.
* [PO comparison cards](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/po-comparison-versions-guide.md): comparison direction and tolerance base.
* [Quote comparison cards](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/quote-comparison-guide.md): Any/All and missing comparable prices.
* [Logic cards](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/logic-cards-guide.md): tags, organization variables and input types.

Use [Workflow Logs](https://docs.docbits.com/administration-and-setup/workflow/workflow-logs.md) to distinguish success, a false condition, missing data, a setup error and a skipped card. Record the document state and card settings with a test result; a screenshot of the card picker alone does not establish runtime behavior.


---

# 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/administration-and-setup/workflow/cards-overview/card-versions-guide.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.
