# 6.3 Rules setting for Vault Publisher Pack and Go

If PackandGo publications are often performed with the same settings, rules can be set (so far only globally). These are then displayed in the "PackAndGo rules" selection 

In Vault client, drop-down menu Nástroje -> Vault Publisher -> Configuration (login as Administrator)

![](/files/7ZUEBLvouUZ1jT4VHexH)

![](/files/pBPDrtkqk5WHKU3hBljP)

The user fills in the rule name, publication path, the naming of the published files, the file structure of the data (pre-prepared structure or the Vault structure) and whether the file will be directly assigned to the compressed \* .zip folder. 

File naming can be done independently of already published data. As usual, the "Part Number" property is set as the main name of the published data in the Vault. It is used due to simple rewriting and disconnection of already published documentation when unapproved and approving CAD documentation.

![](/files/gxPUIxTnnuIGKdpCR8Ao)

In Pack and Go Settings, you can easily change the name of published files and assign additional properties (from a file and from an item) to it. This setting is only transferred within PackAndGo.

![](/files/B2Oak9K6SMOvy6UVWK4b)

In the **“Publishing file´s name settings“** dialog is possible to choose from three predefined methods.

* **Free text** – any text variable 
* **Vault numbering scheme** – predefined numbering scheme 
* **Vault Property** – as for the file as for item

By selecting the required property, is possible to add or remove it.![](/files/kBs9Nkvs5x53EsAaGGaX)


---

# Agent Instructions: 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:

```
GET https://help.holixa.com/holixa-publisher4vlt/fundamentals/6-export-publishing-documentation-through-vault-publisher-add-in/6.3-rules-setting-for-vault-publisher-pack-and-go.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.