Next week we’ll be going over multiple use cases in our PLM Talk technical webinar – so far my favorite bit is being able to easily approve/reject change requests so I’m not the bottle neck in our process!
In our last release we increased the time limit for script execution for both action and validation scripts. This request came to use from the PLM 360 IdeaStation. This forum was set up to allow our customers to easily share their wish list for product improvements with the PLM 360 development team. It’s a great place to review what’s been proposed and add your ideas to existing ones as well (or simply ‘kudo’ it so we can see how many folks are interested in the proposal).
Today’s tip is more of a best practice (and personal pet peeve when not employed!). When you set up a new workspace and define the descriptor, consider making those mandatory fields. Since the descriptor is used throughout the UI to easily identify items, it’s great to make it as meaningful as possible be making sure your end users input that data.
Want some more tips and tricks or some best practices on training your end users? Join us tomorrow for PLM Talk where I’ll talk about best practices around involving your end users in defining and improving your PLM 360 solution.
After spending last week clearing trails where we camp, I’m ready to get back to blogging about great new features in PLM 360! One that our coding friends will like is the new Clear() method we recently introduced. Before we had the remove () method which was great for removing a single specified value or object in an array, but you’d have to use a for loop to clear everything. Not anymore! Now you can use clear () – it’s supported on multi-select fields on the item details page and on the various tabs where you would need it: Grid,Relationships, Bill of Materials, Sourcing, Workflow Items, and Project Management.
For example, to remove all items from a multi-select pick list, you’d use item.MULTISELECT.clear(). Want to empty the grid array? Use item.grid.clear().