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

Currently, the PowerShell scripts and modules in the Data Standard are frequently reloaded by the system—sometimes even twice for each action. For example, before every command execution via Data Standard (e.g., editing a file datasheet), all PowerShell scripts are reloaded twice. During the development phase, this is convenient because the application doesn't need to be restarted after modifying the scripts. However, in later stages of operation, this becomes unnecessary. Especially in more complex environments, loading the scripts and modules can take a considerable amount of time, significantly slowing down performance. Over the course of a workday, these PowerShell scripts are reloaded very frequently.   I believe it would be beneficial to make this behavior configurable. This way, we can retain the current behavior during development but avoid redundant script loading in regular operation Show More

If you set Vault permissions so that a group does not have the ability to create a change order, the behavior still allows for the new change order button to be clicked and a change order number to be consumed. Only after the user tries to click save does the error appear that they do not have permission to create a change order.   This should be changed to prevent clicking on the new button and prevent the consumption of a change order number.     Show More

Users would like better support for file handling within the autoloader. It's great that the autoloader detects errors, but why can't you replace or search for the faulty files? If, for example, data is missing that is located on an inaccessible external drive, why is there no way to change the path in the autoloader?       Show More

Select the model in the Forge Viewer (Vault) and right-click to view the document or article.   Im Forge Viewer (Vault) Modell auswählen und mit der rechten Maustaste kann dann das Dokument oder Artikel aufgerufen werden. Show More

Users would like the dialogs in the autoloader to be easier to use. The size can only be changed if you click on the dialog box in the bottom right corner. A standard Windows function for the dialog box would be desirable here. green arrow = change size red arrow = not possible See additional Autodesk Supportcase 23011250. Autoloader - Fehler die keine sind?     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 everyone,   Some time ago I customised the web.config of our VAULT Professional so that indexing is given a lower priority in day-to-day business. Just like in this knowledgebase entry:   https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-throttle-Vault-Search-Indexing-process-so-it-does-not-consume-all-System-resources.html   Nevertheless, today I had the problem that an indexing was carried out and the Vault was slowed down as a result.   After consulting with Markus Koechl, he made the following suggestion: If a property change is made during day-to-day business, there should actually be a query as to whether this change is necessary immediately or should only be carried out at a defined time.   This makes sense above all because we admins also want to finish work from time to time instead of starting the changes only then 😉   Greetings Sven   ____________________________________________________   Hallo Zusammen,   ich habe vor einiger Zeit bei unserer VAULT Professional die web.config so angepasst, dass Indezierungen eine geringere Priorität im laufenden Tagesgeschäft bekommen. Sprich wie in diesem Knowledgebase Eintrag:   https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/How-to-throttle-Vault-Search-Indexing-process-so-it-does-not-consume-all-System-resources.html   Nichts desto trotz hatte ich heute das Problem, dass eine Indizierung durchgeführt wurde und die Vault dadurch ausgebremst wurde.   Nach Rücksprache mit Markus Koechl, machte er folgenden Vorschlag: Wenn eine Eigenschaftsänderung im laufenden Tagesgeschäft vorgenommen wird, müsste eigentlich eine Abfrage kommen, ob diese Änderung sofort nötig ist, oder erst zu einer definierten Uhrzeit durchgeführt werden soll.   Dies macht vor allem Sinn, weil wir Admins ja auch mal Feierabend machen möchten, anstatt erst dann mit den Änderungen anzufangen. 😉 Gruß Sven Show More

Wir würden gerne in der Dokumentenansicht neben dem Symbol "Verknüpfung mit Artikel" auch ein Symbol für den Artikelstatus sehen. So erkennt man schnell, ob der Artikel am Dokument auch freigegeben ist. Unsere Arbeitsweise sieht vor: 1. Dokumenten- Freigabe 2. Artikel- Freigabe 3. mit der Artikel- Freigabe werden die Daten ins Fusion PLM übergeben. Bei einer Änderung erhät das Dokument eine neue Revision. Bei der Freigabe des Dokument wird der Artikel in "Bearbeitung" genommen. Der Artikel muss nun noch freigegeben werden. Leider kann der PDM User den Status des Artikels direkt am Dokument nicht sehen.   --------------------------------------------------------------------------   We would like to see a symbol for the article status in the document view next to the "Link to article" symbol. This way you can quickly see whether the article in the document has also been released. Our way of working is as follows: 1. Document release 2. Article release 3. With the article release, the data is transferred to Fusion PLM. If a change is made, the document receives a new revision. When the document is released, the article is put into "processing". The article now has to be released. Unfortunately, the PDM user cannot see the status of the article directly on the document. Show More