Managing Export Center Workflows

Understanding what the Export Center can export

In Atloria, the Export Center is where you choose exactly what you want to send out of a project. The main source record is a documentation version. From there, you can export either the version by itself or the version together with related records that are linked to that selected version. Those related records matter when the destination needs more than the main documentation content, such as supporting items that belong with the same release or handoff.

You usually begin from an Export Center list that shows available records, or from a version detail view that leads into export actions for that specific version. In both cases, the workflow starts with the same decision: select the correct source version first. After that, Atloria asks you to choose an export path based on what you need the output to include.

The most important difference is scope:

• Single documentation version export gives you only the selected version.
• Documentation version with related records gives you the selected version plus linked content that belongs with it.

Before you start the export, pause at these decision points:

If you already checked readiness in Validating Export Readiness for Documentation Versions, use that work here instead of repeating it. In this stage, the focus is not whether a version is ready in general, but whether you are choosing the right record and the right export scope for the job.

Preparing the version and related records before export

Before you click Export, confirm that the version shown in Atloria is the exact revision you mean to send. If the Export Center includes a version selector, use it to switch to the correct version. If you started from a version detail page, review the version name and any visible status or identifying details there before opening the export options. This is the easiest place to catch a wrong selection before Atloria creates the output.

Next, review the related records attached to that version. If your export needs linked content, make sure those records are current and belong to the same release or handoff. A version can look correct on its own while still pointing to outdated or incomplete supporting records. When that happens, the export may finish successfully but still be missing important context.

Focus on these checks before exporting:

• The version name matches the release, review round, or handoff you intend to send
• Related records connected to the version are the ones you expect
• Names are clear enough that the exported package will be easy to identify later
• The source content looks complete, not partially updated

It also helps to review whether the record status and visible content match the intended use. For example, a review package may be acceptable with a narrower set of records, while an archive or handoff usually needs a more complete set. If something looks unfinished, go back and update the source records before exporting rather than trying to fix the package afterward.

Finally, make sure you can actually use the export actions on the records you selected. If the Export action is not available, or if you can open the version but cannot complete the export, your access may not include the required Export Center permissions or source record access. In that case, confirm your access with an administrator before continuing.

Choosing the right export path for your goal

The export path you choose in Atloria controls how much content goes into the final output. In practice, you are usually choosing between a narrow export and a broader export. A narrow export includes only the selected documentation version. A broader export includes that version plus its related records. The right choice depends on what the recipient needs to do with the output after it leaves Atloria.

Use this table to match common goals to the best export path:

A narrower export is usually better when the recipient only needs the main documentation version. This avoids clutter, reduces confusion, and keeps reviewers focused on the exact revision you selected. It is especially useful when you want a clean output for approval, comparison, or limited sharing.

A broader export is better when the destination needs context, continuity, or supporting records tied to the version. This is often the safer choice for archiving, migration, or team handoff because it preserves more of what belongs with the selected version.

When you open the export action or export dialog in Atloria, pay close attention to wording that indicates scope. If the option mentions only the selected version, expect a narrower result. If it mentions related records, linked content, or a fuller package, expect a broader result. If you are unsure, compare your goal against Choosing the Right Export for Sharing Review or Archiving before you run the export.

Exporting documentation versions and related records

1. Open the Export Center in Atloria and locate the documentation version you want to export. If you entered from a version detail page, confirm you are still looking at the correct version before moving on.

2. Select the version from the available records list. In list view, this usually means clicking the row or opening the record so the export actions apply to the right source item.

3. Click the Export action. Atloria will present the available export path options for that selected version. Choose whether you want:

   • only the selected documentation version, or
   • the documentation version together with its related records

4. Review the export configuration shown in the export dialog or confirmation screen. Check the selected version name carefully. If the export includes related records, confirm that this broader scope matches your purpose. If you only need a review copy, switch back to the narrower option before starting.

5. Start the export. Atloria will create the output based on the path you selected. Depending on the workflow shown in the Export Center, you may see a generated output record, a package entry, or a download-ready result after processing finishes.

6. Monitor the result in the Export Center. Look for the completed export entry and open it when it becomes available. If Atloria provides a Download link or a generated package record, use that item to access the exported output.

7. Open the exported result right away instead of assuming it is correct. A quick check immediately after export is faster than discovering later that the wrong version or wrong scope was used.

Checking that exported output matches the intended use

