> 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-29.1.0-and-28.6.0.md).

# Versions  29.1.0 & 28.6.0

For compatibility information of each P4V version with Autodesk Vault versions, visit the [System Requirements](/p4v/system-requirements.md#compatibility-matrix) page.

{% hint style="success" %}
With version 29.x.x, we bring support for Autodesk Vault Professional 2024.
{% endhint %}

{% hint style="info" %}
All the below-mentioned information is valid for both Publisher4VLT versions.
{% endhint %}

{% hint style="danger" %}

* Because of the lifecycle, lifecycle state, revision index of a published file, and categorization synchronization, internal objects storing the information about the file and item categories in Vault were modified. These objects are also used in the "Category rules" section. When upgrading, we recommend checking this part of the configuration thoroughly.
* Due to a change in license file storage folders, Publisher4VLT must be re-licensed.
  {% endhint %}

## <mark style="background-color:orange;">Fixes</mark>

* The “Midnight Issue” (web license disconnecting after midnight) was fixed.
* “Proxy error on start” fix implemented.
* The repetitive text from the validation message has been removed.<br>

  <figure><img src="/files/z9UeewSpXeGxGjc4UWqP" alt=""><figcaption></figcaption></figure>
* We fixed the error when saving the configuration of Inventor publishing modules if the publishing application "Inventor Vault Server" was set and the configuration for "Application process" had been removed.<br>

  <figure><img src="/files/y1JYH61XqPGv6luJ9xG2" alt=""><figcaption></figcaption></figure>
* In some cases, the publication file was not disconnected when the item status was changed.\
  The error occurred when the revision index was in the published file name, and the revision was incremented when the item's lifecycle state changed (for example, changing the state from „Release“ to „Work in progress“).

## <mark style="background-color:blue;">Changes</mark>

* Licensing information is now stored in Publisher4VLT dedicated folder so no other Holixa-licensed products can affect the licensing of Publisher4VLT and vice versa.&#x20;
* The license verification on JobProcessor now occurs only at startup.
* The "Publishing into Vault" option, which confused some users, has been removed from the “Copy native files” module. To copy native files inside Vault, use the Vault Copy Design feature.<br>

  <figure><img src="/files/AVxrpszHUUJpcahiseqQ" alt=""><figcaption></figcaption></figure>
* As a part of the modifications, the “Set item permissions on the published file” was moved to the “Synchronize category, lifecycle, and revision or set item permissions on the published file” section when publishing to Vault.<br>

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

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

### Synchronization of category, lifecycle, lifecycle state, and revision index of a published file <a href="#synchronization-of-category-lifecycle-lifecycle-state-and-revision-index-of-a-published-file" id="synchronization-of-category-lifecycle-lifecycle-state-and-revision-index-of-a-published-file"></a>

When publishing to Vault, you can now set the category, lifecycle, lifecycle state, and revision index of the published file. It is possible to choose whether the category, lifecycle, and lifecycle state are taken from the source entity...

<figure><img src="/files/m5ACAdD2Og1AKlNFzsWf" alt=""><figcaption><p>Synchronization with the source entity (<em>Publishing targets</em> tab in the publishing configuration)</p></figcaption></figure>

...or you can choose your own (custom) settings.

<figure><img src="/files/OdrIdF8jjow55jJcIBoX" alt=""><figcaption><p>Custom synchronization settings (<em>Publishing targets</em> tab in the publishing configuration)</p></figcaption></figure>

&#x20;Also, you can copy the properties from the original file to the published file.

#### **Synchronization with the source entity**

The category, lifecycle, lifecycle state, and revision index of the published file will be synchronized with the source entity. *When publishing from an item, only synchronization with the source file is available because the categories for the item and the file are different in Vault*.&#x20;

#### **Custom settings**

The lifecycle and revision schemes in the menus correspond to the selected category as defined in Vault, i.e., not all lifecycles and revision schemes are displayed, only those associated with the category.

#### **Common settings**

The revision index is always synchronized from the source entity. When publishing from the file, it is always the source file. When publishing from the item, the user can choose the source file or the source item.

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

The revision scheme of the source entity (file, item) has to be the same as the revision scheme that is selected for the synchronization.

For example:

<table><thead><tr><th width="304">Revision scheme for the source entity</th><th width="306.3333333333333">Revision scheme for synchronization (in Publisher4VLT configuration)</th><th>Result</th></tr></thead><tbody><tr><td>Alphabetic (indexes: A, B, C, ...)</td><td>Alphabetic (indexes: A, B, C, ...)</td><td>Supported</td></tr><tr><td>Numeric (Indexes 1, 2, 3, ...)</td><td>Numeric (Indexes 1, 2, 3, ...)</td><td>Supported</td></tr><tr><td>Alphabetic (indexes: A, B, C, ...)</td><td>Numeric (Indexes 1, 2, 3, ...)</td><td>Unsupported</td></tr></tbody></table>

## <mark style="background-color:yellow;">Known Issues</mark>

1. When editing the old publishing configuration for the first time, the below-displayed error message may appear.

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

The solution is to:

* Click OK to close the error message.
* Click OK in the publishing module configuration window (no changes are necessary).

2. Inventor Model states are not supported.


---

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

```
GET https://help.besmart.software/p4v/whats-new/versions-29.1.0-and-28.6.0.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.