> For the complete documentation index, see [llms.txt](https://help.besmart.software/p4v/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/p4v/whats-new/versions-30.2.0.1-29.7.0.1-28.12.0.1-and-27.19.0.1.md).

# Versions 30.2.0.1, 29.7.0.1, 28.12.0.1 & 27.19.0.1

For information on the compatibility of each P4V version with Autodesk Vault versions, visit the [System Requirements](/p4v/system-requirements.md#compatibility-matrix) page. To download the software, visit our [download page](https://download.besmart.software/).

## <mark style="color:green;">New features</mark>

### <mark style="color:green;">Inventor BOM Export Module (BETA)</mark>

The new *Inventor BOM* publishing module (currently in Beta) streamlines customer workflows and expands the capabilities of (particularly) file-based Vaults by enabling the export of Inventor assembly Bill of Materials (BOM) to CSV and XML files. The resulting CSV/XML file can then facilitate **one-way** communication with various business systems.

Exporting BOMs to CSV/XML files provides simple ERP integration-like capabilities, even for Autodesk Vault users without a full Vault-ERP integration.

<figure><img src="/files/sijdLY2dggnWG7g4TuFp" alt=""><figcaption></figcaption></figure>

The publishing module is available both for files and items and uses the same configuration principles as other publishing modules. The CSV/XML file BOM content can be configured on the *Additional settings* tab.

<figure><img src="/files/D5CZMTsTpONvWxSQkHAq" alt=""><figcaption></figcaption></figure>

The following options are available:&#x20;

* *CSV* or *XML* output.
* *Structured* or *Parts Only* views can be published. They don’t need to be enabled in the assembly file in advance.
* *First Level Only* or *All Levels* of BOM can be published.
* Selection of the *Item Number Delimiter*.
* *Virtual Components* can be exported or ignored.
* Inventor standard or custom properties and Vault properties can be exported.

#### Standard configuration workflow

1. In the *BOM Settings* section, select the basic configuration options:
   1. View to export,
   2. Structure level,
   3. Output file type,
   4. Item number delimiter.
2. Add properties to the list (the *Columns* section):
   1. Select the *Property Type* first.
      1. For the *Inventor* property type, select the property from the *iProperty* drop-down list, or enter the custom (user) iProperty name in the *User iProperty* field.
   2. Click the *Add* button to send the property to the list.
   3. *Up*, *Down*, and *Remove* buttons can be used to organize properties in the list.

### <mark style="color:green;">Hybrid Category, Lifecycle Status, and Revision Synchronization</mark>

We have added a third mode for lifecycle status and revision synchronizations, which can be configured on the *Publishing Targets* tab of the publishing configuration window.

To recap:

* The first mode enables users to synchronize all parameters by the source FILE entity.
* The second mode enables users to set all parameters statically based on the selected category.
* The third, hybrid mode, allows users to select the category while synchronizing the rest with the source FILE entity.&#x20;

<figure><img src="/files/VLOCdcQ1ozOBZES9QxY7" alt=""><figcaption><p>A different category can be selected for published files</p></figcaption></figure>

<figure><img src="/files/eESet4KjdcIDIsx43X0Z" alt=""><figcaption><p>Published csv files with different category than the source file</p></figcaption></figure>

Such a configuration provides users with greater flexibility in solving complex workflow requirements.

{% hint style="warning" %}
The selected category must contain the same lifecycle, states, revision scheme, and index as the source FILE entity.
{% endhint %}

### <mark style="color:green;">PackAndGo Speed Improvements</mark>

#### **Loading of the PackAndGo search window**

Thanks to improvements in search algorithms, the PackAndGo search window loading speed can be up to 98% faster compared to previous Publisher4VLT releases - a real time-saver for customers! This enhancement is particularly beneficial for users connecting to a remote Vault and working with large assemblies (thousands of components).

<figure><img src="/files/DPLw3SLbG3zNOv55c4tp" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The actual value depends on the publishing configuration and the network infrastructure when accessing the remote Vault server.
{% endhint %}

**Loading of the PackAndGo copy window**

We also removed a slowdown when opening the PackAndGo copy window. Compared to previous Publisher4VLT releases, it no longer tries to automatically rename the published files to match the default source file names, thus saving users time.

<figure><img src="/files/Y7NgJ48a3lYlDXlYjBLf" alt=""><figcaption></figcaption></figure>

## <mark style="color:blue;">Other Changes and Improvements</mark>

* The library necessary for communication with the ERP Connector was updated. We also fixed the issue causing the *link\_type* identifiers to be assigned incorrect values in the database after being transferred to the EcLink table.&#x20;
  * The corresponding versions of the ERP Connector for the *Pending publication* feature are [mentioned here](https://help.besmart.software/erpc/whats-new/versions-30.1.0.6-29.3.0.5-28.8.0.5-and-27.14.0.5).
* Watermarks behaved incorrectly when the watermark text was entered directly into the *Set watermark text* field. We’ve made this field read-only to clarify that the *Settings* button must be used to configure watermarks.
  \*

  ```
  <figure><img src="/files/k1bZ7T7aTMLfHUrYuNMv" alt=""><figcaption></figcaption></figure>
  ```
* Because it was not functioning correctly, we have removed the option to execute Publisher4VLT and ERP Connector commands from the context menu in all *Preview Pane* tabs. Publisher4VLT and ERP Connector menu entries are now grayed out, and the only option to run their commands is through the files/items list, which is the standard method normally used.
  \*

  ```
  <figure><img src="/files/C6NgpE5vH6OKhSIXTrm5" alt=""><figcaption></figcaption></figure>
  ```
* The *Enable synchronize lifecycle status and revisions as a source file* checkbox on the *Publishing targets* tab of the job configuration has been renamed to *Enable lifecycle status and revisions synchronization*. The original checkbox name was confusing because it suggested that synchronization would always occur by the source file, regardless of the category selection.
  \*

  ```
  <figure><img src="/files/EiKjfjX9mdeOyOYkRf05" alt=""><figcaption></figcaption></figure>
  ```
* We have renamed the nonsense "Not a type" value in the "Update document" list.
  \*

  ```
  <figure><img src="/files/p5IB7jFaJOhZRrcUMVXz" alt=""><figcaption></figcaption></figure>
  ```
* We have added an automatic migration of the configuration file to accommodate new features introduced to Publisher4VLT.
  * This migration will take place in the background during the first initialization of Publisher4VLT after installing the new version, provided that the developer has enabled it in the code of this version. No user interaction is needed.
  * An example of a new migration record in the syntax of a configuration file: `<HistoryOfMigrationConfigs Name="FixHybridLFCLAndRevisionSync" MigratedTime="3/24/2025" />`
* We have improved logging to better track the process when published files are attached to items.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.besmart.software/p4v/whats-new/versions-30.2.0.1-29.7.0.1-28.12.0.1-and-27.19.0.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.