> 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/version-28.0.3.md).

# Version 28.0.3

Released on 13th January 2023

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

## Known Issues

* Some user accounts may experience random web license disconnecting. That may happen mostly after midnight. Manual reconnecting/restart of the licensing client is necessary.
* A standalone licensing method may experience issues if a shared licensing folder is used.
* The API key licensing method may experience issues if a shared licensing folder is used.
* Inventor Model states are not supported.

We are working on fixes, and in the meantime, we recommend you test the behavior before deployment to the production environment.

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

* Bug 36681 (Holixa licensing fails after a while)
* Bug 36682 (Watermarks - only the text behind ":" is printed to PDF)
* Bug 36687 (Typo in Published Files tab - "...was not founded")
* Bug 37309 (Rename \*.ps to \*.ps1 when selecting a post-process script to run)

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

### Option to Publish a PDF in separate folder

#### Publish to the same folder as the source file

The published file will always be in the same folder as the source file.

*Example*

If the source file "V000003.idw" is stored in the "$/Data" folder, the published file "V000003.pdf" will also be stored in this folder.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2F9WNjFh9s2lx44K9PeYhX%2F001%20Publish%20to%20the%20same%20folder%20as%20the%20source%20file.png?alt=media&amp;token=e33985c6-d7f9-4760-a8a6-245a695037f3" alt=""><figcaption></figcaption></figure>

#### Publish to the defined folder

The published file will be stored in the defined folder according to the configuration. If the folder defined for the publication does not exist, Publisher4VLT will automatically create it. All files of the given configuration will be published to this folder.

*Example*

If the source file "V000003.idw" is stored in the "$/Data" folder, according to this configuration, the published file will be stored in the "$/Data/PDF/V000003.pdf" folder.

If the source file "V000003.idw" is stored in the "$/Data/Project 1" folder, according to this configuration, the published file will be stored again in the "$/Data/PDF/V000003.pdf" folder.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FKpOujEW9HqwvecSBEhpI%2F002%20Publish%20to%20the%20defined%20folder.png?alt=media&amp;token=50540785-5057-43aa-bf7b-f3050567ffb8" alt=""><figcaption></figcaption></figure>

#### Publish to the relative path

Publisher4VLT also allows publishing to a relative path. The relative path is entered using the slash character "/". The published file will be stored in a folder related to the folder where the source file is stored. If the folder defined for the publication does not exist, Publisher4VLT will automatically create it.

*Example*

If the source file "V000003.idw" is stored in the "$/Data/Project 1" folder, according to this configuration, the published file will be stored in the "$/Data/Project 1/#PDF/V000003.pdf" folder.&#x20;

If the source file "V000003.idw" is stored in the "$/Data/Project 2" folder, according to this configuration, the published file will be stored again in the "$/Data/Project 2/#PDF/V000003.pdf" folder.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2F3kr6ghgivxlL2D2RJYY1%2F003%20Publish%20to%20the%20relative%20path.png?alt=media&amp;token=1ed64258-6b79-4249-a450-263e7c617654" alt=""><figcaption></figcaption></figure>

### Naming according to the properties of the sheets&#x20;

It is now possible to use the properties 'Sheet name' and 'Sheet number' to name the published file when publishing an image from a drawing using the InventorRaster module

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2FLwLMsCqakFNvWRfok73l%2FNaming%20by%20Drawing%20sheet.png?alt=media&amp;token=4a30eb18-a727-4ef8-abcf-6e44066167b9" alt=""><figcaption></figcaption></figure>

### Languages

#### Czech language support

Publisher4VLT now supports the Czech language.

#### Change the default language

Supported language variants are automatically detected based on the language version of the Vault client. Newly added option to change this default setting and set Publisher4VLT language variant as needed.

<figure><img src="https://4111171440-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F84dgaorYMHNzbCzAM2fW%2Fuploads%2Fa2ILGpVJsGe9mrE1iXLs%2FSelect%20languages.png?alt=media&amp;token=977d65e1-c70b-4082-a9fb-23f6c23b468e" alt=""><figcaption></figcaption></figure>


---

# 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/version-28.0.3.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.