> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sheetmetalconnect.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Follow a QF2UNS project export

> See how an exported QuotationFactory project reaches the UNS, how revisions are identified, and what to check in a receiving application.

A QF2UNS export starts in QuotationFactory and ends with project data available to configured UNS consumers. The receiving application determines what its users can do next.

## From calculation to connected application

```mermaid theme={null}
flowchart TB
  A["Calculate the project in QuotationFactory"] --> B["Export to ERP through the configured QF route"]
  B --> C["Edge Connector supplies project files"]
  C --> D["QF2UNS preserves files and publishes project entities"]
  D --> E["UMH ingress brings messages into the UNS"]
  E --> F["A configured consumer processes the project"]
  F --> G["Check the project in that application"]
```

1. **Export the project.** Use QuotationFactory's normal export to ERP, or the export settings agreed for the installation. The Edge Connector supplies the project files.
2. **Look for the project in the receiving application.** Search using the project reference and compare the parts and attachments needed for the work. The application may show a different view from QuotationFactory.
3. **Continue in that application.** Its own workflow determines the next action. QF2UNS does not itself approve a quotation, create a production order, or record a delivery.
4. **If the project is missing or incomplete**, follow [the checks for a missing project](https://docs.sheetmetalconnect.com/qf2uns/troubleshooting.md). A connector confirmation alone does not establish that the receiving application processed it.

## When a project is exported again

A new export is handled as a revision. The worker keeps a revision identity and publishes an overview of the expected project data. A receiving system can use those identities and the overview to distinguish revisions and reconcile the project.

```mermaid theme={null}
flowchart TB
  A["Project export"] --> B["Reserve revision identity"]
  B --> C["Publish project data and revision overview"]
  C --> D{"Publication interrupted?"}
  D -->|"No"| E["Confirmation and archive"]
  D -->|"Yes"| F["Retry may repeat messages"]
  F --> G["Receiving system recognizes repeated data"]
  F --> C
```

A retry can repeat messages around a failure. The receiving system needs to recognize repeated data so the same revision is not processed twice. The confirmation does not guarantee a single delivery. If an export reuses a filename with different contents, the worker rejects it rather than treating the changed file as the earlier export.

[Overview](https://docs.sheetmetalconnect.com/qf2uns/overview.md) · [Troubleshooting](https://docs.sheetmetalconnect.com/qf2uns/troubleshooting.md) · [Nederlands](https://docs.sheetmetalconnect.com/nl/qf2uns/workflow.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.