New Idea
2 Kudos

Workflow version control, Export and Import

Status: New Idea
by ravidalli on ‎06-12-2014 03:30 PM



It would be very helpful to have following workflow features:


1) Export a workflow from one enviornment to Import to Other.

2) It would be nice to have export and import done with all dependencies like Permissions, scripts etc. if not then Import shall display messages for missing dependencies and allow import only if all dependencies are in place. Like the permissions, roles and scripts.


Also on the workflow summary there should be an option(button) for complete information where each Transistion information including Condition script, Validation Script, Action Script, all other selectable options along with Escalation setup.


This would give user to copy this information and version control/document it. Also it can be compared against other enviornment setup.


As of today it is very easy to miss a setting when you are copying your workflow from Dev to Prod.



Ravi Dalli

6 Kudos

After having become more familar with PLM it appears to me that the BOM handling across workspaces are lacking.


I like the idea of having multiple workspaces because it allows me to collect different information for different types of items. 

But I have come to the conclusion that this is simply not viable at this point, because:


1) PLM does not support BOM import when it references items in other workspaces. (It is possible manually)


2) Even if I did add them all manually, I cannot create a BOM view that includes my custom fields from other workspaces because the BOM view can only see the Descriptor field from other workspaces.


The result of this is that I have to put everything in a common workspace have have to clutter up the item details with a lot of fields that does not apply.


Proposed improvement

1) Include cross-workspace BOM import


2) More configurale BOM view, where I can specify the FIELDNAME (could be free text) for each column. If the FIELDNAME does not exist for a specific item/WS on the BOM, just leave it blank. For example: If I am referencing 3 different workspaces in a BOM and 2 of them has a field called PART_NUMBER, I would expect the value to be inserted if available, otherwise left blank/null.


Status: Future Consideration
Hello plmadmin, We appreciate your submission, and we will add this to our future enhancement list. thanks, Trung
13 Kudos

Allow a BULK IMPORT of Attachments

Status: Accepted
by Contributor Asingh5 on ‎11-05-2012 08:15 AM

It is highly tedious and annoying to attach a pdf or a dwg file to a list of items in a workspace. Having the ability to bulk upload attachments to specific items in a workspace would be ideal for mass drawing updates or file updates.


One solution would be importing a zip file of the attaching files and an excel file that would have the item descriptor in one column and the corresponding file name in the other column. 

Status: Accepted
6 Kudos

Import excel into grid tab

Status: Comments Requested
by james.n.tennent on ‎04-28-2013 12:03 AM

Need to be able to import data into grid tab.

This could be done in the same way that the items and boms is imported into

I don't know of any way to import large amounts of data into the grid tab currently which is restrictive


Thanks again


Status: Comments Requested
Hi James, This is a good request. Many customers have requested this feature. We already have it on our feature list. thanks, Trung
7 Kudos

Desktop folders

Status: Future Consideration
by Contributor jonas.andersson on ‎02-13-2013 03:45 AM

A function where a "desktop folder" can be added inorder to add/view documents from the desktop/finder directly into PLM360. The folder to be added should be connected to a certain workspace, where the user can chose which workspaces should be able to "share" information. 


The folder should be a direct connection through the username and password from the user, where permissions should be added depending on what role the user has.


Similar to dropbox, but with the added finess of PLM360.


Kind regards,



Status: Future Consideration
Jonas, interest idea. I don't think is something we'll address right away, but let's come back to this in the future
5 Kudos

Allow bulk Import into Multiple Selection Picklists

Status: Duplicate
by Contributor Asingh5 ‎11-14-2012 10:52 AM - edited ‎11-14-2012 10:53 AM

When using the import tool, performing a bulk import of values into a "single selection" linking picklist is possible. Unfortunately I cannot select a "Multiple Selection" linking picklist it in my import to do the same thing.


This feature is very important for our company since it would allow us to show our linked product items in one specific field, as opposed to having multiple "single selection picklists"--which doesn’t make a clean visual. 


The data I have is in a excel format. With over thousands of entries, having the import tool to bulk import the linking picklist values in the multiple selection picklists would allow me to provide my tenant with the information it needs efficiently and visually appealing.



