Graphic Hub Administrator Guide

Version 3.8 | Published February 06, 2023 ©

Export Archives

Folders and/or files can be exported out of the Graphic Hub as Viz archive files (*.via) through the Archives Panel.

Note: Export of archives only works properly for content located in the /data root project and assumes that any data is stored inside the specified data-root location. It does not store the /data root part with the objects path, otherwise Viz Engine (or any other client, using the data-root setting) would not be able to correctly import it again.

To Export a Folder or a Single File

Note: Folders and files can be multi selected in the Explorer panel.

  1. Select the folder or file to be exported as an archive:

    • In the Servers and folders panel select a folder, or

    • In the Explorer panel select a file or folder

  2. Drag the selected folder or file to an archive in the Archives panel.

  3. Fill-in the Export to Archive panel, as required.

    Note: Export all linknames to the archive: All link names are exported (default). When unchecked, only link names from the folder/project from where the file was dragged, are exported to the archive. Link names in sub-folders are also added.

  4. Click Continue.

  5. Click Export.


Context Menu Export

To Export a Folder or a Single File

  1. Right-click the folder, project, or file to be exported.

  2. Select Export to archive.

  3. Click Browse to select a destination folder.

  4. Enter a name for the archive.

  5. Click Apply password to generate a password-protected archive.

  6. Click Export.

    Note: If password protection is enabled, the archive must be unlocked by entering the correct password to import or modify it. The user is automatically asked to enter the password during at import or modification. Password protection can also be added on an existing archive by context-menu View > Archives > Apply password. To remove password-protection, leave an empty password.

    Note: Creating an archive via Graphic Hub Manager on a network drive needs a mapped network drive, do not use UNC Paths (for example, //SERVER/DRIVE/sharedfolder/)