> 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.4.0.1-and-28.9.0.1-and-27.16.0.1.md).

# Versions 29.4.0.1 & 28.9.0.1 & 27.16.0.1

Released on March 22nd 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.holixa.com/?id=holixa-p4v).

{% hint style="info" %}
Keep in mind that PUBLIC BETA features available in these releases may - though unlikely - contain bugs.
{% endhint %}

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

### <mark style="color:green;">Support for publishing AutoCAD files to PDF without an AutoCAD license</mark>

A third option has been added to the configuration of the publishing job (Additional Settings tab), so now it is possible to use the TrueView core console to publish in PDF format. Therefore, AutoCAD license is no longer required!

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FcYSN5QYYLHjQJRHu6Jac%2Fimage.png?alt=media&amp;token=3be237ba-bc47-4260-be6d-05b7c84ac7bb" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
To use this feature, DWG TrueView version matching the corresponding Vault version must be installed.
{% endhint %}

If the publishing using the TrueView core console does not work, try the following steps:

* Check you have the DWG TrueView installed and that it can be succesfully run.
* Install the DWG TrueView, if needed.
* If the DWG TrueView is already installed, [reset](https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-reset-DWG-TrueView-to-defaults.html) it to defaults, or, if that does not help...
* ...[reset](https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-reset-DWG-TrueView-to-defaults.html) the DWG TrueView to deafults and (re)install it using the [latest installer](https://www.autodesk.com/products/dwg-trueview/overview).

### <mark style="background-color:green;">PUBLIC BETA</mark> <mark style="color:green;">- Publishing from Inventor to STL</mark>

A new “**Inventor STL**” publishing module is available for files and items to publish Inventor models (ipt, iam) to the STL file format suitable for, e.g., 3D printing.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FBQ96pl1c5YJTJakUOQsN%2Fimage.png?alt=media&amp;token=c4768752-cef0-44b1-973e-a1c461d8bccc" alt=""><figcaption></figcaption></figure>

The same philosophy as in the Inventor [STL File Save As Options](https://help.autodesk.com/view/INVNTOR/2024/ENU/?guid=GUID-68FCAD0E-93BD-4D90-B9FE-9CF82AA4E64D#:~:text=STL%20File%20Export%20Options) dialogue windows is used.

{% hint style="info" %}
Only the “One File” structure is supported to avoid any file naming issues or duplication of publishing tasks. In other words, only one STL file is published from the IAM file. Individual assembly components must be published directly from their source (IPT) files.&#x20;
{% endhint %}

### <mark style="background-color:green;">PUBLIC BETA</mark> <mark style="color:green;">- Publishing from Inventor to JT</mark>

A new “**Inventor JT**” publishing module is available for files and items to publish Inventor models (ipt, iam) to the JT (Jupiter Tessellation) visualization format developed by Siemens PLM and used for the data exchange in, e.g., automotive or aircraft industry.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FVhcMHJawZaIYJiwLYStX%2Fimage.png?alt=media&amp;token=be96d759-d1f9-4838-a575-1e2beb70150b" alt=""><figcaption></figcaption></figure>

The same philosophy as in the Inventor [JT File Save As Options](https://help.autodesk.com/view/INVNTOR/2024/ENU/?guid=GUID-68FCAD0E-93BD-4D90-B9FE-9CF82AA4E64D#:~:text=JT%20File%20Export%20Options) dialogue windows is used.

{% hint style="info" %}
Only the “MONOLITHIC” file structure is supported to avoid any file naming issues or duplication of publishing tasks. In other words, only one JT file is published from the IAM file. Individual assembly components must be published directly from their source (IPT) files.
{% endhint %}

{% hint style="info" %}
The "Level of Detail" section ("Use of Configuration File" checkbox) is not available due to an error reported to Autodesk regarding this feature.
{% endhint %}

### Publisher4VLT 2022 Only

* [Synchronization of category, lifecycle, lifecycle state, and revision index of a published file](https://help.holixa.com/holixa-publisher4vlt/whats-new/versions-29.1.0-and-28.6.0#synchronization-of-category-lifecycle-lifecycle-state-and-revision-index-of-a-published-file) is now available in Publisher4VLT 2022.

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

* Fixed a scrolling issue in the ITEM configuration window.
* Fixed an issue when publishing failed for Inventor drawings with "mixed" sheets' names.
* Fixed the issue where it was not possible to use the Inventor Raster publishing module with the "Current sheet" option.
* Fixed the issue where the selected folder structure was not saved in the PackAndGo rules configuration.
* Fixed some CZ translation bugs.
* Fixed the issue where - when publishing from ITEMS, it was not possible to copy properties from the original file to the published file, when the "Set item permissions on the published file" checkbox was used.
* Fixed the issue causing the source files to remain checked out after publishing.
* Fixed the issue causing the content of the Published Files tab not to be visible in dark mode.
* Fixed the issue where the "Custom layout selection" option caused a publishing error when "Ac core console" was used to publish AutoCAD DWG files to PDF.

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

* Modifications to the licensing mechanism to fix the recurring Midnight Issue.
* Improved behavior of handling the Login History file errors. Users' workflow should now remain uninterrupted because of the Login History error messages.
* Updated file naming behavior for the "Publishing visualizations" module
  * The source file extension will ALWAYS be a part of the published filename (a safety measure to handle the situations where the visualization files are to be published from multiple source files (idw, iam, ipt) with the same file name, which would result in only one visualization file being created).
  * If the source file extension position IS NOT defined in the "Publishing file name" configuration, or the configuration is empty, it will automatically be placed at the end of the file name.
  * If the source file extension position IS defined in the "Publishing file name" configuration, it will be inserted into the published file name according to this configuration.
* The "Sheet as a separate file" option is not available when publishing a Model space to PDF from AutoCAD drawing.
* The 1st phase of rebranding to Be.Smart
  * The installer and some main icons were rebranded to match the Be.Smart style. The rest will follow soon.<br>

    <figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2Fkfet5gGK8zTfSCkEzR3a%2Fimage.png?alt=media&amp;token=51db6508-da6e-4405-bcad-d349c88c6e2d" alt="" width="361"><figcaption></figcaption></figure>

## <mark style="background-color:purple;">Update Instructions for Web-license-activated Installations</mark> <a href="#update-instructions-for-web-license-activated-installations" id="update-instructions-for-web-license-activated-installations"></a>

{% hint style="info" %}
\*The below steps are valid for the following Publisher4VLT versions and newer: 29.1.0, 28.6.0, 27.15.0. You don't need to follow these instructions if upgrading from the internal RC1/RC2 builds.
{% endhint %}

1. Before uninstalling the older\* Publisher4VLT version from the Vault client, go to Tools → Publisher4VLT → About Add-In.
2. Click “License…” in the add-in summary window.
3. Click “Reset license” in the next window and confirm with OK.
   1. Alternatively, you can delete the content of the folder `c:\Users\!!USER!!\AppData\Roaming\ArkanceSystems\Publisher4VLT\`
4. Close the Vault client and uninstall the older P4V version.
5. Install this Publisher4VLT release.
6. Activate the product using your Holixa (Be.Smart) web license credentials (e-mail, password).&#x20;

<figure><img src="https://m1906.sharepoint.com/_api/v2.1/sites/m1906.sharepoint.com,c5384a60-78cc-4920-b9c4-3fe1ee927880,6793955b-086d-4824-aa9a-8720701ced20/items/b8856df3-f394-4a8a-9d34-f465ebb5b155/driveItem/thumbnails/0/c960x99999/content?prefer=noRedirect,extendCacheMaxAge&#x26;clientType=modernWebPart&#x26;format=webp" alt="" width="563"><figcaption></figcaption></figure>

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

{% hint style="warning" %}
After installing, the Publisher4VLT configuration must be manually reinitialized to accommodate changes. This process must be done only once by performing at least a small change that can be reverted to a previous state. This process is valid only if a configuration from a previous Publisher4VLT version is used.

* Please, go to the Publisher4VLT Configuration window.

* On the General tab, change the logging level and click the Save button. (Alternatively, you can change any settings you need).
  * *After this step, the settings reinitialization process is complete.*

* Repeat the above steps to revert the settings to a previous state if needed.
  {% endhint %}

* More than two condition rules cause Copy Native Files not to work. We are working on the fix. Temporarily, do not use conditions or use only one condition.

* AutoCAD PDF publishing module
  * The "Custom Layout Selection" option causes the publishing to fail (error in a Job Queue) or the incorrect/incomplete layouts can be published when the True View core console is used for publishing.
  * The option to publish "Sheet as a separate file" is automatically disabled when the TrueView core console is used because the DWG TrueView core console alters the alphabetical order of the sheets. This can cause issues when publishing custom layouts.
  * Layout/Model names are not included in the published file name.

* The product license might become invalid overnight, leading to the failure of publishing jobs due to license issues. Manual reactivation is required. Avoid keeping the Vault client open on a job processor machine overnight as a temporary solution. A permanent fix is in progress.

* Inventor Model states are not supported.

* The “Use pending publication” feature of the latest ERP Connector versions (29.1.0.0, 28.6.0.0, 27.12.0.0) and older is not compatible with these Publisher4VLT releases. To use this feature, wait for the soon-to-be-released new versions of the ERP Connector.


---

# 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-29.4.0.1-and-28.9.0.1-and-27.16.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.