We have recently implemented Okta identity management (www.okta.com) and it has been very successful in not only helping to provision/deprovision access to our cloud apps centrally but has also helped drive adoption and usage of those apps.
Adding SAML 2.0 support to Autodesk PLM360 would be a huge boon. This would require users being able to sign in with a corporate email address which may or may not also be an Autodesk ID.
the workflow state disappears from the editor window
create a new workflow state with the same name
create a transition to the new workflow state
try to transition an object to the new workflow state
receive error "<new workflow state> is not the unique short name of a workflow step in the relevant workspace"
It appears the original workflow state was orphaned (still existed but unable to access in the workflow editor) when the transition to it was deleted. The only workaround I could find was to delete the workspace and start over again.
We would like to be able to narrow down a linked picklist for a certain criteria.
Example: We use Product ID as a unique identifier for products. In other workflows, we will link a picklist of Product IDs to a form so that we can assign more attributes to the product. Product ID can have a status of "Assigned," "Orderable" or "Retired." We would like to pre-filter a picklist of products to show only those that are in status "Assigned" but not "Orderable" state. There is no current client-side scripting available today.
Only possible by "chaining" workspaces. Create a new picklist when the item changes status, e.g., when a Product ID is first released, spawn record in another workspace with the narrowed-down population of "Assigned." .
Conditional form-building in a workspace with workflow. We would like to be able to change a form layout based on a classification. Classification is the capability where we get different fields in a form for different scenarios, for example, in pricing.
The pricing attributes necessary for a product for a price list effective period can change depending on the period or type of product. The actual pricing framework and calculation can change as frequently as every month or any ad hoc period as set by the pricing team.
Framework impacts to forms Ex) We work on about price list effective periods at the same time – the form would be different for a different pricing framework
Per Jared: This is not on the roadmap. The team needs to talk to he product manager responsible for classifications for the expected timeline. The workaround is that we would use a more complex form that needs to accommodate the superset of everything that might be needed. The workaround is not ideal.
SOmetimes you want to add a new field or change an existing field for all the records in a WS. If there are hundreds of records, this is a tedious task. It would be great to be able to run a report to export the desired records to Excel. Then you can easily edit the Excel file to add or chnage the fields. Finally, you would import this Excel file and update the WS. Currently, the import won't work if the record exists so you have to purge the WS and import to create new records. This is not ideal if you have other workspaces and records linked to the records you need to update.
I'd like to see the ability in the import tool to check a box to check if a record already exists, then just update it.
I think it would be very useful to be able to "pre-filter" a pick list or linked pick list, using a pre-filtering text field, which can be editable, visible, or hidden. For example, I have a linked pick list in a "Product Family" workspace that points to my Items and BOMs workspace. I want users to be able to select one or more records from the Items and BOMs workspace, but I want them limited to a particular prefix (for example, we use 850- prefix for our SKU's). In my Product Family items and details tab, I could create a hidden field with the text, "850", which could be used to pre-filter the linked pick list to only show items starting with "850". When setting up the pre-filtering rules, it would be important to be able to specify the filter condition...starts with, contains, does not contain, etc.