The Query Builder is a useful tool to search for files. It would be great if the configuration of the fields to search can also be part of the distributed searches/settings.   Right now what seems to work is to copy the "Displayed Properties" in the  "C:\Users\<username>\AppData\Roaming\Autodesk\Autodesk Vault Professional 2024\Servers\<servername>\Vaults\<vaultname>\History\QuickFindHistory-IExplorerObject.xml" file, but it is a manual process.   Show More

We have two different work flows, one for standard parts that are highly controlled and one for custom parts that are usually only used once for a job then not changed again but reused of future projects.  The problem we are having is that we do not want the people who are working on custom parts to have access to any standard parts that are currently in work in progress (WIP).   Sometimes parts that are WIP are actually in some larger assemblies and if a user does a "get" of that larger assembly and its children, they will get the WIP version of those parts.  I can deny downloading for them on WIP parts but the problem with that is that vault does not know to go back the most recent version that that user does have permission to download.  What vault does is looks in the user's working folder and deletes that file (if it exists in their working folder) and tries to download the most recent version but the permissions denies the download, so then there is a missing part from the upper level assembly.    There also is not a way to download a previous version manually because the most recent revision is work in progress.   I could also prevent them from seeing WIP parts but Vault hides all revisions not just the work in progress revision.      There needs to be a way for users to be able to download the most recent "released" version of files, not just the most recent.   Show More

Functionality:   Provide a user-friendly environment with no Powershell scripting to relate numbering schemes with cascading properties and discrete visibility to specific categories.   Autodesk example that exists today:   Look at the ACC solution. You can easily create a properties using any definition you want, attach it to a numbering scheme. The numbering scheme is not limited to 10 fields, it can be longer to fulfil international standards. Once user selects the file name from picklist, the properties are automictically populated according to selection. You can easily map the numbering scheme to specific folders by "tick box" process where applies, hence discrete list is offered to end-user - same concept can be adopted for categories.   No powershell required, easy adoption and agile to suit projects and product delivery.     Show More

Hello VAULT team,   at the moment it is possible to customize the output file names of PDF files created with the Job Processor by modifying the Job Processor configuration file JobProcessor.exe.config. The naming convention defined in the config file is valid for all files in the vault. (see picture "VAULT-1" and "VAULT-3")   However, in different projects we need different definitions for the naming conventions for the created PDF files. It would therefore be important to be able to define multiple name definitions in the config file. The application of the appropriate naming convention should be based on the file category of the file from which the PDF is to be created.  (see picture VAULT-2)   For each project, we create a project-specific file category and use it to assign the appropriate life cycle and revision scheme to the files. Using this project-specific file category, the job processor could recognize which naming convention it should use to create the PDF file.   It would be great if these configuration options were added quickly. Thanl you. Show More

When using Copy Design in Vault to copy a file with an higher Revision, the target files are non-compliant when the Revision Vault property of the source file is mapped to a file property. Synchronizing the property manually is an unnecessary step that should happen automatically. Please add the option to synchronize properties automatically. Show More

If the file’s lifecycle state hides the file, the Vault client displays a placeholder indicating the file, but those may not accessible. However, the target folder tree remains unavailable to the user. Why does the "Go to Folder" command not open an error dialog? => Working Folder and open Folder at Explorer are not the same! See Support Case No:23415931. Vault - Berechtigungen auf Dateien und Ordner      Show More

Our designers seem to love very long folder names. Vault checks the file path character limit when creating a folder but not when a folder is renamed.  A check like this would prevent jobs failing due to to many characters. Show More

We currently use the Vault Revision table and have run into an issue with enforcing comments during state transitions. Specifically, we need to ensure that a comment is provided when changing the state of an item, but Vault doesn't allow us to enforce input in the comment field during state transitions.   As a workaround, we considered using a file property to store the "Change Comment." However, Vault does not offer an out-of-the-box solution to clear specific properties when changing states. For example, it would be ideal to have the "Change Comment" property automatically cleared when transitioning a file from "Released" back to "Work in Progress" to avoid confusion with outdated comments.   It would be incredibly helpful if Vault could support a lifecycle transition action that allows us to clear selected properties, such as the "Change Comment," upon moving between specific states. This feature would provide a cleaner workflow and help prevent mix-ups from previous comments carrying over when they no longer apply. Show More

Please add the ability to use user/system properties in Vault's numbering schemes Show More