Product Line Code - which is the lowest level of child
Can we do a validation from a field in a Parent item details form to a child BOM?
The Pricing form has a field to display Product name and show some derived fields that are used in a pricing calculations. Can we ensure that somewhere down the chain of BOMs, that the same Product is added as a child?
The validation logic may possibly only be done on a workflow transition.
Form validations on the client side can save the user's time by pointing out errors in the form as they are entered or auto-populating values based on other values in another field.
An example is on a pricing form where there some data relationships that should not be broken and internal logic would be enabled based on values the user selects. If a user selects value 1 from picklist A, then picklist B would show a different set of values than if the user selected value 2.
In PLM360, the history of an item is available through a change log, however, the change log is not available through the API for each record in order to enable historical reporting on the actions for an item.
Use Case: changes to Product Name as it moves from temporary to legal versions.
Previously we had problems with product name changes over time because we were communicating to customers about products they didn’t buy.
We could write on every transaction into the ODS
For Ad hoc we could clone records into another workspace and store them for a historical view
There should be an easier way to delete items from a workspace without having to use the import tools. Sometimes you just want to delete 8 items and there is not an easy and fast way. I know that exist the import utility but you need to have a spreadsheet in order to do it.
I'd love to see more robust script management. Ideally I'd like to see the ability to officially version or rev scripts. In addition to the Save button, you could add a button for Version. This would store the script in its current state with the appropriate verison number.
In addition, I'd like to review previous versions of the script and have the option of making a previous version the current version.
byAsingh511-06-201208:22 AM - edited 11-06-201208:25 AM
The TABS section of the preview should open up and expand when clicked on instead of redirecting to the specific item. This would allow the quick easy access to key information such as BOM items, attachments, relationships, changes ext. Also there should be the ability to click the specified print view for the item as well.
It would be VERY useful to allow a tenant to be divided into secure "Projects" so that access to information relating to different projects could be controlled centrally. This should allow workspaces to be managed centrally, but used optionally on each project. Similarly, roles should be managed centrally, but users are given a role on each project allowing them to have differing levels of access. This model is already used to good effect in Buzzsaw.