> 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-28.5.0-and-27.13.0.md).

# Versions  28.5.0 & 27.13.0

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.

## 28.5.0 & 27.13.0

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

### Inventor Drawing to AutoCAD module

It was not possible to select (and keep selected) the *Advanced optimization* option in `Additional settings -> Publication configuration method`.&#x20;

### Unique custom names of Inventor drawing sheets

IDW drawing sheets with names different from the default "Sheet" weren't processed (published). It was due to the fact Publisher4VLT expected the default sheet name + sheet index number. Other than the default sheet name caused the publishing job to fail.

The new behavior is:

* The drawing contains default sheet names (Sheet:1, Sheet:2, etc.): index is added automatically after the sheet name (Sheet\_1, Sheet\_2, etc.).
* The drawing contains custom sheet names (Assembly, Detail, etc.): no index is appended to the sheet name.


---

# 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-28.5.0-and-27.13.0.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.