I like the idea of the new "out-of-the-cloud" learning tenant but a couple comments:
1. The name is confusing, I'm not sure what out-of-the-cloud means. How about "PLM 360 Model Tenant"?
2. Can I access this tenant? It would be sweet if the tenant were accessible so that I could create items and look at all the settings. I'd like to look at scripts, workflow setups, workspace setups, etc, but I don't need to be able to change anything. Everything shown in the model tenant would then be accessible to install via the App Store in my own tenant. That way I could really test things out before committing to an App, or I could grab code snippets or setups here and there without needing to install (or re-install) an App.
It would be really useful if the admin could set behavior for fields on clone. If i clone an item and want to carry over certain fields but not others. For example, if I have a fields for "close out comments" i would like that to ve set back to empty on the cloned item.
I need to be able to create reports detailing outstanding PLM tasks for all of my team-members. It would be greatly benefitial to be able to generate a report detailing my own and other people's outstanding work.
To aide breaking down of a BOM View into lists for different purposes the custom BOM view is great. But when you have multiple functional areas looking at that information such as Procurement, Fabrication, Wharehouse etc. it would be nice to be able to filter the list to show only items in the BOM that met a specific criteria. Similar to the way Excell uses it Autofilter.
The idea would be that you have a filter row you could pick or enter the filter than apply and the currently displayed view would get filtered to show only matching items (parent items could be included if that causes issues). This functionality would be used for both Nested and Flat BOM Views.
It would be a time saver to be able to configure a custom BOM view for the Flat view, Similar to the nested view. This could possibly be implemented with a checkbox for and Applies to Nested, Flat or Both.
We have set up custom BOM field that is used to trigger spawing of tasks to perform action on the item in the BOM Row, I.E. Generate an RFQ request where the item info is copied via script to the RFQ Record. The issue is that in the nested view the quantity shown is the unit quantity not the project rolled up quantity. To get that you need to switch to the flat view get the rolled up quantity and switch back to the nested view and enter the quantity to Request for Quote.
This is just one use case, but feel that functionality would make the BOM View for useful.
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.