After the export finishes, open the file or package and compare it with what you intended to send. Start with the most important check: make sure the exported content matches the documentation version you selected in Atloria. Look at the version name, visible revision details, and any identifying labels in the output. This helps you catch cases where an earlier or later revision was exported by mistake.

If you chose an export path that includes related records, verify that those linked items are actually present in the output. Do not assume they were included just because you selected the broader option. Open the package and confirm that the expected supporting content appears alongside the main version. If the package looks too small or too simple for the path you chose, review it more closely before sharing it.

It also helps to compare the exported structure to the destination use case:

• Review: the output should stay focused and easy to inspect
• Archive: the package should preserve enough context for future reference
• Migration or transfer: the output should contain the items needed by the receiving destination
• Delivery or handoff: the package should include the version and the supporting records the recipient will expect

Check visible filenames, package contents, and how items are grouped. If the result feels too narrow, you likely exported only the selected version when you needed related records too. If it feels too broad, you may have included linked content that the recipient does not need.

When the output does not match the intended use, return to the Export Center and run the export again with a different path. That is usually faster and cleaner than trying to work around an incorrect package after it has already been shared.

Fixing common export mismatches and missing content

Most export problems in Atloria come from one of four issues: the package is missing records, the wrong version was selected, the export scope does not fit the destination, or the export action is unavailable. Start by identifying which of these happened before you rerun anything.

If the exported package is missing expected records, go back to the Export Center and check which export option you used. A package created from documentation version only will not include related records. If you expected linked content, rerun the export using the option that includes related records with the selected version.

If the wrong version was exported, reopen the source record before you click Export again. Confirm the version selector, list selection, or version detail page shows the intended revision. This is especially important when several versions have similar names or belong to the same project.

If the output does not fit the destination use case, the problem is usually scope rather than content quality:

• For a package that is too limited, choose the broader export path
• For a package that includes unnecessary items, choose the narrower export path
• For review, keep the export focused unless supporting records are specifically required
• For archive or handoff, include related records when context matters

If you cannot complete the export at all, check whether the Export action is visible and available on the selected record. Also confirm that you can access the source version and any linked records involved in the export. If access appears limited, work with your Atloria administrator to confirm your Export Center permissions and record access.

When you need a more detailed readiness check before trying again, return to Validating Export Readiness for Documentation Versions. If the issue is choosing the right package shape rather than fixing source content, compare your options in Managing Export Workflows for Documentation Records.

Overview

The Export Center in Atloria is built around a simple workflow: choose a documentation version, decide whether related records should travel with it, run the export, and confirm the result matches its purpose. The main records you work with are documentation versions and the related records linked to those versions. Every export begins by selecting the correct source record, either from the Export Center list or from a version detail page that leads into export actions.

The most important choice is export scope. If you export only the selected documentation version, the output stays narrow and focused. If you export the version with related records, the package becomes broader and better suited to archiving, transfer, or handoff. That choice should always be driven by the destination. A reviewer usually needs less than an archive or receiving team.

This workflow also depends on preparation. Before exporting, confirm the selected version is the intended revision, review the linked records that may be included, and make sure the visible names and content are complete enough for the package you want to produce. If the export action is unavailable, access to the Export Center or to the source records may need to be updated.

After the export finishes, open the result and inspect it. Check the version, the included items, and the overall structure against the reason you created it. If the output is too broad or too narrow, rerun the export with a different path rather than trying to reuse a package that does not fit.

Prerequisites

Before working in the Export Center, make sure these conditions are met:

• You can sign in to Atloria and open the authenticated workspace
• You can access the project, documentation version, or Export Center area needed for the export
• The documentation version you plan to export already exists and is identifiable by name or revision
• You know whether your destination needs only the selected version or the version plus related records
• Any related records you expect to include are already linked to the selected version
• The version and linked records have been reviewed for readiness in Validating Export Readiness for Documentation Versions
• The Export action is available for the records you need to use
• You have permission to view the source records and complete export actions in Atloria

It is also helpful to decide the destination before you begin:

• Review usually needs a focused export
• Archive usually needs a broader package
• Transfer depends on what the receiving destination expects
• Handoff often benefits from including related records

If you are still deciding which package shape fits your goal, review Choosing the Right Export for Sharing Review or Archiving. The next step after this workflow is Managing Documentation Exports for Sharing and Archiving, which covers how to use the exported results once they are created.