as sometimes we have to have the Workflow Transition to be finished before being able to "play" with item created within Action Script (Add item to BOM etc...), could it be possible to have some step that are acting as robot... it means that it should launch a scipt when this "robot" script is reached...
in case of failure, we can either cancel previous Transition or if successfull, force next Transition to go to the next "manual" Step...
What are the chances that the Autodesk team could come up with a solution to change future Field Data Types and not lose all previous saved data.
I have come across this a number of times. I am wanting to keep the same data, but learning the system and its capabilities I have found more efficient ways to pull the data along. The current way is running a report and using an excel spreadsheet to re-populate the fields (which is a strenuous process, for me)
It would be great to have a matrix built based on a dynamic data set, like color and size; You could specificy sizes across the top and colors along the sides and allow the user to enter values at the intersection of both values, like indicate if this combination is offered or not. This would eliminate the need to hard code the values in a matrix every time new valuse are added and make the matrix more useful over all.
Please can you consider the user of the work Close instead of cancel. For example, I've just edited the item details in one of my workspaces. I've clicked "save layout" and the green banner has appeared, saying "the layout was successfully saved." my only option to exit this interface is to click "cancel" couldn't this be "close" to save any confusion?
A use case came up to compare two BOMs using the flat version of the BOMs. Basically we are going to start importing quoted (flat) BOMs into PLM 360 to compare to the structured/level BOMs created in our custom configurator application. The team is looking a quick way to verify totals in PLM 360, exporting to excel is possible but sub-optimal. Ideally you would mimic the Nested Views and features for the flat view.
Right now you can only use purge on the workspace to remove all the data in that workspace, one issue we are facing is deleted items are appearing in search and other users are finding ways of navigating to them. So basically any user error or duplicate that we deleted sits in our data forever and crops up to cause confusion.
So I am looking for a way to truly hide deleted items, their previous releases, and all the relationships they may have (project, BOM, relationships...). The two options I can think of would be purging those deleted items from the workspace or possibly creating a deleted item view permission.