Vault Ideas

francis.korde · ‎12-13-2023

With the new user management interface, there is no longer a column displaying "username" in the "User and Group Management" function. For each user, you have to click several times to find the information. Even when exporting everything to Excel, this information does not appear. According to Autodesk, only the "Display Name" is useful, but I don't agree. For Vault Administrators, it can be very useful to have all "usernames" at once, if only to check that you're not creating a duplicate because of a homonym. Also to check the consistency of the list between "username" and "display name". When you have a lot of users and/or suppliers accessing the Vault, the more information you have to manage them, the better. It's true that for all users connected to the Active Directory, the information may seem less useful since it's found in the AD, but for Vault users it only exists there. In my case, both types of account are used. I can understand that for security reasons simple users shouldn't have access to this information, but the "user and group management" function is blocked for them anyway. Please add the "username" column to the "User and Group Management" interface. Thank you.

xavier_dumont1 · ‎03-26-2021

Microsoft PowerBi is part of Office 365 Subscription. This product allows to create reports on almost all kind of solutions and is a central point for companies who need a 360° view of the activity. You could connect in those BI tools: ERP, CRM, PLM, Cloud services, etc. But..... not PDM Autodesk Vault. Why? Because there is no solution to query live the Vault Database (the Vault API is not a solution in this case). SQL queries are prohibited by Autodesk rules: https://forums.autodesk.com/t5/vault-ideas/allow-sql-select-query-on-vault-database/idi-p/9205104 There is no REST-API: https://forums.autodesk.com/t5/vault-ideas/rest-web-services/idi-p/9638516 This is a great opportunity to replace heavy RDLC report available in Vault. Thanks in advance.

JorgenBjornes · ‎07-17-2012

Instead of permanently deleting files from vault, make a recycle bin type functionality in Vault. Upon right clicking a folder, we should have the option to undelete the files (with dependents). Emptying the recycle bin should be an administrative task

Frodl · ‎10-24-2017

Hello, it should be possible to create a new folder at the datastandard Dialog.

john.stewart · ‎05-02-2013

Project based implementations using Vault have definite beginning and end. AEC and Infrastructure Customers are Project driven. MFG customers serving the Oil and Gas are also Project driven since machinery is custom specific for the project.Typical projects can create a large number of files throughout the Project lifecycle. E.g. Filestore = 5GB Customer Scenario: A customer can have 20 active projects and 100 completed projects over a 5 year period. In this scenario IT run weekly backups. 100GB for active projects and 500GB for completed projects. Currently Vault will require that all 600GB be backed up. Vault Project Archiving would allow IT to classify the 500GB filestore as Archive and exclude these Archive Filestore folders from the weekly backup. Solution : Allow administrator to archive Project folders from the ADMS Console. Project Files would be moved to a new ARCHIVE Folder that can be excluded from the ADMS backup or 3rd party Backup. The Vault Database metadata would point to the new ARCHIVE Folder location. The Project Files would be moved on all ADMS Filestore Servers and supported on Full replicated databases. The metadata for the Archived Completed Project would remain in the Vault Database. Folder ACLs can used to set the Archived Project to Read Only

mandalt · ‎07-25-2018

This ability will enable users to purge files controlled by lifecycle rules with ability to choose from number of latest versions to keep in the latest revision and also ability to choose files older than certain dates. This feature is available for files that are not controlled by lifecycle now it's needed for files controlled by lifecycle.

fvdhoef · ‎04-01-2024

Would be great when the document purge wizard contains a filter option for "Exclude versions". One can already skip versions having a certain value, but I would like to have the option, whenever a document version has a comment, it will be skipped by document purge. As a result only versions without a comment will be purged.

j_spiradek · ‎10-09-2018

Hyper link to an element in TC as a property of an element or file. If there is a property, you could export it to other systems (XLS, ERP).

tschaeferZNBXX · ‎03-10-2017

Currently there is no functionality present I can find to automatically attach a PDF file at Item Master record correction. This is time consuming to add each PDF file manually. This should automatically add PDF files when an Item is created if it has the same file name/part number.

philippelandry4954 · ‎03-12-2018

Hello, By using the files purge command in the ADMS, it is possible to purge the file store by basing on the document life cycle states. However, the rule is applied for each file previous version state, but not based on the last version. For example, the user is working on a document and save it several times into the database in a state allowing the edition (eg WORK IN PROGRESS). If you want to keep all version in the database during the design step you, you define in the life cycle state that none version is purged. When the document is validated (eg in RELEASED state) you would wish to keep only the document last version between the previous Revision and the current one. Unfortunately, the ADMS purge command will check the life cycle state of each version of the document, apply the rule and then keep a lot of useless files. My wish would be to consider the last version file state and apply the purge rules for the previous versions except the RELEASED and CANCELLED state. As long as the document is in an edition state, no purge could be applied because a user should be able to return to a previous version of design. When the document is in REALEASED state, all intermediated version should be purgeable even. Today we are able to set if we want to keep all versions, first and last, version, the last one or none. Moreover we are able to define what kind of state it is (Released or cancelled). Why isn't there a new option in RELEASED state saying that we want to keep the last version and purge all unflagged state previous versions ? Of course all RELEASED or CANCELLED document should be kept in the database. However, I think that we should keep the current working as today. when a child document is linked to another one (eg INVENTOR assembly) the document can not be purged whatever the life cycle state rule.

vault 2024 - Add a column "username" in "User and Group Management".

Better reporting with help of Microsoft PowerBI or Tableau

Recycle bin

Datastandard create a new folder

Vault Project Archiving

Ability to purge lifecycle controlled files with nunber of versions and days

Document purge: skip versions with any comment

Link to Item/File in Thin Client as a file/item property

Ability to attach PDF files on Item creation

PURGE ENHANCEMENT ON PREVIOUS DOCUMENT VERSIONS

Forums Links