Status: Duplicate
Comma delimited values can now be imported into multi-select pick lists! See the PLM 360 "What's New in PLM 360" page for more details on the June 2013 release.
1 Kudo

Static BOM import from separate workspace

Status: Accepted
by dsl145 on ‎11-14-2013 09:23 AM

I've got a situation where we have imported a large amount of Heirarchy items from Autodesk Vault and we need to link a an assembly of items to a specific repair.

If we were able to import a static snap shot of the assembly of items and then be able to assign a QTY New to some of the items.

Status: Accepted
Hi DSL145, I'm not understand your request. Please elaborate and provide additional information. thanks, Trung
4 Kudos

Call scripts at import

Status: Comments Requested
by Mentor on ‎10-04-2012 04:28 PM



It would be a useful addition if scripts could be called when performing imports. 





4 Kudos

Mass Deletes from the Import Tool

Status: Duplicate
by Employee jared.sund ‎06-22-2012 01:21 PM - edited ‎06-22-2012 01:22 PM

If a user imports a large number of new items (not BOM items) and realizes a mistake has been made. Now the user has to delete all these item through the UI, which is very painful. The user would like to perform a mass delete with a list of specific items.


It would be nice for the user to use the existing match functionality in the import tool, with the option to delete existing records on match.

Status: Duplicate
1 Kudo

Mass Manipulation of Attachments

Status: Accepted
by Distinguished Contributor jdavis417 on ‎08-04-2013 09:57 AM

Evaluting the process of a physical Design Review meeting, we've identified a want for a Mass Checkout/In feature.  Additionally, it would be nice to have the option to simply Mass Delete attachments.  This would give the user the option to bypass the "history" functionality (which is very useful to "build" by replacing files with all the marked-up then updated versions) which becomes very time-consuming when dealing with large numbers of attached files.


A "real" solution might be to simply embrace full Design Review functionality and workflows in the varous Autodesk 360 products!  .dwf(x) is your own file-type... why it always seems to be an afterthought, I don't understand.


For any design review process to work efficiently, we need attributes of the file (.dwf, for instance) that can be searched and sorted.  It is desireable to know the approval status without opening the file (this is more about files that are created and/or exist on my computer)!  Secondly, it could save a lot of file re-creation (and allow the re-use of the file to stop round-tripping from the cloud) if the .dwf (and .dwfx) document had the option of whether-or-not to print either Mark-ups, Stamps or both!!!!


Now, I must admit where a "cloud-only" mark-up/review/approval workflow falls apart (as of today)... it's for those of us who'd like to use the .dwf(x) as an "underlay", right under the sheet-to-be-corrected.  This use of the marked-up .dwf(x) allows the Autocad/Inventor user to complete and track the tasks as they are done... in their native application!  If Autocad/Inventor could open a cloud-based .dwf(x), edit it, then re-publish it... transparently... it would be easier to complete the Design Review process.  This is more about the Design Review product than PLM360, but I'd think that Autodesk would like to have one solution, rather than the several vaguely-similar markup/review approaches they currently employ.


To summerize my suggestions;

  1. Mass Checkout/In in PLM360
  2. Cloud-ize all of Design Review for consistant use in all Autodesk 360 and off-the-shelf products
  3. Add file attributes to .dwf(x) which indicate Approved status (if they don't exist)
  4. Add the option of printing DR markups, stamps, both or neither (if it doesn't exist)
  5. Add the ability to preserve mark-up and stamps upon recreation of .dwf(x) without creating another file (perhaps closing the open file as part of the "Republish Sheets" (in Inventor, for instance) process would allow the user to maintain one file... one file name... ? the current process won't over-write the open file but the Republish commands are unavailable after closing the underlay mark-up.)




Status: Accepted
Hi John, You have a lot of things on this one request. There are some things on this list that we will potentially add to the list and some are future considerations. If you can help breakdown this list and prioritize the level of importance for each the requests. Thank you, Trung

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

IdeaStation Guidelines
Review guidelines and best practices
before posting a new idea

PLM 360 Survey