> 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.0.1.2-29.5.0.2-28.10.0.2-and-27.17.0.2.md).

# Versions 30.0.1.2, 29.5.0.2, 28.10.0.2 & 27.17.0.2

Released on July 19th, 2024

For compatibility information 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;">Support for Vault 2025</mark>

{% hint style="success" %}
Starting with version 30.0.0.0, we added support for Vault Professional 2025.
{% endhint %}

### <mark style="color:green;">Improved licensing (LT Licensing)</mark>

All Publisher4VLT versions are now equipped with (mostly internally) redesigned licensing to greatly enhance the stability and user experience when using the product. Licensing information (token and license files) is now stored in the `c:\Users\---USER---\AppData\Roaming\Arkance\Licenses` folder.

* **Only one licensing method (online license) is now supported.**
* **Because of changes to the licensing folder, users must log into their Be.Smart (Holixa) account after running this new Publisher4VLT version for the first time.**\ <br>

  <figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2Flxm1LfIJ30UKDnCiW191%2Fimage.png?alt=media&amp;token=5d643f07-3cec-446f-83c7-6111c81c5c8e" alt=""><figcaption></figcaption></figure>

  <figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2Fx0YIjjtUCZOznFTRBTdN%2Fimage.png?alt=media&amp;token=77579d98-2315-4712-aa0f-dc47c4033f3d" alt=""><figcaption></figcaption></figure>

### <mark style="color:green;">120px thumbnail size support</mark>

In addition to the standard thumbnail size of 254px, it is now possible to select the size of 120px. It will help to improve the communication and sharing of the data with certain ERP systems. The option can be found on the Additional Settings tab of the thumbnail publishing module.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FPy6rIbyb1Bzoko7hTPId%2Fimage.png?alt=media&amp;token=aab5224f-5344-44ec-b671-02654d736dd7" alt=""><figcaption></figcaption></figure>

### <mark style="color:green;">Rebranding to Be.Smart</mark> <a href="#rebranding-to-be.smart" id="rebranding-to-be.smart"></a>

We have completed rebranding to Be.Smart style. All Publisher4VLT icons were adjusted, providing a unified user experience emphasizing the Be.Smart brand identity.

* Theme-based icon switching is available starting with Vault 2024.
* For versions 2022 and 2023, only one color version of the icon set is used. You must restart Vault Professional to use the icon set corresponding to the selected theme.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2Fwrm2nCUdMtndYs3zU2z9%2Fimage.png?alt=media&amp;token=fa0e4233-2917-41c0-a228-8251aa4ad487" alt=""><figcaption></figcaption></figure>

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

* Convert Configuration button was removed from the Tools -> Publisher4VLT menu as it no longer served its purpose.

{% hint style="warning" %}
To ensure the configuration is set correctly when upgrading from the pre-2020 Publisher4VLT to the most recent versions, only a manual configuration is supported (configuration must be set up from scratch by a PDM consultant).
{% endhint %}

* STL and JT publishing modules promoted from BETA to production. You can continue using them as before.
* We simplified the AC Core Console error message displayed when no corresponding AutoCAD version is installed in the system, so now it is easier for users to understand what's going on.
* DWG TrueView Core Console has some limitations in accessing the drawing data, therefore we disabled the option to publish the "Sheet as a separate file" and removed the "Custom layout selection" option when the "TrueView Core Console" is set for publishing.\ <br>

  <figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2F69NuncmW7y3jrQKngF77%2Fimage.png?alt=media&amp;token=bfa252a4-e665-4439-83e0-c4f2cfddec4f" alt=""><figcaption></figcaption></figure>

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

* Some typos in the user interface elements.
* Other bug fixes.


---

# 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.0.1.2-29.5.0.2-28.10.0.2-and-27.17.0.2.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.